What this workflow does
This workflow reads messages with a ticket emoji 🎫 from a Slack channel.
It checks if tickets already exist in Linear for those messages.
If not, it asks ChatGPT to make a ticket title, summary, troubleshooting tips, and priority.
Then it creates a new ticket in Linear with all the information.
This saves time and stops duplicate tickets from being made.
Who should use this workflow
Teams that get many customer support messages in Slack with 🎫 emoji.
People who want to make good organized tickets in Linear without doing it manually.
Anyone who wants AI to help make better ticket summaries and priority decisions.
Tools and services used
- Slack: To read new messages from a support channel.
- Linear: To manage and create support tickets.
- OpenAI ChatGPT API: To write ticket titles, summaries, suggestions, and set priority.
- n8n automation platform: To run and connect all steps in the workflow.
Inputs → Processing → Output
Inputs
- Slack channel messages with ticket emoji 🎫.
- All existing Linear tickets to find duplicates.
Processing Steps
- Search Slack every minute for messages in the chosen channel tagged with 🎫.
- Extract details like message text, user, permalink, and timestamp.
- Download all current Linear tickets and get their descriptions.
- Find Slack message IDs referenced in Linear tickets to spot duplicates.
- Compare new Slack messages with existing ticket message IDs to decide if a new ticket is needed.
- Send new message texts to ChatGPT with a prompt to create a short title, summary, troubleshooting tips, and priority level.
- Parse ChatGPT response into JSON format to get structured ticket details.
- Create a well-formatted new Linear ticket using ChatGPT outputs and Slack message metadata.
Output
- New tickets in Linear with clear titles, summaries, suggestions, priorities, and original Slack message links.
- Less duplicate tickets and improved ticket quality.
- Support team saves hours each week.
Beginner step-by-step: How to use this workflow in n8n
Import the workflow
- Inside the n8n editor, click the Download button on this page to get the workflow file.
- In n8n, choose Import from File and upload the downloaded workflow.
Set up credentials
- Add your Slack API credentials with permission to search messages.
- Add your Linear API key that can read and create tickets.
- Add your OpenAI API key for ChatGPT access.
Update workflow settings
- In the Slack node, check the search query to match your Slack channel and emoji if different.
- Review the Linear ticket priority ID mapping in the Create Ticket node, and change IDs if your Linear setup is different.
- Edit the prompt text in the Generate Ticket Using ChatGPT node if you want to change what the AI returns.
Test and activate
- Run the workflow once manually to confirm it finds Slack messages and creates tickets properly in Linear.
- If tests pass, turn on the workflow to run automatically on its trigger schedule.
- Keep an eye on execution logs for errors or skipped items after activation.
For users self hosting n8n, see self-host n8n for help with setup and management.
Common issues and edge cases
- Slack API rate limits: Too frequent queries cause limits errors. Increase schedule interval or reduce search size.
- No tickets created when expected: The workflow may think tickets exist due to wrong Slack message ID extraction from Linear tickets. Check the regex in Get Hashes Only node.
- Linear authentication failure: Wrong or expired API keys cause failure. Re-enter credentials.
Customization ideas
- Change the Slack channel monitored by editing the query in the Slack node.
- Adjust or add priority levels in Linear by changing the ID map in create ticket step.
- Modify the AI prompt to ask for sentiment, escalation advice, or other details.
- Add more Slack message data like thread IDs or attachments to ticket description for more info.
Summary of benefits
✓ Saves time by searching Slack and making tickets automatically.
✓ Stops creating duplicate tickets.
✓ Makes tickets clearer and more complete with AI summaries and suggestions.
✓ Keeps ticket data linked to original Slack messages.
✓ Helps support teams focus more on solving problems than organizing info.