OAuth Guide
← All guides

Intercom

Hard

Building and testing OAuth in a free development workspace is quick, but a public app stays private to your own team until Intercom reviews it, so no customer can connect before approval.

Agent-researched, not yet reviewed by a personResearched 2026-10-20

Working in dev

30–60 min

Signing in with your own account

Any user can connect

1–3 weeks

A public unlisted app that reads and writes conversations, tickets and contacts in customers' workspaces; App Store listing is a separate optional step after approval.

Waiting on
Intercom app review (stated as up to seven business days), plus resubmission time if scopes or the video are rejected.
Cost
No fees found in the docs

What you need first

  • An Intercom development workspace

    Apps are created in the Developer Hub of a workspace; development workspaces come with OAuth enabled.

  • HTTPS redirect URLs (test and production can both be registered)

    Intercom requires HTTPS redirect URLs; the first is the default and others are chosen with redirect_uri.

  • Test credentials or setup instructions for your own service

    Reviewers need to exercise the full app if it requires an account with you.

  • Privacy policy URL and support email (for an App Store listing)

    Both are required listing fields.

Who does what

Intercom OAuth setup · OAuth Guide