verapli
Sign inJoin free
Menu

Guides · messaging · Popular APIs

Intercom Developer Hub app

Create an app in the Intercom Developer Hub; private apps use the workspace access token, public apps use OAuth and must pass Intercom's app review before other workspaces can install them.

Researched · not yet run liveLast researched 25 October 2026 · Intercom · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

Apps are created in the Developer Hub against a workspace (paid workspace for private apps, development workspace for public apps).

  • Intercom workspace (paid) organisationoptionalFor private apps.
  • Intercom development workspace developeroptionalRequired for public apps; free; US region only.

Have ready

  • End-to-end video showing OAuth install (full client_id and state in URL), all functionality, and uninstall [3]Needed for: Submit for app review
  • Privacy policy and end-user agreement for the listing [to verify] Needed for: Submit for app review

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Create the app

    In Developer Hub > Your Apps click New App, name it, choose the workspace (create a development workspace for public apps), then Create app.

    • verapli co-pilot
    • Human step: You press submit

    Where: https://app.intercom.com/a/apps/_/developer-hub

  2. Copy the access token (private apps)

    The app's Authentication page shows the access token for your own workspace; never share it with third parties.

    • verapli co-pilot
    • After: Create the app

    verapli captures INTERCOM_ACCESS_TOKEN here by plain code: encrypted in your browser, never shown to AI.

    Where: https://app.intercom.com/a/apps/_/developer-hub

  3. Turn on OAuth (public apps)optional

    On Authentication tick Use OAuth, add HTTPS redirect URLs and the minimum scopes; copy client ID and secret from Basic Information.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create the app

    verapli captures INTERCOM_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.

    Where: https://app.intercom.com/a/apps/_/developer-hub

  4. Submit for app reviewoptional

    Submit with the end-to-end video; reviewers check that scopes match functionality. Required for listed and unlisted public apps.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Turn on OAuth (public apps)
    The provider says
    Review can take up to seven business days; resubmissions also up to seven business days. [3]

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Development workspaces are US-only and their apps can't be installed into EU or AU paid workspaces. [1]

Worth knowingThe rules say

Changes to an approved public app need re-review [to verify]. [3]

What you end up with

Env varSecretFormatWhat it is
INTERCOM_ACCESS_TOKENsecretopaque token stringWorkspace access token (private app)
INTERCOM_CLIENT_IDnot secretopaque id stringOAuth client ID
INTERCOM_CLIENT_SECRETsecretopaque secret stringOAuth client secret

For agents

The same entry as JSON: /api/v1/entries/intercom/app · requirements /api/v1/requirements/intercom/app · terms /api/v1/terms/intercom/app.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Intercom Developer Hub app, and how long will it take?"
  → tools/call requirements { "provider_id": "intercom/app" }

Sources

  1. Set up a Workspace Public apps must be built in a new development workspace; private apps can use the paid workspace; Developer Hub > Your Apps > New App; access token on Authentication page; development workspaces free, US-only, 20 users/leads, cannot be converted; not advised for EU/AU accounts. · accessed 25 October 2026 · official
  2. Setting up OAuth Tick Use OAuth on Authentication page; HTTPS redirect URLs; select scopes (reviewed on submission); client_id and client_secret on Basic Information page; regional authorize endpoints. · accessed 25 October 2026 · official
  3. App Review and Publishing Public apps (listed or unlisted) must be reviewed before install; private apps not; end-to-end video of OAuth install, functionality, uninstall with full client_id and state visible; review up to seven business days, same for resubmissions. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Intercom is not affiliated with verapli.