Add Mailchimp 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 when a Mailchimp contact reaches the right lifecycle moment, optionally filter or delay the workflow, then add the contact 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 Mailchimp subscriber is added to a segment or tag, Zapier sends the subscriber's contact details to Scribeless and adds the person as a recipient in your chosen campaign.
Use this for B2B workflows such as:
Sending a handwritten offer when a contact enters a VIP customer segment.
Sending a celebratory birthday, renewal, anniversary, or contract milestone card.
Sending a premium direct mail follow-up after a contact reaches an email engagement threshold.
Sending a win-back note when a customer enters a lapsed or at-risk segment.
You can also send offline response signals back into Mailchimp. For example, when a recipient scans a Scribeless QR code, use a second automation to add a Mailchimp tag, start a journey, or update the contact profile so future email journeys can react to the offline response.
What you need
A Mailchimp audience, tag, or segment that identifies the contacts who should receive handwritten mail.
Contact fields for recipient name and postal address. Mailchimp email fields alone are not enough for physical mail.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to Scribeless.
A Mailchimp account connected to Zapier, or access to the Mailchimp account owner who can approve the connection.
A paid Zapier plan if you want to use
Filter by Zapier,Delay by Zapier, or Paths.
If Mailchimp does not store postal addresses for the contacts you want to mail, add a lookup or enrichment step before Scribeless. Common sources include your CRM, customer data platform, order platform, or data warehouse.
Recommended Zap structure
For a simple lifecycle mail workflow, use Mailchimp - New Subscriber in Segment or Tag followed by Scribeless - Add Recipients.
For a more controlled B2B workflow, add a filter before Scribeless to check audience, tag, segment, region, lifecycle stage, account tier, or engagement threshold. Add a delay if the note should send after a renewal sequence, engagement milestone, or win-back window rather than immediately.
Build the Mailchimp trigger
In Zapier, create a new Zap.
Set the trigger app to
Mailchimp.Choose
New Subscriber in Segment or Tagas the trigger event. This starts the Zap when a subscriber is added to a selected segment or tag in an audience.Connect your Mailchimp account.
Choose the audience and the segment or tag that should trigger handwritten mail.
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 first name, last name, company if needed, and complete postal address fields.
Add optional filters and delays
Add a filter if only some Mailchimp contacts in the trigger group should receive handwritten mail. Common B2B filters include:
Audience is the business audience, not a newsletter-only audience.
Tag is
VIP,Target Account,Renewal,Customer Winback, or another campaign-specific label.Company type, region, or account tier meets your campaign criteria.
The contact has a complete postal address.
The contact has not already received the same Scribeless campaign.
Place the filter after the Mailchimp trigger and before the Scribeless action. If the filter does not pass, Zapier stops the run and no recipient is added to Scribeless.
Add a delay when the handwritten note should follow a specific lifecycle moment rather than send immediately. Useful delay patterns include:
Wait one day after a VIP tag is added before sending a premium offer.
Wait until after a renewal email sequence has started before sending a celebratory card.
Wait several days after a high engagement threshold before sending an account executive follow-up.
Wait until a customer has stayed in a lapsed segment for a set period before sending a win-back note.
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, routing, deduplication, or enrichment steps that decide whether the subscriber should receive mail.
Map the fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map first name and last name from Mailchimp merge fields.
Map address line 1, address line 2, city, state or region, postal code, and country code from Mailchimp address fields or an enrichment step.
Map company name if your Scribeless campaign uses it in the note or envelope.
Optionally map email, audience, tag, segment, lifecycle stage, renewal date, customer tier, or engagement fields if your campaign uses those values as merge variables.
If Mailchimp stores the address as a single address object, use the individual subfields Zapier exposes in the field picker. If address fields do not appear, retest the trigger with a subscriber that has those fields populated.
Test and turn on
Test the Zap with a safe internal Mailchimp contact.
Confirm the recipient appears in the correct Scribeless campaign.
Check that the name, address, company, and merge variables are complete.
Review filter and delay logic if the note should only send after a qualification, lifecycle, or timing step.
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 the Mailchimp tag or segment is applied 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 ran successfully. Then confirm the action is pointing at the right Scribeless organization and campaign.
Address fields are missing
Mailchimp may not have postal address fields for every contact. Add address collection to your forms, sync address data from your CRM or commerce platform, or add an enrichment step before Scribeless.
The wrong contacts are receiving mail
Check the Mailchimp audience, segment, and tag selected in the trigger. For stricter control, add a filter before Scribeless or use separate Zaps for VIP, renewal, win-back, and engagement-triggered campaigns.
A QR scan should update Mailchimp
Create a second automation from the QR scan event or tracking destination back to Mailchimp. Use Mailchimp actions such as adding a tag, starting a journey, or updating a contact field.