Add Reply.io prospects 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 another automation platform that can read Reply.io events and call the Scribeless recipient action. The core pattern is: trigger from a Reply.io sales moment, then add the prospect 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 any 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 Reply.io prospect reaches the right sales engagement moment, Zapier sends the prospect, company, postal address, and sales context to Scribeless and adds the person to your selected campaign.
Use this for B2B workflows such as:
Sending a handwritten follow-up after a meeting is booked.
Sending an executive note when a prospect moves to a key opportunity stage.
Sending a card after a positive reply creates sales intent.
Sending a nudge when a sequence completes without a reply.
If your Scribeless campaign uses a QR code, send scan activity back into Reply.io in a separate workflow. A QR scan can pause a sequence, create a rep task, alert the owner, or update an engagement field so reps focus on leads showing offline intent.
What you need
You need Reply.io and Scribeless connected to Zapier, a Scribeless campaign that is ready to receive recipients, and Reply.io prospect records with the postal fields Scribeless needs: first name, last name, address line 1, city, postal code, and country. Reply.io is strong for owner, sequence, stage, meeting, and reply context, but postal address data may live in custom fields or another CRM.
Recommended Zap structure
For a simple sales follow-up send:
Trigger:
Reply- a prospect, meeting, sequence, or stage event.Optional filter: continue only when the event matches the direct mail moment.
Optional lookup or enrichment: find postal address fields if they are not on the Reply.io trigger.
Action:
Scribeless-Add Recipients.
For higher-control workflows, add filters before Scribeless for account tier, territory, owner, sequence, stage, meeting type, country, or address completeness. Add a delay when the note should send the next business day or after a follow-up window.
Build the Reply.io trigger
In Zapier, create a new Zap.
Set the trigger app to
Reply.Choose the Reply.io event that matches your send rule, such as a meeting, stage change, or sequence completion.
Connect your Reply.io account.
Test the trigger so Zapier can load a recent prospect.
Use a test prospect that includes the person, company, owner, sequence or stage, and address fields you expect to map into Scribeless.
Add optional filters and delays
Add a filter if only some Reply.io events should trigger mail. Common B2B filters include:
Prospect stage changed to
Meeting booked,Opportunity,Positive reply, or another qualified status.Sequence equals your outbound, ABM, expansion, partner, or reactivation campaign.
Meeting type, account tier, owner team, territory, or company size matches the campaign rule.
The prospect has not already received the same direct mail campaign.
Place the filter after the Reply.io trigger and before Scribeless. Add a delay when mail should send the day after a booked meeting or two business days after a positive reply.
Add the Scribeless action
Add the final action step.
Choose
Scribeless.Set the action event to
Add Recipients.Connect your Scribeless account.
Choose the organization that has the campaign you want to use.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map Reply.io's first and last name fields.
Map postal fields into address line, city, state or region, postal code, and country code.
Map company, title, sequence, stage, owner, meeting date, reply status, account tier, or territory if your campaign uses those merge variables.
Optionally map email or phone for reconciliation.
If a field does not appear in the picker, retest the trigger with a prospect that includes data in that field. If Reply.io does not store postal address data, add a CRM lookup or enrichment step.
Send QR scan activity back to Reply.io
If your Scribeless note includes a QR code, create a separate automation for offline response signals. The Reply.io destination action is usually one of:
Pause the prospect in the active sequence.
Create a task for the assigned rep.
Alert the owner for fast follow-up.
Update a custom engagement field such as
Last direct mail QR scan date.
Keep this separate from the send workflow. The first Zap adds recipients to Scribeless; the second records the response signal back in Reply.io or the connected CRM. Learn more in QR codes: tracking engagement.
Test and turn on
Test the Zap with a safe internal Reply.io prospect.
Confirm the recipient appears in the correct Scribeless campaign.
Check that name, address, company, sales context, and merge variables are complete.
Review filter and delay logic.
Turn on the Zap once the test recipient looks correct.
For live workflows, monitor the first few Zap runs and Scribeless recipients, especially when address data comes from custom fields or CRM lookups.
Troubleshooting
The prospect appears in Zapier but not in Scribeless
Check the Zap run history. Confirm the filter passed, the delay completed, and the Scribeless action ran successfully. Then confirm the action points at the right organization and campaign.
Address fields are missing
Sync postal fields into Reply.io, add a CRM lookup, or enrich the record before Scribeless.
Every Reply.io event is triggering mail
Use a filter based on event type, sequence, stage, meeting status, owner team, account tier, country, or direct mail eligibility.
QR scan activity is not updating Reply.io
Keep the QR response workflow separate from the send workflow. Confirm the QR scan trigger is receiving events, then confirm the Reply.io action updates the intended prospect by a stable ID or email address.