Collect incident reports with a simple form, sort them with AI, and store clean tickets in NocoDB. Clients and assignees get clear updates, while your team tracks response and resolution times without manual effort. Built for IT and support teams that need fast routing and reliable follow up.

After a form submission, the flow pulls incident definitions from NocoDB. An AI model compares the user description with those definitions and returns category, response time, resolution time, and default assignee in a structured format. Mapped fields are saved to your incidents table in NocoDB. A daily schedule checks for tickets not picked up in time and tasks past the due time. If rules match, the client and assignee get emails, and the assignee also gets a Slack message when a Slack contact exists. A manual trigger is included for safe testing.

Connect OpenAI, NocoDB, SMTP email, and Slack before you start. Point the NocoDB nodes to your tables and columns, and confirm the form fields match your schema. Run the daily check at a calm pace so clients do not receive too many reminders. Teams often cut triage from thirty minutes to two minutes and reduce missed SLAs with steady alerts. Ideal for IT help desks, software teams, and internal service desks.

• Form intake collects email and incident description to start the flow
• NocoDB getAll loads definitions with response time, resolution time, and default assignee
• Aggregate step compiles definitions so the AI can compare them with the user text
• OpenAI chat model returns category and SLA values in a structured format
• Structured output parser enforces the exact JSON fields needed for storage
• Field mapping prepares clean records for the NocoDB incidents table
• Daily schedule checks for unpicked and overdue tasks against expected times
• Conditional logic flags delays and triggers the right notifications
• SMTP emails notify clients and assignees with clear status updates
• Slack messages alert the assignee when a Slack contact is available

• Reduce manual triage from thirty minutes to two minutes
• Automate up to 90 percent of ticket routing with AI
• Improve data quality by 30 percent using structured fields in NocoDB
• Cut missed SLAs by 50 percent with daily checks and alerts
• Connect NocoDB, email, and Slack in one flow
• Handle three times more incidents without extra headcount

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with OpenAI, NocoDB, Slack and SMTP. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create an OpenAI credential. Add your API key from the OpenAI website. Double click the OpenAI node, choose your credential, and save.
4. In NocoDB, create a project and tables for Incident Definitions and Incidents. Note the project ID and table IDs. In n8n, create a NocoDB Token credential with your API token, then select it on all NocoDB nodes.
5. Open the Form Trigger node. Confirm it has fields for Email and Incident Description. Copy the form URL and submit a test entry later for validation.
6. Open the Get incident definitions node. Point it to your definitions table and select fields Title, Definition, Response time, Resolution time, and Default assignee. Enable return all records.
7. Check the Assign Category node and the structured output parser. Ensure the schema includes category, response_time, resolution_time, and default_assignee so the AI output matches your NocoDB columns.
8. Open the Format for Noco and Insert Incident nodes. Map email, category, response time, resolution time, and assignee to the correct NocoDB columns. Save your changes.
9. Set up SMTP. In the credentials manager, create an SMTP credential with host, port, username, and password from your email provider. Select it in all email nodes and set the from email address.
10. Set up Slack. In the credentials manager, create a Slack OAuth2 credential. Authorize your workspace. Choose this credential in the Slack message node.
11. Open the Check status every day node and set the schedule to once per day. Avoid very frequent checks so clients do not receive too many reminders.
12. Review the If conditions for unpicked and overdue tasks. Adjust filters in the Get Unpicked Tasks and Get Unfinished Tasks nodes so they match your SLA rules.
13. Test the flow. Use the manual trigger to run the check path, then submit the form once. Confirm the incident appears in NocoDB and that emails or Slack messages are delivered.
14. Troubleshoot common issues. If NocoDB returns unauthorized, verify the API token and project ID. If emails fail, confirm SMTP TLS and ports. If AI output is missing fields, refine the prompt or schema in the parser. If Slack fails, reauthorize the Slack credential.