Skip to main content

Add WooCommerce customers to a Scribeless campaign with Zapier

Learn how to add WooCommerce customers to an existing Scribeless campaign with Zapier.

Add WooCommerce 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 WooCommerce order, optionally filter and wait, 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, 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 WooCommerce order is created or completed, Zapier sends the customer's billing or shipping address to Scribeless and adds them as a recipient in your chosen campaign.

For post-purchase campaigns, we recommend sending after fulfilment or after a short delay, such as five days after the order is completed. This gives the customer time to receive the product before the handwritten note arrives.

What you need

  • A WooCommerce 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 WooCommerce and Scribeless.

  • A paid Zapier plan if you want to add Delay by Zapier and Filter by Zapier steps in the same Zap.

Recommended Zap structure

For a complete post-purchase flow:

  1. Trigger: WooCommerce - new order or updated order.

  2. Filter: continue only when the order status is completed or fulfilled.

  3. Delay: wait five days.

  4. Action: Scribeless - add recipient to campaign.

If your Zapier plan only supports a two-step Zap, start with the simpler version:

  1. Trigger: WooCommerce - new order.

  2. Action: Scribeless - add recipient to campaign.

Then add filtering and delay later, or handle timing in Scribeless if your account has an appropriate flow setup.

Build the WooCommerce trigger

  1. In Zapier, create a new Zap.

  2. Set the trigger app to WooCommerce.

  3. Choose an order trigger, such as New Order.

  4. Connect your WooCommerce store.

  5. Test the trigger so Zapier can load a recent order.

WooCommerce trigger selected in the Zapier editor

If you only want to send notes for fulfilled orders, add a filter step after the trigger. Set the rule so the Zap continues only when the WooCommerce order status matches your fulfilment state, such as completed.

Add a five-day delay

For post-purchase follow-up, add Delay by Zapier after the filter and set the delay to five days.

Add the Scribeless action

  1. Add the final action step.

  2. Choose Scribeless.

  3. Set the action event to Add Recipients.

  4. Connect your Scribeless account.

  5. If you are in more than one Scribeless organization, choose the organization that has the campaign you want to use.

Scribeless action connected after the WooCommerce trigger

Map the order fields

In the Scribeless Configure tab:

  1. Choose the campaign in Campaign ID.

  2. Map the customer's first name and last name from the WooCommerce billing or shipping fields.

  3. Map the address from billing or shipping fields, depending on where the handwritten note should be sent.

  4. Map company name if you collect it at checkout.

  5. Optionally map the order number, product name, or customer segment into a custom field if your campaign message uses it.

Use shipping address fields when the note should go to the delivery address. Use billing address fields when the note should go to the purchaser.

Scribeless recipient fields ready to map from WooCommerce order data

Test and turn on

  1. Test with a recent internal order or a safe test order.

  2. Confirm the recipient appears in the correct Scribeless campaign.

  3. Check the address source, especially if billing and shipping addresses differ.

  4. Turn on the Zap once the test recipient looks correct.

Did this answer your question?