Personalized recall brief for every new Zendesk ticket

Build me an agent workflow that gives my Zendesk support reps a personalized recall brief for every new ticket so they never start a conversation cold.

Trigger: an outgoing webhook from Zendesk. I will configure a Zendesk trigger or automation that fires on ticket creation and POSTs the ticket payload to the workflow's webhook URL. Expect the payload to contain at minimum the ticket id, requester id, subject, the first comment body, the assignee id (or group), and the ticket URL.

Steps for the agent:

1. Parse the incoming Zendesk webhook payload and pull out ticket id, requester id, subject, first comment body, assignee, and ticket URL.

2. Call Zendesk Show User on the requester id to get the requester's email address. If the user has no email, stop and add a private internal note on the ticket explaining why no brief was generated.

3. Call Mem0 Search Memories with user_id set to that email address and a semantic query built from the ticket subject plus the first ~500 characters of the first comment. Ask for the top ~10 results.

4. From the returned memories, synthesize a short recall brief (aim for 6-10 bullets total) organized into these sections, only including sections that have content: Prior unresolved issues, Stated preferences (channel, tone, technical depth), Commitments we've made, Recurring pain pattern. Cite which memory each bullet came from where useful. Keep it tight, this is for a rep about to reply.

5. Call Zendesk Update Ticket on the original ticket id to add the brief as a comment with public: false (a private internal note). The brief must never appear in the public-facing conversation. Prefix it with a clear header like "Customer recall brief (auto-generated from Mem0)".

6. Call Slack Send a Message to post the same brief into the team's support channel (channel name should be a configurable input, default #support-triage). Tag the assignee by Slack handle if available, and include a clickable link back to the Zendesk ticket. Use Slack mrkdwn formatting.

7. If Mem0 Search Memories returns zero results or nothing semantically relevant, do NOT generate a brief. Instead, add a single private internal note on the ticket that says "No prior context found in Mem0 for this customer" and skip the Slack message entirely. The support channel should stay quiet for first-time customers.

Safety constraints: every Zendesk comment this workflow writes MUST have public: false. Past memories may contain sensitive context (account details, prior complaints, internal notes about the relationship) and must never leak to the customer. Do not edit existing public comments or change ticket status, priority, or assignee.

Inputs I want to be able to configure without editing the workflow: the Slack channel to post into, and an optional list of Zendesk tags or brand ids that scope which tickets get a brief (so we can pilot on paid accounts first).