← All N8N workflows
AI & researchAggregateChain LLMIfLinearOpenAI Chat Model

search slack and receive schedule events and list linear

Configured with Aggregate, Chain LLM, Linear, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
MessagingSlackSlackAI & modelsOpenAI Chat ModelOpenAI Chat ModelTransformStructured OutputParserOutput Parser StructuredTriggerSchedule TriggerSchedule TriggerTransformGet ValuesEdit FieldsRoutingCreate New Ticket?IfIntegrationGet Existing IssuesLinearAI & modelsGenerate Ticket UsingChatGPTChain LLMIntegrationCreate TicketLinearTransformMergeMergeTransformGet Hashes OnlyEdit FieldsTransformCollect DescriptionsAggregate

Node categories in this workflow

  • Messaging
  • AI & models
  • Transform
  • Trigger
  • Routing
  • Integration

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
SlackMessagingSlacksearch
OpenAI Chat ModelAI & modelsOpenAI Chat ModelSee node parameters
Structured Output ParserTransformOutput Parser StructuredSee node parameters
Schedule TriggerTriggerSchedule TriggerSee node parameters
Get ValuesTransformEdit FieldsSee node parameters
Create New Ticket?RoutingIfSee node parameters
Get Existing IssuesIntegrationLineargetAll
Generate Ticket Using ChatGPTAI & modelsChain LLMSee node parameters
Create TicketIntegrationLinearSee node parameters
MergeTransformMergeSee node parameters
Get Hashes OnlyTransformEdit FieldsSee node parameters
Collect DescriptionsTransformAggregateSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • linearApi
  • openAiApi
  • slackApi

Workflow notes

1. Query Slack for Messages

1. Query Slack for Messages

Read more about the Slack Trigger

Slack API search uses the same search syntax found in the app. Here, we'll use it to filter the latest messages with the ticket emoji within our designated channel called #n8n-tickets.

2. Decide If We Need to Create a New Ticket

2. Decide If We Need to Create a New Ticket

Read more about using Linear

For generated issues, we add the message id to the description of the message so that we can check them at this point in the workflow to avoid duplicates.

3. Use AI to Generate Ticket Contents

3. Use AI to Generate Ticket Contents

Read more about using Basic LLM Chain

For this demo, we've instructed the AI to do the following:

  • Generate a descriptive title of the issue
  • Summarise the user message into an actionable request.
  • Determine a prority based on tone and context of the user message.
  • Can offer possible fixes through use of tools or RAG. (not implemented)
Try It Out!

Try It Out!

This workflow does the following:

  • Monitors a Slack channel for new user messages asking for assistance
  • Only user messages which are tagged with the ticket(🎫) emoji are processed.
  • Linear is first checked to see if a ticket was created for the user message.
  • User messages are sent to ChatGPT to generate title, description and priority.
  • Support ticket is created in Linear.

Need Help?

Join the Discord or ask in the Forum!

Happy Hacking!

4. Create New Ticket in Linear

4. Create New Ticket in Linear

Read more about using Linear

With our ticket contents generated, we can now create our ticket in Linear for support to handle.

Sticky Note4

🚨Required

  • Set the Slack channel to monitor here.
Sticky Note5

🚨Required

  • Set the Linear Team Name or ID here.
search slack and receive schedule events and list linear

search slack and receive schedule events and list linear

Purpose and structure

This folder contains the search slack and receive schedule events and list linear workflow. Its executable nodes use aggregate, chainLlm, if, linear, lmChatOpenAi, merge, outputParserStructured, scheduleTrigger, set, slack. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Schedule Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Schedule/0526_Schedule_Slack_Create_Scheduled.json MIT; preserve source notices.

More in AI & research