Can I use Jira instead of GitHub?

Not as shipped; the package is GitHub only. Jira’s Create Issue call takes the same title and body, so the swap is one node and a new credential; the setup guide marks the spot. Change one value and the duplicate check looks for a Jira browse link instead.

Which tag triggers it?

Any tag you choose. Bug is the default, set in one field at the top of the workflow. Intercom sends the webhook for every tag added to a conversation, and the first step drops all but the one you named.

What does the customer see?

Nothing. Internal note, your repo, your Slack channel. Only the Slack message carries the customer’s email. The issue body links to the conversation rather than naming the customer, and the prompt is told to leave names and addresses out, but read the first few drafts before pointing this at a public repo.

Does it need a paid n8n plan?

No particular tier. Any n8n Cloud plan or a self-hosted Community Edition instance runs it; nothing here needs an Enterprise feature. Intercom does need a public webhook URL, which Cloud provides and self-hosted users get through their own domain or a tunnel.

IcAIGHSMade to order

Customer support & tickets

Intercom conversation tagged 'bug' → GitHub issue + note back + Slack

Tagging a conversation in Intercom opens a written-up GitHub issue and links it back.

Bugs reported in support chats get retyped into the tracker, or lost. With this flow an agent adds one tag to the Intercom conversation and the rest happens. GPT drafts the write-up, an issue opens in your GitHub repo with labels, the link is noted back on the conversation, and engineering hears about it in Slack. If GitHub rejects the call, the summary still reaches Slack.

How it works

Ic
Trigger
conversation_part.tag.created webhook: a teammate adds a tag to a conversation in the Inbox
Intercom
if
Step 1
Keep only the bug tag
Each payload names the tag and the conversation ID; anything other than the tag you configure (bug by default) is dropped here.
Ic
Step 2
Pull the whole conversation
Retrieve Conversation returns the customer’s messages, agent replies, contact email, assignee and the existing internal notes.
if
Step 3
Skip if an issue already exists
If an internal note already links to your repository’s issues, the run stops so a re-applied tag cannot open a duplicate.
AI
Step 4
Draft the issue title and summary
GPT turns the thread into a title plus four sections: what the customer did, what they expected, what happened, and any browser or plan details mentioned.
GH
Step 5
Open the issue in your repository
Create Issue files the title and body in the repo you choose, applies the bug and from-support labels, and links back to the Intercom conversation.
Ic
Step 6
Note the issue link on the conversation
A Reply call with message_type note, posted as the admin you choose, adds an internal note with the issue number and URL, visible to agents, hidden from the customer.
S
Step 7
Tell the engineering channel
A Slack message carries the issue link, the customer's email, the assigned agent and the first line of the summary.
S
Step 8
Catch a failed GitHub call
When Create Issue errors, the drafted summary and conversation link go to Slack marked unfiled, and the n8n run is recorded as failed for retry.

What changes once it runs

One tag in Intercom produces a labelled GitHub issue with a structured write-up, without the agent leaving the inbox.
Whoever picks up the customer later can check the fix status, because the issue link sits on the conversation as an internal note.
Re-applying the tag does not create a second issue; the flow checks for an existing link first.
Engineering sees the report in Slack with the customer's email and the agent who filed it.
A GitHub outage or a bad token does not lose the report: the summary lands in Slack marked as unfiled.

What you get

n8n workflow export with the error branch already wired
A setup guide for the Intercom private app and webhook, the GitHub token, the OpenAI key and the Slack app
Issue-writing prompt as an editable file, with the section headings the issue body uses
A GitHub issue body template you can change without touching the prompt
A recorded walkthrough of one tagged conversation becoming an issue, a note and a Slack post
30 days of email support for setup questions

Before you start

Intercom: a private app in the Developer Hub with an access token that can read and reply to conversations, and the admin ID the note is posted as
Intercom: a webhook subscription to the conversation_part.tag.created topic, pointed at the n8n webhook URL
A GitHub fine-grained personal access token with Issues read and write on the target repository
An OpenAI API key with a payment method on file
A Slack app or bot able to post in the engineering channel
An n8n instance reachable from the internet so Intercom can deliver the webhook (n8n Cloud, or self-hosted with a public URL)

Built for

Questions before you buy

Can I use Jira instead of GitHub?: Not as shipped; the package is GitHub only. Jira’s Create Issue call takes the same title and body, so the swap is one node and a new credential; the setup guide marks the spot. Change one value and the duplicate check looks for a Jira browse link instead.
Which tag triggers it?: Any tag you choose. Bug is the default, set in one field at the top of the workflow. Intercom sends the webhook for every tag added to a conversation, and the first step drops all but the one you named.
What does the customer see?: Nothing. Internal note, your repo, your Slack channel. Only the Slack message carries the customer’s email. The issue body links to the conversation rather than naming the customer, and the prompt is told to leave names and addresses out, but read the first few drafts before pointing this at a public repo.
Does it need a paid n8n plan?: No particular tier. Any n8n Cloud plan or a self-hosted Community Edition instance runs it; nothing here needs an Enterprise feature. Intercom does need a public webhook URL, which Cloud provides and self-hosted users get through their own domain or a tunnel.

Nearby on the shelf

Whole catalog