Noco Kanban Board with AI Prioritization
Configured with Agent, Aggregate, Email Send, Form Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Transform
- Data store
- Routing
- 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 |
|---|---|---|---|
| Incident Form | Trigger | Form Trigger | See node parameters |
| Assign Category | AI & models | Agent | See node parameters |
| OpenAI Chat Model1 | AI & models | OpenAI Chat Model | See node parameters |
| Structure Output Todoist Ready1 | Transform | Output Parser Structured | See node parameters |
| Get incident definitions | Data store | Noco Db | getAll |
| Insert Incident | Data store | Noco Db | create |
| Aggregate for AI parsing | Transform | Aggregate | See node parameters |
| On schedule or during flow | Routing | No Op | See node parameters |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Task is not picked up after expected response | Routing | If | See node parameters |
| Send email to client | Messaging | Email Send | See node parameters |
| Check status every day | Trigger | Schedule Trigger | See node parameters |
| Send email to asignee | Messaging | Email Send | See node parameters |
| Get Unpicked Tasks | Data store | Noco Db | getAll |
| Get Unfinished Tasks | Data store | Noco Db | getAll |
| Task is not complete in expected time | Routing | If | See node parameters |
| Send email to client1 | Messaging | Email Send | See node parameters |
| If there is asignee email | Routing | If | See node parameters |
| If there is assignee slack | Routing | If | See node parameters |
| Slack to assignee | Messaging | Slack | See node parameters |
| Send another email to asignee | Messaging | Email Send | See node parameters |
| Format for Noco | Transform | Edit Fields | 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
nocoDbApiTokenopenAiApislackOAuth2Apismtp
Workflow notes
Incident Form
Incident Form
This workflow is triggered when someone fills incident form. You could replace it for example with email or webhook, but you will need to update references in other nodes to new fields
Parse Incidents
Parse Incidents
Allow AI to compare your incident definitions with input from user. AI will attempt to assign proper category and proper person to given incident. WIth AI assignment, we are formatting fields to input them into NocoDB table
Stay Informed
Stay Informed
Inform both client and developer about current task status. Maybe task was not picked up. Feel free to replace with Slack messages if applicable
Task incomplete
Task incomplete
Inform both client and developer that task is after due. Developer should receive message and react accordingly.
Trigger Task Check Daily
Trigger Task Check Daily
Running this more often is probably not good idea because client may receive too many messages when task is delayed
Noco Kanban Board with AI Prioritization
Noco Kanban Board with AI Prioritization
Purpose and structure
This folder contains the Noco Kanban Board with AI Prioritization workflow. Its executable nodes use agent, aggregate, emailSend, formTrigger, if, lmChatOpenAi, manualTrigger, noOp, nocoDb, 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
Incident Form, When clicking ‘Test workflow’, Check status every day
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/1418_Schedule_Nocodb_Automation_Scheduled.json MIT; preserve source notices.