Add Help Scout conversations 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 Help Scout conversation 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 Help Scout conversation is closed, tagged, or moved by a workflow, 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 meaningful support conversation.
Sending a welcome letter after an onboarding milestone.
Sending a customer success note after expansion or implementation help.
Sending a save-the-account postcard when a renewal or escalation needs a human touch.
Sending a handwritten follow-up after a customer success team resolves an executive request.
If your Scribeless note includes a QR code, you can send scan engagement back into Help Scout or your CRM in a separate workflow. For example, a QR scan could add a follow-up task, update a customer record, or notify the account owner.
What you need
A Help Scout account connected to Zapier.
A Scribeless campaign that is ready to receive recipients.
Help Scout customer, conversation, tag, or workflow data that identifies the send moment.
Postal address data in Help Scout, your CRM, a customer database, or a lookup step.
A paid Zapier plan if you want filters, delays, Paths, or multi-step enrichment.
Help Scout is usually strongest as the source of support timing, tags, mailbox, owner, and conversation context. Postal address fields may need to come from your CRM or customer database, especially if Help Scout is used mainly for support messaging.
Recommended Zap structure
For a post-support handwritten note:
Trigger:
Help Scout-Tags Updated.Filter: continue only when the tag or workflow represents a send moment.
Optional lookup: find the related customer, company, CRM account, or address record.
Optional delay: wait until after the support moment.
Action:
Scribeless-Add Recipients.
This structure keeps Help Scout responsible for the support signal, while Scribeless handles the handwritten mail send.
Build the Help Scout trigger
In Zapier, create a new Zap.
Set the trigger app to
Help Scout.Choose
Tags Updated.Connect your Help Scout account.
Choose any mailbox or tag settings Zapier asks for.
Test the trigger so Zapier can load a representative conversation.
Use a test conversation that includes the customer, company, tag, mailbox, owner, conversation reason, postal address source, and any merge variables you expect to print.
Add optional filters and delays
Add a filter if only some Help Scout tags should trigger handwritten mail. Common filters include:
Tag equals
resolved-escalation,thank-you-note,onboarding-complete,renewal-risk, or another campaign-specific tag.Mailbox, owner team, priority, customer segment, plan, or account tier matches the campaign.
Postal address fields are complete, or a lookup step returned a valid address.
The conversation is customer-facing, not an internal note or routine admin update.
Add Delay by Zapier if the note should arrive after the support experience rather than immediately after the tag changes. For example, you might wait one or two business days after an escalation is resolved before sending a personal follow-up.
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.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map the customer's first name and last name.
Map postal fields into
Address line 1,Address line 2, city, state or region, postal code, and country code.Map company, tag, mailbox, owner, customer segment, or support reason if your campaign uses merge variables.
Optionally map email or phone for reconciliation, tracking, or reporting.
If Help Scout does not include address fields in the trigger sample, add a CRM or data lookup step before Scribeless. Retest with a complete record before mapping final fields.
Test and turn on
Test with a safe internal Help Scout conversation.
Confirm the recipient appears in the correct Scribeless campaign.
Check the name, address, company, and merge variables.
Confirm filters prevent routine support updates from triggering mail.
Turn on the Zap once the test recipient looks correct.
Troubleshooting
If the Zap test does not create the right recipient, check these points first:
The selected Scribeless organization contains the campaign you chose.
The Help Scout trigger sample includes the fields you mapped.
The lookup step returns one customer or account record, not multiple matches.
Address fields are split into the format Scribeless expects.
Filters exclude routine support updates, internal notes, and conversations without a postal address.
For higher-volume support workflows, start with a narrow tag or mailbox first. Once the test records look correct in Scribeless, you can broaden the automation to more segments or workflows.