Automate Instagram complaint handling with Claude AI, tickets & SLA management

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

Important notice

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

1. Workflow Overview

This enterprise grade n8n workflow automates the Instagram complaint handling process — from detection to resolution — using Claude AI , dynamic ticket assignment, and SLA enforcement. It converts ...

Best for

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

Tools used

n8n-nodes-base.cron, n8n-nodes-base.httprequest, n8n-nodes-base.splitinbatches, n8n-nodes-base.set, n8n-nodes-base.if, n8n-nodes-base.googlesheets, n8n-nodes-base.slack, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Oneclick AI Squad.

Original n8n.io source

1.1 Workflow description

Title: Automate Instagram complaint handling with Claude AI, tickets & SLA management
Workflow name: Automate Instagram complaint handling with Claude AI, tickets & SLA management

This enterprise-grade n8n workflow automates the Instagram complaint handling process — from detection to resolution — using Claude AI, dynamic ticket assignment, and SLA enforcement. It converts customer complaints in comments into actionable support tickets with auto-assignment, escalation alerts, and full audit trails, ensuring timely responses and improved customer satisfaction with zero manual intervention.

Key Features

Real-time Instagram polling for new comments
AI-powered complaint detection using Claude 3.5 Sonnet for sentiment and issue classification
Automatic ticket creation in Google Sheets (or integrable with Zendesk/Jira)
Round-robin assignment to team members from a dynamic roster
SLA timer and monitoring (e.g., 24-hour response window with escalation at 80% elapsed)
Escalation engine notifies managers via Slack if near breach
Multi-channel notifications: Slack for assignees and escalations
Audit-ready: Logs ticket details, assignments, and actions
Scalable triggers: Webhook or scheduled polling

Workflow Process

Step	Node	Description
1	Schedule Trigger	Runs every 15 minutes or via webhook (`/complaint-handler`)
2	Get Instagram Posts	Fetches recent posts from Instagram Graph API
3	Get Comments	Retrieves comments for the latest post
4	Loop Over Comments	Processes each comment individually to avoid rate limits
5	Detect Complaint (Claude AI)	Uses AI to classify if complaint, extract issue/severity
6	IF Complaint	Branches: Proceed if yes, end if no
7	Get Team Members	Loads team roster from `TeamMembers` sheet
8	Assign Ticket	Sets assignee via round-robin logic
9	Create Ticket (Google Sheet)	Appends new ticket with details and SLA due date
10	Notify Assignee (Slack)	Alerts assigned team member
11	Wait for SLA Check	Delays to near-SLA-breach point (e.g., 20 hours)
12	Check Ticket Status	Looks up ticket status in sheet
13	IF SLA Breach Near	Checks if unresolved; escalates if yes
14	Escalate to Manager (Slack)	Notifies manager for urgent action
15	End (Non-Complaint Path)	Terminates non-complaint branches

Setup Instructions

1. Import Workflow

Open n8n → Workflows → Import from Clipboard
Paste the JSON workflow

2. Configure Credentials

Integration	Details
Instagram API	Access token from Facebook Developer Portal
Claude AI	Anthropic API key for `claude-3-5-sonnet-20241022`
Google Sheets	Service account with spreadsheet access
Slack	Webhook or OAuth app

3. Update Spreadsheet IDs

Ensure your Google Sheets include:

SupportTickets
TeamMembers

4. Set Triggers

Webhook: /webhook/complaint-handler (for real-time Instagram notifications if set up)
Schedule: Every 15 minutes

5. Run a Test

Use manual execution to confirm:

Ticket creation in sheet
Slack notifications
SLA wait and escalation logic (simulate by shortening wait time)

Google Sheets Structure

SupportTickets

ticketId	commentText	user	createdAt	assignedTo	status	slaDue	issueType	severity
TKT-12345678	Sample complaint text	user123	2023-10-01T12:00:00Z	[email protected]	Open	2023-10-02T12:00:00Z	Product Issue	Medium

TeamMembers

name	email
John Doe	[email protected]
Jane Smith	[email protected]

System Requirements

Requirement	Version/Access
n8n	v1.50+ (AI integrations supported)
Claude AI API	`claude-3-5-sonnet-20241022`
Instagram Graph API	Business account access token
Google Sheets API	`https://www.googleapis.com/auth/spreadsheets`
Slack Webhook	Required for notifications

Optional Enhancements

Integrate Zendesk/Jira for professional ticketing instead of Google Sheets
Add email notifications to customers acknowledging complaints
Use sentiment thresholds for prioritizing high-severity tickets
Connect Twilio for SMS escalations
Enable multi-platform support (e.g., Twitter/Facebook comments)
Add reporting dashboard via Google Data Studio
Implement auto-resolution for simple complaints using AI responses

Result: A single automated system that detects, tickets, assigns, and enforces SLAs on Instagram complaints — with full AI intelligence and zero manual work.

Explore More AI Workflows: Get in touch with us for custom n8n automation!

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

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

Block 2 - Get Instagram Posts

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

Block 3 - Get Comments

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

Block 4 - Loop Over Comments

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

Block 5 - Capture Original Comment

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

Block 6 - Detect Complaint (Claude AI)

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

Block 7 - IF Complaint

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

Block 8 - Check Ticket Status

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

Block 9 - IF SLA Breach Near

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

Block 10 - Escalate to Manager (Slack)

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

Block 11 - End (Non-Complaint Path)

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

Block 12 - Create Ticket (Google Sheet)

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

Block 13 - Get Team Members

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

Block 14 - Assign Ticket

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

Block 15 - Notify Assignee (Slack)

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

Block 16 - Wait for SLA Check

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

Block 17 - Webhook

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

Block 18 - Sticky Note

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

Block 19 - Sticky Note1

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

Block 20 - Sticky Note2

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

Block 21 - Sticky Note3

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

Block 22 - Sticky Note4

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

Block 23 - Sticky Note5

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

Block 24 - Sticky Note6

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

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

3. Summary Table

Workflow	Automate Instagram complaint handling with Claude AI, tickets & SLA management
Complexity	advanced
Nodes	31
Categories	Ticket Management, AI Summarization
Author	Oneclick AI Squad
Published	30 Oct 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/10324/10324.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 Automate Instagram complaint handling with Claude AI, tickets & SLA management 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.

Oneclick AI Squad

224 workflows

Nodes

n8n-nodes-base.cron n8n-nodes-base.httprequest n8n-nodes-base.splitinbatches n8n-nodes-base.set n8n-nodes-base.if n8n-nodes-base.googlesheets n8n-nodes-base.slack n8n-nodes-base.wait

Complexity

advanced

Published 30 Oct 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/10324/10324.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.

Automate Instagram complaint handling with Claude AI, tickets & SLA management

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Key Features

Workflow Process

Setup Instructions

1. Import Workflow

2. Configure Credentials

3. Update Spreadsheet IDs

4. Set Triggers

5. Run a Test

Google Sheets Structure

SupportTickets

TeamMembers

System Requirements

Optional Enhancements

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Block 2 - Get Instagram Posts

Block 3 - Get Comments

Block 4 - Loop Over Comments

Block 5 - Capture Original Comment

Block 6 - Detect Complaint (Claude AI)

Block 7 - IF Complaint

Block 8 - Check Ticket Status

Block 9 - IF SLA Breach Near

Block 10 - Escalate to Manager (Slack)

Block 11 - End (Non-Complaint Path)

Block 12 - Create Ticket (Google Sheet)

Block 13 - Get Team Members

Block 14 - Assign Ticket

Block 15 - Notify Assignee (Slack)

Block 16 - Wait for SLA Check

Block 17 - Webhook

Block 18 - Sticky Note

Block 19 - Sticky Note1

Block 20 - Sticky Note2

Block 21 - Sticky Note3

Block 22 - Sticky Note4

Block 23 - Sticky Note5

Block 24 - Sticky Note6

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