Turn Slack requests into clear tickets in Linear with AI. The flow watches a channel for the ticket emoji and writes a clean issue with title, summary, and priority. It suits support teams that chat in Slack and track work in Linear.

On a set schedule, the workflow searches Slack using a query that targets a specific channel and the ticket emoji. It collects the message id, user, and link, then pulls current issues from Linear and gathers descriptions. A merge and check step blocks duplicates by matching the Slack message id. New items go to an AI step with a strict schema so the output is structured. The ticket is then created in Linear with the AI title, summary, and priority.

You need Slack, Linear, and OpenAI accounts and credentials. Configure the Slack channel to watch, the Linear team to receive tickets, and the run interval. Expect faster intake, fewer duplicates, and better ticket quality. This is useful for internal help desks, bug reports from team channels, and quick capture of feature ideas without leaving Slack.

• Schedule Trigger polls Slack at set intervals for new requests
• Slack Search filters a specific channel for messages with the ticket emoji
• Set node extracts message id, user, channel, and permalink for tracking
• Linear Get All retrieves existing issues to compare and prevent duplicates
• Aggregate and Set build hashes from message data to match prior tickets
• If node decides when a new ticket should be created
• LLM Chain with OpenAI generates title, summary, and priority from the message
• Structured Output Parser enforces a JSON schema for safe field mapping
• Linear Create Ticket posts the new issue using the AI generated content

• Reduce manual triage from 30 minutes per day to 5 minutes
• Automate about 90% of ticket entry from Slack
• Eliminate up to 95% of duplicate tickets with id checks
• Connect Slack, OpenAI, and Linear in one flow
• Create consistent tickets with clear titles and priorities

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Slack, Linear and OpenAI. See the Tools Required section above for links to create accounts with these services.
3. Open the Slack node: in the 'Credential to connect with' dropdown, click 'Create new credential' and follow the on screen steps. Make sure the app or bot has access to the channel you will monitor.
4. Open the Linear nodes: choose 'Create new credential' and paste a personal API key from your Linear settings. Name the credential clearly, such as Linear Support API Key.
5. Open the OpenAI Chat Model node: choose 'Create new credential' and paste your OpenAI API key from your account. Select the model you prefer.
6. Set the Slack query to your channel. In the Slack node, update the query to match your channel name, for example in:#support has::ticket:. Keep the limit at a level that fits your volume.
7. Adjust the Schedule Trigger. Choose an interval in minutes that fits your intake speed, such as every 5 minutes.
8. Set the Linear team in the Create Ticket node. Pick the correct team name or team id so new issues land in the right queue.
9. Review the AI output fields. In the LLM Chain and Structured Output Parser, keep the fields for title, summary, ideas, and priority so the mapping is stable.
10. Test the Slack search. Post a message in the chosen channel with the ticket emoji and a clear request. Run the workflow once to confirm the Slack node returns the message.
11. Validate duplicate protection. Run once to create a ticket, then run again without changing the message. Confirm the If step blocks a second ticket.
12. Verify ticket creation in Linear. Check that the title, summary, and priority are filled correctly and that the message link appears in the description.
13. Troubleshoot common issues. If Slack returns no results, add the bot to the channel and check the query. If Linear fails, confirm the API key and team id. If the AI step errors, check your OpenAI key and model limits. Use the n8n execution logs to see which node failed.