Add BigCommerce customers 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 BigCommerce order event, optionally filter for the right order status or customer 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, discount 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 an order is completed in BigCommerce, Zapier sends the customer's name and address to Scribeless and adds them to your chosen campaign. For example, you can send a handwritten thank-you note with a discount code after a first purchase, surprise VIP customers after a high-value order, or trigger a win-back note when a lapsed buyer returns.
You can also use Scribeless QR scan engagement as a follow-up signal. When a recipient scans the QR code, send that engagement back into your ecommerce stack with BigCommerce or a webhook step so retention, loyalty, and win-back flows can react to real-world response.
What you need
A BigCommerce store connected to Zapier.
Orders that include usable billing or shipping address data.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to BigCommerce and Scribeless.
A paid Zapier plan if you want to add
Filter by Zapier,Delay by Zapier, or a webhook step in the same Zap.
Recommended Zap structure
For a post-purchase flow:
Trigger:
BigCommerce-Order Status Updated.Filter: continue only when the new order status is completed.
Delay: wait three to seven days, depending on fulfilment timing.
Action:
Scribeless-Add Recipients.
If you only need a simpler first version:
Trigger:
BigCommerce-Order Created.Action:
Scribeless-Add Recipients.
Then add status filtering, delays, or segmentation once the basic recipient handoff is working. Zapier's BigCommerce integration page lists triggers such as Order Created, Order Updated, and Order Status Updated, and BigCommerce's webhook event reference includes order-created and order-updated events that can support similar flows through webhook-based tools.
Build the BigCommerce trigger
In Zapier, create a new Zap.
Set the trigger app to
BigCommerce.Choose
Order Status Updatedif you want the Zap to react when an order reaches a completed state.Connect your BigCommerce store.
Test the trigger so Zapier can load a recent order status update.
If you use Order Created, add a filter after the trigger so incomplete or unpaid orders do not create handwritten mail too early. Zapier's BigCommerce troubleshooting notes recommend filtering when you only want completed orders to continue.
Add timing and eligibility rules
For post-purchase thank-you notes, add Delay by Zapier after the filter. A three-to-seven-day delay usually works better than immediate mail because the note can arrive after the customer receives the product.
For VIP or repeat-purchase programs, add a filter for the customer segment, order total, product category, or purchase count before the Scribeless action. For win-back mail, trigger from your ecommerce or retention system when a lapsed buyer returns, then route the recipient into a campaign with a relevant offer.
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 order fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map the customer's first name and last name from the BigCommerce billing or shipping fields.
Map address line 1, city, postal code, and country code from the address that should receive the note.
Map company name if you collect it at checkout.
Map order number, order value, product name, discount code, customer segment, or loyalty tier into custom fields if your Scribeless message uses merge variables.
Use shipping address fields when the handwritten note should go to the delivery address. Use billing address fields when the note should go to the purchaser or account holder.
Test and turn on
Test with an internal order or a safe test order.
Confirm the recipient appears in the correct Scribeless campaign.
Check the address source, especially if billing and shipping addresses differ.
Confirm any discount code or QR merge variable appears correctly in the Scribeless preview.
Turn on the Zap once the test recipient looks correct.
Optional: send QR engagement back to BigCommerce
If your Scribeless campaign uses a QR code, use the scan event as a follow-up signal. Depending on your stack, that follow-up can update a customer segment, add a loyalty marker, create a customer note, or fire a webhook that another tool uses to continue the journey.
For example:
QR scanned after thank-you note -> move customer into a repeat-purchase audience.
QR scanned by a VIP buyer -> trigger a loyalty follow-up webhook.
No scan after a win-back note -> route the customer to a different retention campaign.
Keep the first Zap focused on reliable recipient creation. Add the QR engagement loop after the post-purchase mail flow is tested end to end.