1. Before you start
- Confirm that you administer the intended Seedling workspace and can authorize an Intercom app for the intended Intercom workspace.
- Identify whether the Intercom workspace uses the US, EU, or AU data region before starting OAuth.
- Review the displayed read permissions, 90-day initial conversation/contact window, restricted-by-default access, and 500-part history boundary.
- Do not send Intercom credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
2. Connect Intercom
- Open the Intercom connection in the intended Seedling workspace and review the current data-use notice.
- Select the correct Intercom region and continue to Intercom OAuth.
- Authorize the displayed read capabilities. Seedling rejects a partial capability grant.
- Return to Seedling and wait for identity verification and the bounded initial synchronization.
- A workspace administrator must explicitly configure the source audience before members can read synchronized content.
3. Authorization and connection problems
- Wrong region
- Restart authorization with the region that owns the Intercom workspace. Seedling does not silently redirect API traffic between regions.
- Missing capability
- Confirm the required read capabilities in the Intercom Developer Hub, then restart OAuth. Seedling fails closed when any capability probe is forbidden.
- Authorization required
- Reconnect the same Intercom workspace after an uninstall, revoked token, or persistent unauthorized response.
4. Missing or delayed data
- Confirm the record was updated inside the synchronized history window and is visible to the installed Intercom app.
- For contacts, allow for Intercom search propagation and the whole-day overlap reconciliation.
- For conversations, check whether Seedling reports the provider's 500-part history cap.
- For articles, confirm that the locale is published; drafts and unpublished locales are intentionally excluded.
- Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
- If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.