--- title: "Gorgias and HubSpot customer briefing writer" type: "skill" url: "https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief" 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/customer-360" instructions: "https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief/SKILL.md" --- # Gorgias and HubSpot customer briefing writer > Share a customer name or email. Get CRM details, recent support tickets, contact activity and gaps in one brief. Use a Composio setup linked to Gorgias and HubSpot, then share the customer’s name or email. It finds matching records, reads up to five recent tickets and gathers CRM activity. Get a brief with open issues, recent contact and proposed next steps. Mark missing history and keep any sentiment or risk label as a rough judgement, not a validated score. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief.zip - JSON version: https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-and-hubspot-customer-brief" ## What you give it - A customer email or name. - Access to your Gorgias account, linked through Composio CLI. - Access to your HubSpot account, linked through Composio CLI. ## What you get - A profile with company, title, lifecycle stage and owner. - Ticket counts and a table of the five most recent tickets. - A dated timeline of notes, emails and calls. - A simple health score for sentiment, engagement and risk. - A short list of recommended actions. ## Example: what goes in and what comes out ### What goes in - A customer email or name - Your Gorgias account, connected through Composio CLI - Your HubSpot account, connected through Composio CLI ### Before you start - An AI that can run commands in a terminal - Composio CLI installed - Gorgias and HubSpot accounts linked to Composio ### What comes out - **Profile (HubSpot)**: Company, title, lifecycle stage, owner, created date, last activity and any useful custom fields. - **Support History (Gorgias)**: Total tickets, open tickets, average resolution time and the date of last contact. - **Recent Tickets**: A table of the latest tickets with subject, status, priority, created date and last update. - **Engagement Timeline (HubSpot)**: A dated table of notes, emails and calls with a short summary of each. - **Customer Health Score**: Sentiment, engagement and risk levels, based on recent tickets and how often they get in touch. This is the AI's estimate, so check it before you act on it. - **Recommended Actions**: Specific next steps based on the data found. ## Use it when - A customer writes in and you want their full history before you reply. - You are about to call a customer and need to know their open issues. - A teammate hands you an account and you need to catch up fast. - You want to check if a customer is at risk before a renewal. ## Skip it when - The customer has no Gorgias or HubSpot record. Use a plain ticket export from your help desk instead. - You cannot install Composio CLI or connect both accounts. Paste the ticket text and CRM notes into your AI and ask for a summary. - You want to reply to the customer. Use your help desk reply box, then check the brief first. ## How to use it 1. Use an AI that can run terminal commands, such as Claude Code. A plain chat window cannot run the live lookup. 2. Install Composio CLI and link both accounts with composio link gorgias and composio link hubspot. Gorgias is a paid help desk. HubSpot has a free CRM plan, with paid extras. Composio may charge for use, so check its pricing before the first run. 3. Add the skill folder and ask for the Customer 360 view. 4. Give it the customer email or name. 5. Check the brief. If one system has no match, it shows the other and says so. 6. Approve any reply or account change yourself before it happens. 7. Next, copy the brief into the HubSpot record, or use the Gorgias support reply writer to draft a reply you approve before sending. ## 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/customer-360, shared under the MIT licence (original name: customer-360). - [customer-360 skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/customer-360), Composio: Copied under the MIT licence. We gave it a plain name, replaced the HubSpot placeholder call with steps built from the fetched schema, labelled the health score as an estimate, and added a next step that never sends anything. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Customer 360 View You are a customer intelligence specialist. Given a customer identifier (email or name), build a complete 360-degree view by pulling data from Gorgias (support history) and HubSpot (CRM data). 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 and HubSpot:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "search for customer support tickets by customer email in Gorgias" "search for contact by email or name in HubSpot CRM and get contact history"` in Bash. #### Step 2: Get tool schemas Run `composio execute --get-schema` in Bash (in parallel) for each of these slugs: - `GORGIAS_LIST_TICKETS` - `GORGIAS_GET_TICKET` - `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` - `HUBSPOT_READ_CONTACT` - `HUBSPOT_SEARCH_CRM_OBJECTS_BY_CRITERIA` #### Step 3: Search in parallel Run these in parallel (either as parallel Bash calls, or via `composio execute --parallel GORGIAS_LIST_TICKETS -d '{...}' HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA -d '{...}'`): 1. `GORGIAS_LIST_TICKETS` — filter by customer email/name 2. `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` — search by the customer identifier If the CLI reports a toolkit isn't connected, ask the user to run `composio link gorgias` or `composio link hubspot` and retry. #### Step 4: Deep dive Parse the JSON output from Step 3 and based on results: - For Gorgias: Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` in parallel Bash calls for the most recent 5 tickets - For HubSpot: Use the contact_id to fetch engagement history with `composio execute HUBSPOT_SEARCH_CRM_OBJECTS_BY_CRITERIA -d ''`, once each for notes, emails and calls. Build the JSON from the schema you fetched in Step 2: set the object type (notes, emails or calls) and filter on records associated with that contact ID. If the schema has no way to filter by contact, say so and show only the profile from `HUBSPOT_READ_CONTACT`. #### Step 5: Present the 360 View ``` ## Customer 360: [Name] ([Email]) ### Profile (HubSpot) - **Company:** ... - **Title:** ... - **Lifecycle Stage:** ... - **Owner:** ... - **Created:** ... - **Last Activity:** ... - **Custom Properties:** [any relevant ones] ### Support History (Gorgias) - **Total Tickets:** X - **Open Tickets:** X - **Avg Resolution Time:** ... - **Last Contact:** ... #### Recent Tickets | # | ID | Subject | Status | Priority | Created | Last Update | |---|-----|---------|--------|----------|---------|-------------| ### Engagement Timeline (HubSpot) | Date | Type | Summary | |------|------|---------| ### Customer Health Score _Your estimate from the tickets and contacts listed above. Check it before acting on it._ - Sentiment: [Positive/Neutral/Negative based on recent tickets] - Engagement: [Active/Moderate/Low based on interaction frequency] - Risk: [Low/Medium/High based on open issues and sentiment] ### Recommended Actions - [Specific suggestions based on the data] ``` If the customer is not found in one system, note it and show data from whichever system has results. End with one next step: for example, copy the brief into the CRM record, or draft a reply for the user to approve before anything is sent. Never send a reply or change a record yourself. ### 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.