Add Recharge subscription events 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 Recharge subscription or charge event, optionally filter for the right 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 a subscription charge succeeds in Recharge, Zapier sends the customer's name and address to Scribeless and adds them to your chosen campaign.
Use this for ecommerce retention workflows such as:
Sending a thank-you note after a subscription charge succeeds.
Sending a handwritten surprise to VIP or high-LTV customers.
Sending a win-back offer by mail when a customer returns.
Sending a retention note after a failed or churn-risk subscription moment.
If your Scribeless note includes a QR code, you can use scan engagement as a signal for loyalty, win-back, or retention automation.
What you need
A Recharge account connected to Zapier.
Subscription records with usable shipping or billing address data.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to Recharge and Scribeless.
A paid Zapier plan if you want filters, delays, Paths, or webhook steps.
Recommended Zap structure
For a post-charge handwritten thank-you flow:
Trigger:
Recharge- a successful charge, subscription event, or customer event.Filter: continue only when the charge or customer segment qualifies for the campaign.
Delay: wait three to seven days, depending on fulfilment timing and customer experience.
Action:
Scribeless-Add Recipients.
For a churn-risk or win-back flow, trigger from the Recharge event that represents the customer moment, then use a filter to route only the right subscription status or segment into Scribeless.
Build the Recharge trigger
In Zapier, create a new Zap.
Set the trigger app to
Recharge.Choose the event that matches your send moment, such as a successful charge, subscription update, or customer event.
Connect your Recharge account.
Test the trigger so Zapier can load a recent subscription or customer event.
Use a test record that includes the customer's name, email, subscription status, order or charge context, shipping address, and any discount or loyalty variables you expect to print.
Add timing and eligibility rules
Add a filter if only some Recharge events should trigger handwritten mail. Common filters include:
Charge status is successful.
Subscription count, order count, lifetime value, product, plan, SKU, or bundle matches the campaign.
Customer segment, loyalty tier, VIP status, subscription tenure, or churn-risk marker matches your playbook.
Shipping or billing address fields are complete.
Add Delay by Zapier when the note should arrive after the product experience. For subscription thank-you notes, a three-to-seven-day delay often works better than immediate mail. For save-the-customer campaigns, the delay should match your retention window.
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 filters, delays, routing, lookup, or enrichment steps that decide whether the Recharge customer should receive mail.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map the customer's first name and last name.
Map shipping address fields into
Address line 1,Address line 2, city, state or region, postal code, and country code.Map product name, subscription plan, order number, loyalty tier, discount code, renewal date, or customer segment if your campaign uses those merge variables.
Optionally map email or phone for reconciliation, tracking, or reporting.
Use shipping address fields when the note should go to the product recipient. Use billing address fields only when the note should go to the purchaser or account holder.
Send QR scan activity back to Recharge
Keep QR response handling separate from recipient creation. The first Zap adds recipients to Scribeless; the second records offline engagement back into your retention stack.
Common follow-up actions include:
Tag the customer for retargeting or loyalty follow-up.
Trigger a win-back or upgrade automation.
Send a visit event into your attribution stack.
Add the customer to a repeat-purchase audience.
Fire a webhook that updates Recharge-adjacent lifecycle tooling.
Use a stable matching key such as email, customer ID, subscription ID, or order ID.
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 source, especially if billing and shipping addresses differ.
Confirm any discount code, product, QR, or loyalty merge variable appears correctly.
Turn on the Zap once the test recipient looks correct.