--- title: "Gorgias support reply writer" type: "skill" url: "https://useaiblocks.com/skills/gorgias-support-reply-writer" updated: "2026-10-28" first_published: "2026-10-25" job: "Help your customers" tested: true licence: "MIT" source: "https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/draft-reply" instructions: "https://useaiblocks.com/skills/gorgias-support-reply-writer/SKILL.md" --- # Gorgias support reply writer > Share a Gorgias ticket number. Get a reply based on the recorded thread, ready to review or save as a Gmail draft. Use a Composio setup linked to Gorgias, plus Gmail if you want a saved draft. It reads the returned ticket thread, earlier replies and open questions, then writes a short support response. Missing facts stay visible. Review the text before choosing to create a Gmail draft; a draft is not a sent email. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-support-reply-writer - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-support-reply-writer/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-support-reply-writer.zip - JSON version: https://useaiblocks.com/skills/gorgias-support-reply-writer.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-support-reply-writer" ## What you give it - A Gorgias ticket number. - Your Gorgias account, linked through the Composio CLI. - Your Gmail account, linked the same way (optional). ## What you get - A short summary of the ticket thread. - A draft reply that answers each open question and names the next step. - Options to edit the reply or change its tone. - A Gmail draft, saved only if you choose that. ## Example: what goes in and what comes out ### What goes in - Your Gorgias ticket number - Your Gorgias account, connected through the Composio CLI - Your Gmail account, only if you want a saved draft (optional) ### Before you start - An AI that can run commands in a terminal - The Composio CLI installed, with Gorgias linked - Gmail linked in Composio, only for saving drafts ### What comes out - **Ticket header**: The ticket number, subject, customer name and email, status, message count and time of the last customer message. - **Conversation Summary**: A two or three sentence summary of the thread so far. - **Draft Reply**: A warm, short reply with a subject line that answers each point in the customer's latest message. - **Options**: Three choices: save as a Gmail draft, edit the reply, or rewrite it in a formal, casual or technical tone. - **Gmail draft (optional)**: A draft saved in your inbox, made only after you approve the text. ## Use it when - You have a Gorgias ticket with a customer question that needs a reply today. - A long thread has gone back and forth and you need a reply that answers every open point. - You want a draft reply saved in Gmail for a teammate to check before it goes out. ## Skip it when - You need a refund or account change approved. Ask a person to make that call first, then write the reply. - You answer a simple FAQ question. Use your helpdesk's own saved replies (macros) in Gorgias instead. - You have no Gorgias account or no way to connect it. Paste the thread into your AI and ask for a reply by hand. ## How to use it 1. Gather first: the ticket number, and the Gorgias and Gmail accounts you will link. You need an AI that can run terminal commands and read skill files, and the Composio CLI installed. Gorgias is a paid help desk. Composio may charge for use, so check its pricing first. 2. Link your Gorgias account with the command composio link gorgias. Link Gmail too if you want drafts. 3. Ask your AI to run the Gorgias support reply writer with your ticket number. 4. Read the summary and the draft. Check every fact against what you know is true. The draft does not promise refunds, dates or account changes the thread has not confirmed. It marks them CHECK for you to decide. 5. Ask for edits or a different tone until it sounds right. 6. Choose the Gmail option only when you are happy. Then send the draft yourself from Gmail. ## What to do next - [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer): Support ticket help article writer ## Sources and credits - From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/draft-reply, shared under the MIT licence (original name: draft-reply). - [draft-reply skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/draft-reply), Composio: Copied under the MIT licence. We gave it a plain name and added a rule that the draft makes no promises the thread does not confirm. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Draft Support Reply You are an expert customer support agent. Given a [Gorgias](https://composio.dev/toolkits/gorgias) ticket ID, analyze the full conversation and draft a professional, empathetic reply. Optionally create it as a [Gmail](https://composio.dev/toolkits/gmail) draft. The user's input is: $ARGUMENTS ### Before you start Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait. **What you need** (use your own material or the linked skill): - **Your question** (yours): the decision or problem, and what a good outcome looks like. - **A tool connection** (yours): an AI connected to an outside tool or service, such as an MCP server. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name. 2. **Check what's missing.** Look for your question, a tool connection. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps. 3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. **Tools that do this best:** - **Gorgias; Gmail for optional drafts:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "get support ticket details and messages from Gorgias" "create an email draft in Gmail"` in Bash. #### Step 2: Get tool schemas Run `composio execute --get-schema` in Bash (in parallel) for: - `GORGIAS_GET_TICKET` - `GMAIL_CREATE_EMAIL_DRAFT` #### Step 3: Fetch ticket context Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` in Bash. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry. Parse the JSON output and extract: - Full message thread (all customer and agent messages) - Customer name and email - Ticket subject and tags - Current status and assignee #### Step 4: Analyze and draft Analyze the conversation to understand: - What the customer is asking/reporting - What has already been tried or communicated - The customer's emotional state (frustrated, confused, patient, etc.) - Any unresolved questions Draft a reply following these principles: - **Acknowledge** the customer's situation and any frustration - **Address** each point/question raised in their latest message - **Provide** clear, actionable next steps - **Tone:** Professional but warm, never robotic - **Length:** Concise - respect the customer's time - **No new promises:** Do not promise a refund, date, policy or account change that the thread does not already confirm. If the reply seems to need one, write [CHECK: ...] in its place and point it out to the user. - If you don't have enough info to fully resolve, explain what you need #### Step 5: Present the draft ``` ## Ticket #[ID]: [Subject] **Customer:** [Name] <[email]> **Status:** [status] | **Messages:** [count] **Last customer message:** [timestamp] ### Conversation Summary [2-3 sentence summary of the thread] ### Draft Reply --- Subject: Re: [original subject] [The drafted reply text] --- ### Options 1. Send as Gmail draft (will create a draft in your inbox) 2. Edit the reply (tell me what to change) 3. Regenerate with different tone (formal/casual/technical) ``` #### Step 6: Execute (on user choice) If the user chooses to create a Gmail draft: - Run `composio execute GMAIL_CREATE_EMAIL_DRAFT -d '{"to":"","subject":"Re: ","body":""}'` in Bash - Parse the JSON output and confirm the draft was created with a link if available ### After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - The [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer). It takes the draft. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.