Shopify AI Support Agent

This workflow is built from 24 nodes. Here's what each one does:

#	Node	Type	What it does
1	New Support Email	Gmail Trigger	Starts the workflow when a new email arrives in Gmail.
2	CONFIG — Shop	Set	Holds editable configuration values — fill in your own settings here before activating.
3	Extract Order Number	Code	Runs custom JavaScript to transform, filter, or compute data between steps.
4	Log Email — RECEIVED	Google Sheets	Reads from or writes to a Google Sheet — this workflow's log and state store.
5	Shopify — Get Order	Shopify	Reads or updates data in your Shopify store.
6	Merge Order Context	Code	Runs custom JavaScript to transform, filter, or compute data between steps.
7	CONFIG — AI	Set	Holds editable configuration values — fill in your own settings here before activating.
8	AI Agent — Triage Support Email	AI Agent	The AI brain — reasons over the task and calls tools to get it done.
9	OpenAI Chat Model — Triage	OpenAI Chat Model	The language model powering the AI agent.
10	Structured Output Parser — Triage	Structured Output Parser	Forces the AI to return clean, structured JSON instead of free text.
11	Compute Routing	Code	Runs custom JavaScript to transform, filter, or compute data between steps.
12	Update Sheet — TRIAGED	Google Sheets	Reads from or writes to a Google Sheet — this workflow's log and state store.
13	CONFIG — Notifications	Set	Holds editable configuration values — fill in your own settings here before activating.
14	IF — Auto-Resolvable?	IF	Splits the flow into branches based on a condition.
15	Gmail — Send Reply	Gmail	Sends or reads email through your Gmail account.
16	Update Sheet — AUTO_RESOLVED	Google Sheets	Reads from or writes to a Google Sheet — this workflow's log and state store.
17	IF — Money Involved?	IF	Splits the flow into branches based on a condition.
18	Gmail — Create Draft for Human	Gmail	Sends or reads email through your Gmail account.
19	Update Sheet — DRAFT_CREATED	Google Sheets	Reads from or writes to a Google Sheet — this workflow's log and state store.
20	Slack — Alert Support Channel	Slack	Posts messages or reads data in Slack.
21	Update Sheet — ESCALATED	Google Sheets	Reads from or writes to a Google Sheet — this workflow's log and state store.
22	Merge — Combine Branches	Merge	Combines the outputs of two or more branches back into one flow.
23	Build Summary	Code	Runs custom JavaScript to transform, filter, or compute data between steps.
24	Telegram — Send Summary	Telegram	Sends you a Telegram message or alert.

1. Add your credentials

In n8n go to Credentials → New, create each credential below, then open the named node and select it:

Node	Credential to add
New Support Email	Gmail OAuth2
Log Email — RECEIVED	Google Sheets OAuth2
Shopify — Get Order	Shopify API
OpenAI Chat Model — Triage	OpenAI API
Update Sheet — TRIAGED	Google Sheets OAuth2
Gmail — Send Reply	Gmail OAuth2
Update Sheet — AUTO_RESOLVED	Google Sheets OAuth2
Gmail — Create Draft for Human	Gmail OAuth2
Update Sheet — DRAFT_CREATED	Google Sheets OAuth2
Slack — Alert Support Channel	Slack API (token)
Update Sheet — ESCALATED	Google Sheets OAuth2
Telegram — Send Summary	Telegram Bot API

2. Fill in your config values

Open the config node listed below and replace each placeholder with your own value before activating the workflow:

Node	Field	What to paste
CONFIG — Shop	shop_domain	PASTE_YOUR_SHOP_DOMAIN Your shop domain
CONFIG — Shop	support_email	PASTE_YOUR_SUPPORT_EMAIL Your support email
CONFIG — Notifications	telegram_chat_id	PASTE_YOUR_TELEGRAM_CHAT_ID Your telegram chat id
CONFIG — Notifications	slack_channel	PASTE_YOUR_SLACK_CHANNEL Your slack channel

How this workflow starts

• Gmail Trigger: Fires automatically on its event — activate the workflow and connect the service.

Support email for a Shopify store follows a cruel pattern: most messages are routine, where is my order and shipping questions, and a minority are refund and money questions where one wrong automatic reply costs real money. This template splits the two and never confuses them. A Gmail trigger watches the support inbox every minute. Extract Order Number pulls the order number from the subject or body with a regex, every email is logged to a Support Inbox sheet with status RECEIVED, and Shopify Get Order fetches the real order behind it. Then an AI Agent with a Structured Output Parser returns a strict verdict: intent, a confidence score from 0 to 100, a draft reply, a needs-human flag, and a one-line order summary. Compute Routing turns that verdict into two flags: auto resolvable, meaning a routine intent with confidence at or above the threshold and no human flag, and money involved, meaning a refund or change intent. Auto-resolvable mail gets an instant Gmail reply and the sheet flips to AUTO RESOLVED. Money-involved mail becomes a Gmail draft waiting for a human, and the sheet flips to DRAFT CREATED. Everything else raises a rich Slack alert in the support channel and the sheet flips to ESCALATED. All three branches merge into one Telegram summary with the triaged, auto-resolved, draft, and escalated counts. It is built for store owners who want instant replies without ever letting the AI touch money.

The solo founder buried in where is my order

A founder selling skincare does about 150 orders a day and used to answer email at midnight. Eighty percent of the inbox is order status questions with the order number right in the subject line. The workflow extracts it, Shopify Get Order returns the tracking state, and the AI drafts a correct reply that goes out in under a minute. The confidence threshold in CONFIG Shop starts at 80, so borderline mail falls through to a human.

• Variation: add an Auto Reply Text column to the sheet and write the sent draft into it at Update Sheet AUTO RESOLVED, so there is a permanent audit trail of exactly what the AI told each customer.

The print-on-demand store at four hundred emails a day

A print-on-demand shop selling custom mugs and tees gets crushed every holiday season: hundreds of where is my order and what is your return policy emails daily, mixed with genuine refund requests for misprinted items. The routine intents auto-resolve around the clock, while refund request and order change intents always land as Gmail drafts.

• Variation: raise the confidence threshold to 90 during peak season so the AI answers only when it is very sure, and let the extra volume fall through to drafts rather than risk a bad auto-reply.

The three-person support team protecting its SLAs

A small team supporting a mid-size fashion store has a four-hour first-response SLA and no night shift. The Slack escalation branch is their safety net: anything the AI cannot confidently resolve posts to the support channel with the order summary attached, so the morning shift triages from Slack instead of re-reading the inbox.

• Variation: point the Gmail trigger at a dedicated support address and filter out marketing and newsletter mail before it ever enters the flow, so the AI never wastes a triage on a promo blast.

The international store drowning in shipping questions

A store shipping to forty countries gets the same questions daily: how long to Germany, who pays customs, what if the parcel is stuck. These are policy questions with stable answers, ideal for auto-resolution once the AI has the policy text in its context. Lost-parcel cases, where the answer might involve reshipping at the store's cost, stay firmly in the draft branch: the human sees the AI's draft and the one-line order summary, edits if needed, and sends.

• Variation: extend the parser schema and Compute Routing with a wholesale inquiry intent wired to its own branch, so B2B mail skips the consumer flow entirely.

The new store owner calibrating trust

A first-time founder loves the idea of auto-replies and fears them in equal measure. The template has a built-in calibration mode: remove the auto-reply branch and route everything to drafts while the store is new. Once the scores earn trust, the IF branch goes back on and routine mail starts resolving itself.

• Variation: pre-filter obvious spam with an extra IF on subject keywords before the agent runs, so junk mail never spends OpenAI tokens or pollutes the triage counts.