CUSTOMER SUPPORT
Sync Approved Macro Drafts from Notion Live into Zendesk
When a reviewer marks a proposed macro as Approved in Notion, validates the final wording, creates the macro in Zendesk.
How it runs
The automated pipeline, trigger to output.
- TriggerNotion card marked ApprovedNotion
- ActionRead final macro title, body, and categoryNotion
- LogicValidate fields and title uniqueness
- ActionCreate macro in ZendeskZendesk
- ActionWrite live macro ID back to Notion cardNotion
- OutputConfirm publish to reviewer in SlackSlack
What it does
Closes the last mile of the macro pipeline. The moment a lead flips a draft card to Approved in your Notion review board, this publishes it as a real Zendesk macro, then stamps the card with the live macro ID and timestamp so the board always reflects what actually shipped.
When to use it
When humans review macro drafts in Notion and you want approvals to take effect immediately and traceably, without anyone copy-pasting wording into Zendesk by hand or losing track of which drafts went live.
How it works
- 1A Notion status change to Approved triggers the run.
- 2Read the card's final macro title, body, and target category.
- 3Validate that required fields are present and the title is unique — branch to a fix-needed state if not.
- 4Create the macro in Zendesk with the approved wording and assign it to the right group.
- 5Write the new Zendesk macro ID, live URL, and publish timestamp back onto the Notion card.
- 6Output a confirmation to the reviewer in Slack that the macro is live.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.