Add Drip subscribers 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 Drip lifecycle moment, optionally filter or delay the workflow, then add the subscriber 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 subscriber is added to a Drip tag, enters a workflow, or reaches another lifecycle trigger in Drip, Zapier sends that subscriber's details to Scribeless and adds the person as a recipient in your chosen campaign.
Use this for B2B and ecommerce retention workflows such as:
Sending a handwritten offer when a subscriber enters a VIP customer or target-account segment.
Sending a birthday, renewal, anniversary, or customer milestone card.
Sending a premium direct mail follow-up after a subscriber reaches an email engagement threshold.
Sending a win-back note when a customer enters a lapsed, churn-risk, or reactivation segment.
If your Scribeless campaign includes a QR code, a scan can trigger an email or SMS journey, update a profile, suppress duplicate reminders, or add the subscriber to an engaged segment.
What you need
A Drip account connected to Zapier.
A Drip tag, workflow trigger, or segment that represents the moment you want to mail from.
Subscriber fields for recipient name and postal address. Email-only subscriber records are not enough for physical mail.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to Scribeless.
A paid Zapier plan if you want to use
Filter by Zapier,Delay by Zapier, or Paths.
Drip is often the best system for deciding when a lifecycle touch should happen, but it may not be the source of postal address data. If address fields are stored elsewhere, add a lookup step before Scribeless.
Recommended Zap structure
For a simple tag-triggered workflow, use Drip - New Subscriber Tag followed by Scribeless - Add Recipients. For a more controlled campaign, add a filter, delay, or lookup step before Scribeless so the note only sends when the subscriber is eligible and address data is complete.
Build the Drip trigger
In Zapier, create a new Zap.
Set the trigger app to
Drip.Choose a trigger event that matches your campaign entry point.
New Subscriber Tagis a practical option when Drip applies a tag for VIP entry, birthday, renewal, high engagement, or win-back eligibility.Connect your Drip account.
Choose the account, tag, workflow, or trigger-specific option Zapier asks for.
Test the trigger so Zapier can load a recent subscriber sample.
Use a test subscriber that looks like a real recipient. The sample should include name, company if needed, postal address fields, or a stable key for a lookup step.
Add optional filters and delays
Add a filter if only some Drip subscribers should receive handwritten mail. Common filters include:
Tag is
VIP,Renewal due,High intent,Lapsed customer, orTarget account.Customer tier, lifetime value, account status, or engagement score meets your threshold.
Country or region is supported by the Scribeless campaign.
The subscriber has a complete postal address or passed an address lookup step.
Place the filter after the Drip trigger and before Scribeless. If the filter does not pass, no recipient is added.
Add Delay by Zapier when the handwritten note should follow the lifecycle moment rather than fire immediately, such as after a high-intent email click, delivery window, renewal sequence, or win-back email/SMS attempt.
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 has the campaign you want to use.
The Scribeless action should come after any filters, delays, consent checks, deduplication, or enrichment steps that decide whether the subscriber should receive mail.
Map the subscriber fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map first name, last name, and postal address fields from Drip or a previous lookup step.
Map company name if your Scribeless campaign uses it in the note or envelope.
Optionally map email, tag, workflow name, lifecycle stage, renewal date, VIP status, engagement score, or customer tier as merge variables.
If Drip stores full name in one field, use Zapier Formatter or a CRM lookup to split it before the Scribeless action. If address fields do not appear, retest the trigger with a subscriber that has those fields populated.
Send QR scan activity back to Drip
If your Scribeless campaign uses a QR code, decide what should happen when someone scans it. Capture the scan or form submission with the recipient's email, subscriber ID, or another matching key, then send that event into Drip as a tag, workflow trigger, or profile update. Drip can then start the next journey, update intent, suppress duplicate reminders, or move the subscriber into an engaged segment.
Test and turn on
Test the Zap with a safe internal Drip subscriber.
Confirm the recipient appears in the correct Scribeless campaign.
Check that name, address, company, and merge variables are complete.
Turn on the Zap once the test recipient looks correct.
For live workflows, monitor the first few Zap runs and Scribeless recipients. Pay close attention to address formatting, country codes, duplicates, and whether Drip applies the trigger tag at the right lifecycle moment.
Troubleshooting
The subscriber appears in Zapier but not in Scribeless
Check the Zap run history. Confirm the filter passed, the delay completed, and the Scribeless action points at the right organization and campaign.
Address fields are missing
Drip records may not include postal address fields by default. Add address fields, sync them from your commerce platform or CRM, or add a lookup step before Scribeless.
The wrong subscribers are receiving mail
Check the Drip tag, workflow, or segment selected in the trigger. For stricter control, add a filter before Scribeless or use separate Zaps for each campaign type.