Add Zendesk support moments to a Scribeless campaign with Zapier
This guide uses Zapier as the connector, but the same workflow can be built in Make, Pipedream, n8n, or similar automation tools. The core pattern is: trigger from a Zendesk ticket or customer milestone, then add the customer as a recipient in Scribeless.
Before you build the Zap, create the campaign in Scribeless. Choose the note design, handwriting style, message, QR code, and merge variables first. Zapier's Scribeless action adds recipients to an existing campaign; it does not create the campaign content for you.
What this automation does
When a ticket is solved or a CSAT response arrives in Zendesk, Zapier sends the customer's name, company, postal address, and support context to Scribeless and adds the person to your chosen campaign.
Use this for B2B support and customer success workflows such as:
Sending an apology or thank-you note after a high-touch ticket is resolved.
Sending a welcome letter after an onboarding milestone.
Sending a customer success note after an expansion opportunity.
Sending a save-the-account postcard when a renewal or escalation needs a human touch.
If your Scribeless note includes a QR code, you can send scan engagement back into Zendesk in a separate workflow. A scan can create a follow-up task, update a customer record, log intent on the timeline, or route outreach to the owner.
What you need
A Zendesk account connected to Zapier.
A Scribeless campaign that is ready to receive recipients.
Zendesk user, organization, or ticket data with usable postal address fields.
A Zapier account connected to Zendesk and Scribeless.
A paid Zapier plan if you want filters, delays, Paths, or multi-step lookups.
Zendesk is usually strongest as the source of service timing, support context, owner, and customer health. Postal address data may live on the user, organization, CRM, or an enrichment source rather than the ticket itself.
Recommended Zap structure
For a post-resolution thank-you flow:
Trigger:
Zendesk- a solved ticket, new ticket view, CSAT response, or Zapier-supported Zendesk event.Filter: continue only when the support moment qualifies for handwritten follow-up.
Optional lookup: find the related user, organization, CRM account, or address record if the trigger payload does not include mailing fields.
Optional delay: wait until after the resolution or customer-success timing window.
Action:
Scribeless-Add Recipients.
Build the Zendesk trigger
In Zapier, create a new Zap.
Set the trigger app to
Zendesk.Choose the event that matches your send rule, such as a solved ticket, ticket update, or CSAT-related event.
Connect your Zendesk account.
Choose any trigger settings Zapier asks for.
Test the trigger so Zapier can load a recent ticket or customer record.
Use a test record that includes the requester, organization, ticket status, tags, satisfaction rating, owner, postal address, and any merge variables you expect to print.
Add optional filters and delays
Add a filter if only some Zendesk events should trigger handwritten mail. Common filters include:
Ticket status is solved or closed.
Ticket tag, priority, CSAT rating, customer segment, plan, owner team, or account tier matches the campaign.
The ticket belongs to an onboarding, escalation, success, renewal, or executive-support workflow.
Postal address fields are complete, or a lookup step returned a valid address.
Add Delay by Zapier when the note should arrive after the support moment rather than immediately after the ticket update. Useful patterns include waiting one business day after resolution, a few days after onboarding completion, or the right window before a renewal.
Add the Scribeless action
Add the final action step.
Choose
Scribeless.Set the action event to
Add Recipients.Connect your Scribeless account.
If you are in more than one Scribeless organization, choose the organization that contains the campaign you want to use.
The Scribeless action should come after filters, delays, routing, lookup, or enrichment steps that decide whether the Zendesk requester should receive mail.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map Zendesk's requester first name and last name to
First NameandLast Name.Map postal fields into
Address line 1,Address line 2, city, state or region, postal code, and country code.Map organization, ticket ID, ticket reason, support owner, CSAT rating, account tier, renewal date, or health score if your campaign uses those merge variables.
Optionally map email or phone for reconciliation, tracking, or reporting.
If the Zendesk trigger does not include address fields, add a lookup step for the user, organization, CRM account, or enrichment source before Scribeless. Retest with a complete record before mapping final fields.
Send QR scan activity back to Zendesk
Keep QR response handling separate from recipient creation. The first Zap adds recipients to Scribeless; the second records offline engagement back in Zendesk.
Common Zendesk follow-up actions include:
Create a customer success task.
Update a customer health, intent, or direct-mail engagement field.
Add an internal note to the user, organization, or ticket.
Route outreach to the account owner.
Trigger a follow-up workflow for renewal risk, advocacy, or onboarding.
Use a stable matching key such as email, Zendesk user ID, organization domain, CRM account ID, or ticket ID.
Test and turn on
Test the Zap with a safe internal Zendesk ticket or customer record.
Confirm the recipient appears in the correct Scribeless campaign.
Check that the name, address, organization, and merge variables are complete.
Review filter and delay logic if only specific support or success moments should receive mail.
Turn on the Zap once the test recipient looks correct.