Sentiment analysis tracking on support issues with Linear and Slack
Ready for 3.0What this workflow does
This AI workflow has 14 nodes and runs on a schedule (every 30 minutes) (plus 1 other trigger). Along the way it connects OpenAI Chat Model, Airtable, GraphQL and Slack.
How it runs
Trigger: On a schedule (every 30 minutes) (plus 1 other trigger).
- Fetch Active Linear Issues (GraphQL): uses GraphQL
- Sentiment Transition (Switch): routes items into 1 branches
- Issues to List (Split Out): splits a list into separate items
- Deduplicate Notifications (Remove Duplicates): removes duplicate items
- Sentiment over Issue Comments (Information Extractor): extracts structured fields from text with AI, with model: OpenAI Chat Model
- Report Issue Negative Transition (Slack): uses Slack
- Combine Sentiment Analysis (Edit Fields (Set)): sets or maps fields
- For Each Issue... (Loop Over Items (Split in Batches)): loops over the items in batches
- Copy of Issue (Edit Fields (Set)): sets or maps fields
- Get Existing Sentiment (Airtable): search
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (12)
- Split Out
n8n-nodes-base.splitOut - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Edit Fields (Set)
n8n-nodes-base.set - Information Extractor
@n8n/n8n-nodes-langchain.informationExtractor - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Airtable
n8n-nodes-base.airtable - Airtable Trigger
n8n-nodes-base.airtableTrigger - Switch
n8n-nodes-base.switch - GraphQL
n8n-nodes-base.graphql - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Remove Duplicates
n8n-nodes-base.removeDuplicates - Slack
n8n-nodes-base.slack
From the author
This n8n template monitors active support issues in Linear.app to track the mood of their ongoing conversation between reporter and assignee using Sentiment Analysis. When sentiment dips into the negative, a notification is sent via Slack to alert the team.…