Block 1 - Incident Form
- Type / Role
- n8n-nodes-base.formTrigger - formTrigger
- Config choices
- Version 2.2
This workflow is provided as-is. Please review and test before using in production.
Who is it for? This is automation for support project manager, which helps not only to keep developres informed but also automatically keep clients in the loop especially useful if you are managing...
n8n-nodes-base.formtrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.nocodb, n8n-nodes-base.stickynote, n8n-nodes-base.aggregate, n8n-nodes-base.noop
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Łukasz.
Original n8n.io sourceThis is automation for support project manager, which helps not only to keep developres informed but also automatically keep clients in the loop - especially useful if you are managing SLA-like agreement.
It is actually simple incident management board using free Kanban board, that is extended in functionality via N8N.
Script has two entry points.
The first one is incident form. When incident details are provided, automation gets incident definitions from database and pushes both information to AI. AI comparse definitions with client request, refines incident priority and pushed it in NocoDB database.
Second is schedule trigger, which is responsible for regular notificaitons on task status. If task is not picked up or delivered in proper time, then emails or slack messages are being sent both to client and responsible developer.
If your incident level naming is different, you need to update few nodes and few columns in NocoDB. This is because incident naming must be unified through: automation flow, incident definitions and column NocoDB select fields.
So be sure that following is the same:
|Title |Definition |Response time|Resolution time|Default assignee| |single line text|text|number|number|email|
|email|message|expected category|internal notes|assigned category|status|expected response|expected resolution|assignee|assignee slack| |email|text|single select|text|single select|single select|date and time|date and time|email|slack username|
Simply set up Kanban view and stack by "status" field.
That's actually it. I hope that this automation will help your support line be much more streamlined!
There is actually more that you could do with this automation, but it really depends on your needs. For example, you could add Email trigger to handle incoming support requests (but remember to adjust nodes accordingly). Another thing is that you could make different notification schema, depending on your needs (for example I do imagine that you may want a day or two delay before you notify client that task is after due).
Glad I could help. Visit my profile for other automations for businesses. And if you are looking for dedicated software development, do not hesitate to reach out!
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.
| Workflow | Assign Requests Using AI and Send Reminders Based On NocoDB Kanban Board Status |
|---|---|
| Complexity | advanced |
| Nodes | 27 |
| Categories | Ticket Management, AI Summarization |
| Author | Łukasz |
| Published | 29 Apr 2025 |
Use the JSON export at /data/workflows/3784/3784.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Who is it for? This is automation for support project manager, which helps not only to keep developres informed but also automatically keep clients in the loop especially useful if you are managing...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, AI Summarization use case.