Production AI Playbook: Deterministic Steps & AI Steps (5 of 5)

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

The full end to end workflow that chains all patterns together. This template processes customer feedback from intake to team routing, with normalization, validation, native guardrails, AI classifi...

Best for

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

Tools used

n8n-nodes-base.respondtowebhook, n8n-nodes-base.code, n8n-nodes-base.switch, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.webhook, @n8n/n8n-nodes-langchain.guardrails, @n8n/n8n-nodes-langchain.lmchatopenai

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Production AI Playbook: Deterministic Steps & AI Steps (5 of 5)
Workflow name: Production AI Playbook: Deterministic Steps & AI Steps (5 of 5)

The full end-to-end workflow that chains all patterns together. This template processes customer feedback from intake to team routing, with normalization, validation, native guardrails, AI classification, and confidence-based branching at every step.

What you'll do

Send customer feedback through a webhook and watch it flow through every stage.
See the data get normalized, validated, and scanned by n8n's native Guardrails node for jailbreak attempts and PII.
Watch the AI classify feedback (bug report, feature request, praise, complaint, question) with a confidence score and generate a personalized response draft.
See AI-generated responses pass through output guardrails that check for NSFW content and secret keys before reaching users.
Watch high-confidence results route automatically: bug reports and feature requests to the product team, complaints to customer success, and praise to marketing as testimonial candidates.

What you'll learn

How to chain normalization, validation, native guardrails, AI, and routing into a single pipeline
How to use n8n's Guardrails node for both input screening (jailbreak, PII, secret keys) and output screening (NSFW, secret keys)
How confidence-based branching separates high-confidence results from items that need human review
How Switch nodes route classified feedback to the right destination (product team, customer success, or marketing)
How every step between AI nodes is deterministic and inspectable
How all these patterns work together in a production-ready workflow

Why it matters This is the complete picture. Individual patterns are useful on their own, but the real power comes from combining them into a pipeline where AI handles the judgment calls and everything else follows explicit, testable rules. Import this template as your starting point and connect your own integrations.

This template is a learning companion to the Production AI Playbook, a series that explores strategies, shares best practices, and provides practical examples for building reliable AI systems in n8n.

https://go.n8n.io/PAP-D&A-Blog

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

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.1

Block 2 - Queue for Human Review

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 3 - Flag as Testimonial

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 4 - Escalate to CS

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 5 - Add to Backlog

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 6 - Create Jira Ticket

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 7 - Route by Type

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.2

Block 8 - High Confidence + Valid?

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

Block 9 - AI - Classify + Draft

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

Block 10 - Respond - Missing Fields

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.1

Block 11 - Has Required Fields?

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

Block 12 - Normalize Feedback

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 13 - Webhook - Feedback Intake

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2

Block 14 - Input Guardrails

Type / Role: @n8n/n8n-nodes-langchain.guardrails - guardrails
Config choices: Version 1

Block 15 - Input Guardrails LLM

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

Block 16 - Validate AI Output

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 17 - Output Guardrails

Type / Role: @n8n/n8n-nodes-langchain.guardrails - guardrails
Config choices: Version 1

Block 18 - Respond - Input Blocked

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.1

Block 19 - OpenRouter Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 20 - OpenRouter Chat Model1

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 21 - Respond - Output Blocked

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.1

Block 22 - Sticky Note

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

Block 23 - Sticky Note1

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

Block 24 - Sticky Note2

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	Production AI Playbook: Deterministic Steps & AI Steps (5 of 5)
Complexity	advanced
Nodes	27
Categories	Ticket Management, AI Summarization
Author	Elvis Sarvia
Published	04 Mar 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/13855/13855.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Ticket Management workflows AI Summarization workflows

Frequently asked questions

What does Production AI Playbook: Deterministic Steps & AI Steps (5 of 5) do?

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.

Elvis Sarvia

18 workflows

Nodes

n8n-nodes-base.respondtowebhook n8n-nodes-base.code n8n-nodes-base.switch n8n-nodes-base.if @n8n/n8n-nodes-langchain.agent n8n-nodes-base.webhook @n8n/n8n-nodes-langchain.guardrails @n8n/n8n-nodes-langchain.lmchatopenai

Complexity

advanced

Published 04 Mar 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/13855/13855.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

## Quick Overview This workflow uses Google Sheets, OpenAI, Telegram, and Slack to send post-therapy check-in messages, analyze patient replies for sentiment and risk, alert therapists to at-risk responses, and log non-urgent replies for ongoing wellness tracking. ## How it works 1. Runs every hour on a schedule trigger. 2. Reads session records from Google Sheets and keeps only sessions that have a session date and have not been marked as check-in sent. 3. Uses OpenAI (gpt-4o-mini) to generate a personalized, non-clinical Telegram check-in message from the patient’s session details. 4. Sends the check-in to the patient via Telegram and updates the Google Sheets session row to store the message and mark the check-in as sent. 5. Triggers on incoming Telegram messages, looks up the patient in a Google Sheets master list by Telegram ID, and selects the most relevant recent session to provide context. 6. Sends the patient reply and session context to OpenAI for JSON-formatted sentiment classification and parses the result into structured fields. 7. If the sentiment is classified as at-risk, posts an urgent alert to a Slack channel; otherwise, appends the reply and sentiment details to a Google Sheets wellness log. ## Setup 1. Connect Google Sheets OAuth credentials and update the spreadsheet document ID and sheet names for Sessions, Patients_Master, and Wellness_Log. 2. Create and connect a Telegram bot credential, set up the Telegram trigger webhook, and ensure patient Telegram chat IDs are stored in Google Sheets. 3. Add an OpenAI API key credential and confirm the selected model (gpt-4o-mini) meets your requirements. 4. Connect Slack OAuth credentials and replace the placeholder Slack channel ID used for therapist alerts, and confirm the error-alert channel is set correctly. 5. Verify your Google Sheets columns match the workflow’s expected fields (for example session_id, checkin_sent, checkin_message_sent, therapist_slack_id) before activating.

View

Detect and route customer escalations with Claude, Slack and Linear

## Quick Overview This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and severity, then posts alerts to Slack and creates Linear tickets for actionable cases. ## How it works 1. Receives an inbound support message via a POST webhook. 2. Normalizes the incoming payload (Gmail, Zendesk, Intercom, HelpScout, or a raw test payload) into a consistent schema with customer details, subject, body text, and a source URL. 3. Sends the normalized message to Anthropic Claude and parses the response into structured JSON containing escalation flags, severity, trigger phrases, a summary, and a suggested reply opening. 4. Stops processing silently when the message is not an escalation (severity is none). 5. Builds a formatted Slack alert and Linear issue payload, including SLA guidance, detected signals, and links back to the original conversation. 6. Posts the escalation alert to a configured Slack channel. 7. Creates a Linear ticket for critical, high, and medium severity escalations and sends a Slack DM to a manager for critical and high cases. ## Setup 1. Add an Anthropic API credential for the Anthropic Chat Model node. 2. Add a Slack OAuth2 credential, set the target channel (for example, #escalations), and set the manager’s Slack user ID for direct messages. 3. Add a Linear OAuth2 credential and replace the placeholder Linear team ID used when creating tickets. 4. Copy the webhook URL from the webhook trigger and configure Gmail/Zendesk/Intercom/HelpScout (or your custom source) to POST message payloads to it in one of the supported formats.

View

Triage construction incidents with GPT-4o, Slack, Gmail and Google Sheets

## Quick Overview This workflow ingests construction incident webhooks, normalizes the payload, and uses OpenAI GPT-4o-mini to classify each incident by type and urgency, then routes alerts to Slack and Gmail and logs incidents to Google Sheets, with a daily Slack digest generated from the sheet. ## How it works 1. Receives an incoming incident via a POST webhook. 2. Normalizes the incoming Procore/Fieldwire-style payload into a consistent incident object (ID, title, description, location, reporter, assignee, and timestamps). 3. Sends the incident details to OpenAI (GPT-4o-mini) to classify issue type and urgency and generate a short summary, recommended action, and tags. 4. Routes incidents by urgency, sending Critical incidents to Slack with an @channel mention and emailing details to a project manager via Gmail. 5. Sends High-urgency incidents to Slack as a formatted notice. 6. Appends every incident to a Google Sheets log with status set to open. 7. Runs daily at 18:00 server time, reads the incident log from Google Sheets, builds an urgency-grouped digest, and posts it to a Slack channel. ## Setup 1. Add credentials for OpenAI, Slack (OAuth2), Gmail (OAuth2), and Google Sheets (OAuth2). 2. Copy the webhook URL from the Webhook trigger and register it in your source system (for example, Procore or Fieldwire) as the incident-created endpoint. 3. Replace the placeholder Slack channel IDs for Critical, High, Digest, and Error alerts. 4. Update the Gmail recipient address ([email protected]) to your real project manager email. 5. Set the Google Sheets spreadsheet (document ID) and ensure the target sheet exists with columns that match the incident log fields used by the workflow. 6. Confirm the schedule trigger time (cron: 0 18 * * *) matches your desired timezone/server time for the daily digest.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Production AI Playbook: Deterministic Steps & AI Steps (5 of 5)

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Respond - Result

Block 2 - Queue for Human Review

Block 3 - Flag as Testimonial

Block 4 - Escalate to CS

Block 5 - Add to Backlog

Block 6 - Create Jira Ticket

Block 7 - Route by Type

Block 8 - High Confidence + Valid?

Block 9 - AI - Classify + Draft

Block 10 - Respond - Missing Fields

Block 11 - Has Required Fields?

Block 12 - Normalize Feedback

Block 13 - Webhook - Feedback Intake

Block 14 - Input Guardrails

Block 15 - Input Guardrails LLM

Block 16 - Validate AI Output

Block 17 - Output Guardrails

Block 18 - Respond - Input Blocked

Block 19 - OpenRouter Chat Model

Block 20 - OpenRouter Chat Model1

Block 21 - Respond - Output Blocked

Block 22 - Sticky Note

Block 23 - Sticky Note1

Block 24 - Sticky Note2

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions