Skip to main content

Assign Requests Using AI and Send Reminders Based On NocoDB Kanban Board Status

Workflow preview

Workflow preview
100%
Assign Requests Using AI and Send Reminders Based On NocoDB Kanban Board Status preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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...

Best for

  • Ticket Management automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

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

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Łukasz.

Original n8n.io source

1.1 Workflow description

Title
Assign Requests Using AI and Send Reminders Based On NocoDB Kanban Board Status
Workflow name
Assign Requests Using AI and Send Reminders Based On NocoDB Kanban Board Status

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 SLA-like agreement.

It is actually simple incident management board using free Kanban board, that is extended in functionality via N8N.

How It Works?

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.

How to set up?

  • Clone automation
  • Create (samples below) two NocoDB tables: one with definitions and second that servers as Kanban board (mind column naming!)
  • Set up email and slack connection
  • You should be ready to go

Different incident naming

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:

  • NocoDB: Incident definitions, column "Title"
  • NocoDB: Tasks table, single select fields:
    • "expected category"
    • "assigned category"
  • N8N: Incident Form "Incident Desired Category"

NocoDB Tables

Incident definitions table

|Title |Definition |Response time|Resolution time|Default assignee| |single line text|text|number|number|email|

Tasks table

|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|

Use kanban board

Simply set up Kanban view and stack by "status" field.

What's More?

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).

Thank you, perfect!

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!

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Incident Form

Type / Role
n8n-nodes-base.formTrigger - formTrigger
Config choices
Version 2.2

Block 2 - Assign Category

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.8

Block 3 - OpenAI Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 4 - Structure Output Todoist Ready1

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.2

Block 5 - Get incident definitions

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 6 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Insert Incident

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 9 - Aggregate for AI parsing

Type / Role
n8n-nodes-base.aggregate - aggregate
Config choices
Version 1

Block 10 - On schedule or during flow

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 11 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 12 - Task is not picked up after expected response

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 13 - Send email to client

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 14 - Check status every day

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 15 - Send email to asignee

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 16 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Get Unpicked Tasks

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 18 - Get Unfinished Tasks

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 19 - Task is not complete in expected time

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 20 - Send email to client1

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 21 - If there is asignee email

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 22 - If there is assignee slack

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 23 - Slack to assignee

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 24 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

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

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3784/3784.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Assign Requests Using AI and Send Reminders Based On NocoDB Kanban Board Status do?

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...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.