StyloDocs
Recipes

Customer 360 Enrichment

When a new ticket arrives, pull the customer's full context from Zendesk and HubSpot, then use AI to generate a comprehensive summary posted as an internal note.

View as Markdown

When a new ticket arrives, pull the customer's full context from Zendesk and HubSpot, then use AI to generate a comprehensive summary posted as an internal note.

Prerequisites: Connect Zendesk, Hubspot before adding this recipe. See Integrations.

How it works

Each box is a block; arrows show the order Stylo runs them, and branch labels show the path taken on each outcome.

Parameters

This recipe has no configurable parameters — connect the required integrations and it runs as shipped.

Blocks used

Every block in this recipe, linked to its reference page where one exists:

BlockTypeWhat it does
Webhooktrigger/webhookTrigger workflow via HTTP webhook
Get Ticket Contextzendesk/get-ticket-contextGet complete ticket context (ticket, conversation, customer, assignee, organization) optimized for AI
Get Userzendesk/get-userFetch a Zendesk user by ID
Get User Ticketszendesk/get-user-ticketsGet ticket history for a customer
Get Organizationzendesk/get-organizationGet organization details for B2B context
Search Contactshubspot/search-contactsSearch HubSpot contacts
Generate Textai/generate-textGenerate text using AI models
Add Comment / Replyzendesk/add-commentAdd a public reply or internal note to a ticket
Add Tagszendesk/add-tagsAdd tags to a ticket for classification and tracking

When to use it

Use this to give agents full context the moment a ticket arrives. It pulls the customer's history from Zendesk and HubSpot, then posts an AI-written summary as an internal note so the agent starts informed.

Adapt it

This recipe is a starting point. To fit it to your workspace:

  • Edit the summary generation prompt to highlight the facts your agents care about most.
  • Swap the HubSpot lookup for a different CRM block if you don't use HubSpot.
  • Change the Add Comment block to post the summary publicly instead of as an internal note, if that fits your workflow.

On this page