CUSTOMER SUPPORT
Pre-translate inbound webhook tickets before creating them in Zendesk
Accepts raw ticket payloads on a webhook, detects and translates the message to English with Hugging Face.
How it runs
The automated pipeline, trigger to output.
- TriggerInbound ticket payload via HTTP webhookHTTP webhook
- ActionDetect language via Hugging FaceHugging Face
- ActionTranslate subject and body to English via Hugging FaceHugging Face
- LogicMap language to Zendesk group with fallback
- OutputCreate Zendesk ticket with translation and groupZendesk
What it does
This workflow sits in front of Zendesk for tickets arriving from a custom channel (a contact form, chat widget, or partner integration). It receives the raw message over a webhook, identifies the language, generates an English translation, and creates the Zendesk ticket already enriched with the original-language note and a group assignment so triage is instant.
When to use it
You ingest support requests from a non-Zendesk front door and want them to land in Zendesk fully classified by language rather than dumped into a default queue for manual sorting. Ideal for forms or apps serving a global audience.
How it works
- 1An inbound HTTP webhook delivers the ticket payload (sender, subject, body).
- 2A Hugging Face model detects the body's language code.
- 3A Hugging Face translation model produces an English version of subject and body.
- 4A branch maps the detected language to a Zendesk group; unmapped languages fall back to a general multilingual group.
- 5A Zendesk ticket is created with the English translation in the description, the original text preserved, a language tag, and the resolved group assignment.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect ZendeskTickets, queues, knowledge base.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.