Add Omnisend contacts 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 a direct API workflow. The core pattern is: trigger from an Omnisend contact or lifecycle update, optionally filter for the right ecommerce segment, 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, offer, 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 contact is created or updated in Omnisend, Zapier can send that person's name, company, and postal address to Scribeless and add them to your chosen campaign. For ecommerce retention teams, this is most useful when Omnisend already identifies the customer moment and Scribeless handles the handwritten mail send.
Common examples include:
VIP segment entry -> handwritten offer or loyalty thank-you.
Birthday, renewal, or customer anniversary -> celebratory card.
Email engagement threshold -> premium offline follow-up.
Lapsed customer segment -> win-back note with a QR-linked offer.
If your Scribeless note includes a QR code, you can also send scan engagement back into Omnisend later. That lets an offline response start an automation, update a contact, change a segment, or trigger a follow-up message.
What you need
An Omnisend account connected to Zapier.
Contacts with usable first name, last name, and postal address fields.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to Omnisend and Scribeless.
A paid Zapier plan if you want filters, delays, Paths, or webhook steps in the same Zap.
Recommended Zap structure
For a campaign-first retention workflow:
Trigger:
Omnisend-Updated Contacts.Filter: continue only when the customer matches the segment or event that should receive mail.
Delay: wait until the send moment is appropriate for the customer experience.
Action:
Scribeless-Add Recipients.
You can also use New Contact for a simpler first version. For most retention and lifecycle programs, Updated Contacts is more flexible because segment, profile, and engagement changes often happen after the original subscription or purchase.
Build the Omnisend trigger
In Zapier, create a new Zap.
Set the trigger app to
Omnisend.Choose
Updated Contactswhen the Zap should react to profile, segment, or lifecycle changes.Connect your Omnisend account.
Test the trigger so Zapier can load a recent contact record.
Use a test contact that includes the fields you expect to print: first name, last name, email, postal address, country code, customer status, loyalty tier, birthday, renewal date, discount code, or segment marker.
Add timing and eligibility rules
Add Filter by Zapier before Scribeless so only eligible contacts receive handwritten mail. Good filters include:
Segment, tag, or custom property equals the campaign audience.
Customer lifetime value, order count, or loyalty tier meets the threshold.
Email engagement, product interest, or win-back status matches the playbook.
Address line 1, city, postal code, and country code are present.
Add Delay by Zapier when the note should land after a customer action. For example, wait a few days after a VIP purchase so the card arrives after fulfilment, or wait until a renewal date is close enough for the message to feel timely. For win-back campaigns, match the delay to the lifecycle rule you already use in Omnisend.
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 the Omnisend trigger and after any filter, delay, routing, lookup, or enrichment steps that decide whether the contact should receive mail.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map the Omnisend contact's first name and last name.
Map address line 1, address line 2, city, state or region, postal code, and country code.
Map company name if your store collects it or if the flow supports B2B buyers.
Map customer segment, loyalty tier, discount code, birthday, renewal date, product interest, or last order details if your Scribeless campaign uses merge variables.
Optionally map email or phone for reconciliation, tracking, or reporting.
Use the postal address source that matches the campaign. For ecommerce retention, shipping address is usually the right destination. For B2B ecommerce or account-based gifting, confirm whether the note should go to the buyer, recipient, office, or account owner.
Test and turn on
Test the Zap with an internal or safe customer record.
Confirm the recipient appears in the correct Scribeless campaign.
Check the address fields, especially country code and postal code formatting.
Confirm any discount code, QR link, loyalty tier, or segment merge variable appears correctly.
Turn on the Zap once the test recipient looks correct.
Optional: send QR engagement back to Omnisend
Keep QR response handling separate from recipient creation. The first Zap adds recipients to Scribeless; a second automation can record offline engagement back into Omnisend.
For example:
QR scanned after a VIP note -> update the contact profile and start a loyalty automation.
QR scanned after a win-back note -> move the customer into a reactivated segment.
No scan after a retention note -> continue the existing Omnisend nurture path.
Use a stable matching key such as email, customer ID, or order ID. Start with the recipient handoff first, then add the QR feedback loop after the handwritten mail flow is tested end to end.