CUSTOMER SUPPORT
Route new macro suggestions to Slack for one-click approval
When a draft macro lands in Supabase, posts it to a Slack review channel with Approve/Reject actions, and on approval creates the macro live in Zendesk.
How it runs
The automated pipeline, trigger to output.
- TriggerNew draft row in SupabaseSupabase
- ActionPost draft with action buttons to SlackSlack
- LogicBranch on Approve vs Reject
- ActionCreate macro in Zendesk on approvalZendesk
- OutputMark row published and confirm in threadSupabase
What it does
Closes the loop between an AI-drafted macro and a published one. Every new suggestion is surfaced to a human reviewer in Slack, and an approval pushes it straight into Zendesk as a usable macro—no copy-paste, no portal hunting.
When to use it
Pair this with any pipeline that generates macro drafts. Use it when you want a lightweight human gate before macros go live, so quality stays high without a heavy review meeting.
How it works
- 1A new row in the Supabase `macro_suggestions` table triggers the run.
- 2Format the draft title and body into a readable Slack message with Approve and Reject buttons.
- 3Post it to your support review channel and wait for a reviewer's click.
- 4Branch on the response: Reject marks the row `dismissed` and stops.
- 5On Approve, create the macro in Zendesk via the API.
- 6Update the Supabase row to `published` with the new Zendesk macro ID, and confirm in the Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect SupabaseTables, auth, storage, edge functions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.