Connector · Support
Intercom, in every client’s workflows.
Create a lead, update a contact, or start when a new contact is added, with the client’s own Intercom account.
- Triggers
- 2start a workflow
- Actions
- 2steps in a workflow
Start a workflow when something happens in IntercomBeta
By webhook where Intercom sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Intercom turns it off the alert carries a Reconnect button.
- A new contact is addedPolledA lead or user created in Intercom (a chat, a form, an import), checked every 5 minutes.
- A new conversation comes inPolledA conversation started (a chat, an email), checked every 5 minutes.
Do it in Intercom
A step with its own fields: values from the run go in by name, and what Intercom answers is there for the next step.
- Create a leadA new lead (a contact who is not yet a user).
- Update a contactChange a contact’s name, email, phone or custom attributes, found by id. Fields left empty keep their value; custom attributes must exist in the workspace.
Connect the client’s Intercom
On the client’s page in Thrum: Add credential, type Intercom access token.
In the client’s Intercom: Settings → Integrations → Developer Hub → New app (for their own workspace, no review) → Authentication → copy the access token. The conversation trigger needs the app to be allowed to read conversations.
The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.
Watched like everything else
When Intercom stops answering or refuses the client’s key, you hear about it, and your client does not.
- A failing request
- Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
- A service that asks for a pause
- Given it, up to an hour
- Requests at once, per account
- 2, per worker; the rest wait their turn
- Timeout
- 15 seconds, unless the step sets its own
- Private and internal addresses
- Refused, on every redirect too
- The client’s key
- Encrypted, bound to the client, and kept out of every run record
- A step that keeps failing
- Marks the workflow Degraded and alerts you, not the client
Intercom and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.