--- title: "Gorgias to Linear issue planner" type: "skill" url: "https://useaiblocks.com/skills/gorgias-to-linear-issue-handover" 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/escalate" instructions: "https://useaiblocks.com/skills/gorgias-to-linear-issue-handover/SKILL.md" --- # Gorgias to Linear issue planner > Share a support ticket or problem. Review a Linear issue draft and Slack alert, then approve the handover. Use a Composio setup linked to Linear and Slack, plus Gorgias for ticket input. It gathers the known problem, finds a team and channel, and shows both drafts for approval. It then creates the issue and uses its returned link in the alert. Check each result separately; an issue may exist even if the Slack step fails. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-to-linear-issue-handover - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-to-linear-issue-handover/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-to-linear-issue-handover.zip - JSON version: https://useaiblocks.com/skills/gorgias-to-linear-issue-handover.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-to-linear-issue-handover" ## What you give it - A Gorgias ticket number or a clear problem description. - The intended Linear team and Slack channel. ## What you get - A plan to approve first, with the issue title, team, priority and Slack message. - A Linear issue created after you approve. - A Slack alert that includes the Linear issue link. - A short report with the links and next steps. ## Example: what goes in and what comes out ### What goes in - A Gorgias ticket number, or a short description of the problem - The Linear team that should get the issue (optional) - The Slack channel for the alert (optional) ### Before you start - An AI that can run Composio CLI commands - Gorgias, Linear and Slack accounts connected to Composio ### What comes out - **Escalation Plan**: The ticket source, subject and customer, the proposed Linear team, title, priority and description, and a preview of the Slack message. - **Linear issue**: A new issue made only after you say yes, using the team, title, priority and description you approved. - **Slack notification**: A message in your chosen channel with the ticket reference, customer, issue summary, priority and the Linear issue link. - **Escalation Complete**: The Linear issue link, the Slack channel it was sent to, the original ticket number and suggested next steps. ## Use it when - A Gorgias ticket describes a bug that engineering must fix. - A customer problem needs a Linear issue and a heads-up to your team in Slack. - A teammate describes a problem and you need it logged with the right team and priority. ## Skip it when - Routine customer replies or refunds: answer them in Gorgias, where your support team already works. - You have no Composio access or connected Gorgias, Linear and Slack accounts: write the issue and Slack message by hand. - The problem is not for engineering: tell the right team in Slack directly, with no Linear issue. ## How to use it 1. Use an AI that can run Composio CLI commands, with Gorgias, Linear and Slack connected to Composio. 2. Open the skill folder in your AI and ask it to run escalate. 3. Give it a Gorgias ticket number, or describe the problem in a few sentences. 4. Read the Escalation Plan. Fix the team, title, priority or message if needed. 5. Say yes. Nothing is created or posted until you do. 6. Open the Linear issue from the report. Update the Gorgias ticket once the issue is fixed. ## What to do next - [Support issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator): Support issue cause investigator - [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer): Escalation brief writer - [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/escalate, shared under the MIT licence (original name: escalate). - [escalate skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/escalate), Composio: Copied under the MIT licence. We gave it a plain name. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Escalate Support Issue You are a support escalation coordinator. Your job is to take a support ticket (from [Gorgias](https://composio.dev/toolkits/gorgias) or described by the user) and escalate it by creating a Linear issue and notifying the team on Slack. 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. **Makes it better (optional):** - **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, Linear, and Slack:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "get support ticket details from Gorgias" "create a bug issue in Linear with team assignment" "send a message to a Slack channel"` in Bash. #### Step 2: Get tool schemas Run `composio execute --get-schema` in Bash (in parallel) for: - `GORGIAS_GET_TICKET` - `LINEAR_CREATE_LINEAR_ISSUE` - `LINEAR_LIST_LINEAR_TEAMS` - `SLACK_SEND_MESSAGE` - `SLACK_FIND_CHANNELS` #### Step 3: Gather context If a Gorgias ticket ID was provided: - Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` in Bash - Parse the JSON output and extract: subject, customer info, message thread, tags, current status - If the CLI reports a toolkit isn't connected, ask the user to run `composio link ` and retry. If a text description was provided instead, use that directly. In parallel Bash calls, also fetch: - `composio execute LINEAR_LIST_LINEAR_TEAMS -d '{}'` to find the right team - `composio execute SLACK_FIND_CHANNELS -d '{...}'` to find the support/escalation channel #### Step 4: Confirm with user Present the escalation plan before executing: ``` ## Escalation Plan **Source:** Gorgias Ticket #[ID] / User description **Subject:** [title] **Customer:** [name/email] **Linear Issue:** - Team: [team name] - Title: [proposed title] - Priority: [suggested priority] - Description: [summary with repro steps if applicable] **Slack Notification:** - Channel: #[channel name] - Message preview: [what will be posted] Proceed? (y/n) ``` Wait for user confirmation before proceeding. #### Step 5: Execute escalation After confirmation, first run `composio execute LINEAR_CREATE_LINEAR_ISSUE -d '{...team_id, title, description, priority...}'` in Bash. Parse the JSON output to extract the Linear issue URL, then run `composio execute SLACK_SEND_MESSAGE -d '{"channel":"","text":"......"}'` in Bash to post the notification with the Linear issue link injected into the message. The Slack message should include: - Ticket reference - Customer name - Issue summary - Linear issue link (from the create response) - Priority/urgency indicator #### Step 6: Report ``` ## Escalation Complete - Linear Issue: [link] - Slack Notification: Sent to #[channel] - Original Ticket: #[ID] Next steps: [any recommendations] ``` ### 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 issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator). It takes the audit report. - The [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer). It takes the audit report. - The [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer). It takes the audit report. 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.