Intercom Setup Integration Block for React

Intercom hosts a workspace's data in one region, and each region has its own API host: api.intercom.io for the US, api.eu.intercom.io for Europe and api.au.intercom.io for Australia. The block shows the host for the region you pick, so your integration calls the right one. The region is the one the workspace was created in; it isn't a choice made at install time.

They are the names Intercom's Developer Hub shows when an admin approves an app: Read conversations, Read and list users and companies, Write tags and Write conversations. Which of them your app needs depends on what it does; list your own in SCOPES, and mark the ones you can work without as optional. Unticking a required one blocks Continue and says why.

No. The sample message is a plain text box, and outcomeOf applies four typed rules (billing, access, bug and churn-risk words) to what you type in the browser. If Write conversations is off, the team line says it isn't assigned. Nothing is sent anywhere; replace matchOf with a call to your own routing service to use real rules.

It changes local state only and a status line says "Connected in this demo. Nothing was sent to Intercom." Disconnect returns to the first step. Wire finish to your own OAuth start, where the admin approves the permissions in Intercom.

Steps are a list of buttons; later steps are unavailable until you reach them. Moving focuses the new step's heading, and a polite line says "Step 2 of 3: Permissions". The test result is spoken once typing has paused. The permission rows are real checkboxes, named by their Intercom permission name.

On a phone the step titles hide (the numbers stay), the two test panes stack and Back and Continue become full-width buttons. In a right-to-left layout the bands flip while hosts and tags keep their left-to-right order. The header fades up once on load, and not at all with reduced motion.