Add Copper opportunities 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 Copper opportunity or lifecycle milestone, then add the related person 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 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 Copper opportunity changes stage, Zapier sends the person's name, company, postal address, and deal context to Scribeless and adds the person to your chosen campaign.
Use this for B2B workflows such as:
Sending an onboarding welcome letter when an opportunity moves to
Won.Sending a thank-you note the day after a completed demo.
Sending a save-the-account postcard before a renewal date.
Sending a customer success note from a renewal or upsell trigger.
If your Scribeless note includes a QR code, you can send scan engagement back into Copper in a separate workflow. For example, a QR scan can create an owner task, update a people or company field, log activity on the record, or branch a follow-up workflow.
What you need
A Copper account connected to Zapier.
A Scribeless campaign that is ready to receive recipients.
Copper people or company records with the postal fields Scribeless needs: first name, last name, address line 1, city, postal code, and country.
A Zapier account connected to Copper and Scribeless.
A paid Zapier plan if you want filters, delays, Paths, or multi-step lookups.
Copper is usually strongest as the trigger source for stage, owner, pipeline, renewal, and relationship context. Mailing fields may live on the related person or company record rather than the opportunity itself, so plan for a lookup step if the trigger sample does not include the full address.
Recommended Zap structure
For a closed-won or renewal workflow:
Trigger:
Copper-Updated Opportunity Stage.Filter: continue only when the opportunity reaches the stage that should receive mail.
Optional lookup: find the related person or company if the trigger payload does not include postal fields.
Optional delay: wait until the next business day, a few days after a demo, or the correct renewal window.
Action:
Scribeless-Add Recipients.
Build the Copper trigger
In Zapier, create a new Zap.
Set the trigger app to
Copper.Choose
Updated Opportunity Stage.Connect your Copper account.
Choose the pipeline or stage details Zapier asks for.
Test the trigger so Zapier can load a recent opportunity with representative owner, company, stage, value, contact, and address data.
Use a test opportunity that looks like a real send candidate. If the sample record is missing address fields, add a Copper lookup step after the trigger to find the related person or company before you add the Scribeless action.
Add optional filters and delays
Add a filter if only some Copper opportunities should trigger handwritten mail. Common filters include:
Stage changed to
Won,Demo completed,Renewal due,Upsell opportunity, or another send milestone.Pipeline, owner team, territory, account tier, industry, or opportunity value matches the campaign.
Renewal date, onboarding date, meeting date, or contract end date is inside the correct window.
The related person or company has a complete postal address.
Place the filter after the Copper trigger and before the Scribeless action. If the filter does not pass, no recipient is added to Scribeless.
Add Delay by Zapier when the handwritten note should arrive after the milestone rather than immediately after the stage update. A next-business-day delay works well after demos. A three-to-seven-day delay can work better for onboarding or renewal mail.
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 Copper opportunity should receive mail.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map Copper's first name and last name fields to
First NameandLast Name.Map postal fields into
Address line 1,Address line 2, city, state or region, postal code, and country code.Map company, opportunity name, pipeline, stage, owner, renewal date, customer success manager, or account tier if your campaign uses those merge variables.
Optionally map email or phone for reconciliation, tracking, or reporting.
If the trigger record is an opportunity, the mailing address may come from the linked person or company. Add a Copper lookup step before Scribeless, then map the address from that step. If a field does not appear in the picker, retest the Copper trigger with a complete sample record.
Send QR scan activity back to Copper
Keep QR response handling separate from recipient creation. The first Zap adds recipients to Scribeless; the second records offline intent back in Copper.
Common Copper follow-up actions include:
Create a task for the opportunity or account owner.
Update a custom intent field on the person or company.
Add an activity note to the record.
Move a renewal or expansion opportunity into a follow-up stage.
Trigger another workflow from the updated field.
Use a stable matching key such as email, Copper record ID, account domain, or another unique attribute.
Test and turn on
Test the Zap with a safe internal Copper opportunity.
Confirm the recipient appears in the correct Scribeless campaign.
Check that the name, address, company, and merge variables are complete.
Review your filter and delay logic if the recipient should only be added after qualification or timing checks.
Turn on the Zap once the test recipient looks correct.
For live workflows, monitor the first few Zap runs and Scribeless recipients, especially when address data comes from a related person or company rather than the opportunity trigger itself.
Troubleshooting
The Copper opportunity 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
The opportunity may not store postal data. Add a lookup step for the linked person or company, retest with a complete sample record, or sync postal fields into the record your Zap uses.
Every stage update is triggering mail
Use a filter based on stage, pipeline, owner team, lifecycle status, renewal date, account tier, territory, or a custom trigger field. For more complex branching, use Zapier Paths or separate Zaps for each Scribeless campaign.