issues to list and sentiment over issue comments and search airtable
Configured with Airtable, Airtable Trigger, Graphql, Information Extractor, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- AI & models
- Routing
- Data store
- Trigger
- Web / API
- Messaging
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| Issues to List | Transform | Split Out | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Combine Sentiment Analysis | Transform | Edit Fields | See node parameters |
| Sentiment over Issue Comments | AI & models | Information Extractor | See node parameters |
| Copy of Issue | Transform | Edit Fields | See node parameters |
| For Each Issue... | Routing | Loop Over Items | See node parameters |
| Get Existing Sentiment | Data store | Airtable | search |
| Update Row | Data store | Airtable | upsert |
| Airtable Trigger | Trigger | Airtable Trigger | See node parameters |
| Sentiment Transition | Routing | Switch | See node parameters |
| Fetch Active Linear Issues | Web / API | Graphql | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Deduplicate Notifications | Transform | Remove Duplicates | removeItemsSeenInPreviousExecutions |
| Report Issue Negative Transition | Messaging | Slack | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
airtableTokenApihttpHeaderAuthopenAiApislackApi
Workflow notes
1. Continuously Monitor Active Linear Issues
1. Continuously Monitor Active Linear Issues
Learn more about the GraphQL node
To keep up with the latest changes in our active Linear tickets, we'll need to use Linear's GraphQL endpoint because filtering is currently unavailable in the official Linear.app node.
For this demonstration, we'll check for updated tickets every 30mins.
2. Sentiment Analysis on Current Issue Activity
2. Sentiment Analysis on Current Issue Activity
Learn more about the Information Extractor node
With our recently updated posts, we can use our AI to perform a quick sentiment analysis on the ongoing conversation to check the overall mood of the support issue. This is a great way to check how things are generally going in the support queue; positive should be normal but negative could indicate some uncomfortableness or even frustration.
3. Capture and Track Results in Airtable
3. Capture and Track Results in Airtable
Learn more about the Airtable node
Next, we can capture this analysis in our insights database as means for human review. When the issue is new, we can create a new row but if the issue exists, we will update it's existing row instead.
When updating an existing row, we move its previous "current sentiment" value into the "previous sentiment" column and replace with our new current sentiment. This gives us a "sentiment transition" which will be useful in the next step.
Check out the Airtable here: https://airtable.com/appViDaeaFw4qv9La/shrq6HgeYzpW6uwXL
4. Get Notified when Sentiment becomes Negative
4. Get Notified when Sentiment becomes Negative
Learn more about the Slack node
A good use-case for tracking sentiment transitions could be to be alerted if ever an issue moves from a non-negative sentiment to a negative one. This could be a signal of issue handling troubles which may require attention before it escalates.
In this demonstration, we use the Airtable trigger to catch rows which have their sentiment column updated and check for the non-negative-to-negative sentiment transition using the switch node. For those matching rows, we combine add send a notification via slack. A cool trick is to use the "remove duplication" node to prevent repeat notifications for the same updates - here we combine the Linear issue key and the row's last modified date.
Try It Out!
Try It Out!
This n8n template performs continous monitoring on Linear Issue conversations performing sentiment analysis and alerting when the sentiment becomes negative.
This is helpful to quickly identify difficult customer support situations early and prioritising them before they get out of hand.
How it works
- A scheduled trigger is used to fetch recently updated issues in Linear using the GraphQL node.
- Each issue's comments thread is passed into a simple Information Extractor node to identify the overall sentiment.
- The resulting sentiment analysis combined with the some issue details are uploaded to Airtable for review.
- When the template is re-run at a later date, each issue is re-analysed for sentiment
- Each issue's new sentiment state is saved to the airtable whilst its previous state is moved to the "previous sentiment" column.
- An Airtable trigger is used to watch for recently updated rows
- Each matching Airtable row is filtered to check if it has a previous non-negative state but now has a negative state in its current sentiment.
- The results are sent via notification to a team slack channel for priority.
Check out the sample Airtable here: https://airtable.com/appViDaeaFw4qv9La/shrq6HgeYzpW6uwXL
How to use
- Modify the GraphQL filter to fetch issues to a relevant issue type, team or person.
- Update the Slack channel to ensure messages are sent to the correct location.
Need Help?
Join the Discord or ask in the Forum!
Happy Hacking!
issues to list and sentiment over issue comments and search airtable
issues to list and sentiment over issue comments and search airtable
Purpose and structure
This folder contains the issues to list and sentiment over issue comments and search airtable workflow. Its executable nodes use airtable, airtableTrigger, graphql, informationExtractor, lmChatOpenAi, removeDuplicates, scheduleTrigger, set, slack, splitInBatches, splitOut, switch. 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
Airtable Trigger, 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/Splitout/0663_Splitout_Schedule_Update_Scheduled.json MIT; preserve source notices.