Intercom
Support Access tokenManage contacts, conversations, tickets and tags in Intercom from any Windmill script, flow or app.
Set up in 3 steps
Create an app and copy its token
At apps.intercom.com, create an app. Its access token is under the Authentication tab, and the API version it uses is shown on the app page — note both.
Add the resource in Windmill
Open Resources, add a resource of type intercom, and fill token and apiVersion with the version your app reports.
Run your first script
Fork any script below and read before writing anything. There are hundreds here, so search by the verb you need.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Create Note
Send Incoming Message
Update an existing attribute for a ticket type
Update an article
Update a visitor
Update a ticket type
Update a ticket
Update a news item
Update a data attribute
Update a conversation
Update a contact
Update a company
Update a collection
Unarchive contact
Submit a data event
Show content data export
Set an admin to away
Search tickets
Search for articles
Search conversations
Search contacts
Scroll over all companies
Run Assignment Rules on a conversation
Retrieve companies
Retrieve an article
Retrieve an admin
Retrieve a visitor with User ID
Retrieve a ticket type
Retrieve a ticket
Retrieve a team
Resource type
intercom — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| apiVersion | string | Yes | |
| token | string | Yes |
Questions
Why does it ask for an API version?
Every request sends it as a header, and Intercom changes response shapes between versions. It must match the version your app is pinned to, or fields the scripts expect go missing.
Is my token stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.