It would help if there was a node for:
Intercom
My use case:
We use Intercom Tickets that are linked to conversations. I want to automate the following lifecycle:
-
When an Intercom ticket state changes to “Waiting on customer”, automatically:
- Add a specific tag (e.g.
ticket_waiting_on_customer) to the linked conversation.
- Add a specific tag (e.g.
-
When a customer sends a new message on that conversation:
-
If the conversation has the
ticket_waiting_on_customertag:-
Automatically update the linked ticket state back to “In progress”.
-
Optionally remove the tag from the conversation.
-
-
This is doable today using:
-
An Intercom webhook for ticket events
-
An Intercom webhook for conversation replies
-
Generic Webhook and HTTP Request nodes in n8n
But it’s fragile and not friendly to non-technical users. You need to:
-
Manually register and maintain Intercom webhooks
-
Handle authentication to the Intercom API
-
Parse payloads and map IDs between tickets and conversations
-
Manually construct API URLs and payloads for every small change
A dedicated Intercom node would:
-
Expose ticket and conversation triggers directly in n8n
-
Provide pre-built operations such as “Update ticket state”, “Tag conversation”, “Find ticket by conversation ID”, etc.
-
Make these flows understandable and maintainable for non-developers who manage support operations.
Beyond this specific use case, the same node could support routing, SLA escalations, re-open logic, follow-up reminders, reporting, and other Intercom-based workflows.
Any resources to support this?
Are you willing to work on this?
I can:
-
Provide detailed requirements and example payloads from a live Intercom workspace
-
Help test the node against real-world support workflows
-
Give feedback on UX and edge cases (e.g. multiple tickets per conversation, state transitions, tagging strategies)