Add Pipedrive deals 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 Pipedrive deal, lifecycle, or customer milestone, then add the contact 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 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 Pipedrive deal reaches the right sales or customer milestone, Zapier sends the person, organization, postal address, and deal context to Scribeless and adds the recipient to your selected campaign.
Use this for B2B workflows such as:
Sending an onboarding welcome letter when a deal moves to closed won.
Sending a thank-you note the day after a completed demo.
Sending a renewal-date postcard before a key account reaches risk.
Sending a customer success note after a renewal or upsell trigger.
If your Scribeless campaign uses a QR code, you can also send scan activity back into Pipedrive in a separate automation. For example, a QR scan can create an activity, update a deal field, add a note, or help an owner prioritize follow-up from offline intent.
What you need
A Pipedrive account connected to Zapier.
A Scribeless campaign that is ready to receive recipients.
Pipedrive person, organization, or deal records with the postal fields Scribeless needs: first name, last name, address line 1, city, postal code, and country.
A Zapier account connected to both Pipedrive and Scribeless.
A paid Zapier plan if you want filters, delays, Paths, or multi-step enrichment.
Pipedrive is often strong for deal ownership and pipeline context, but postal address data may live on the person, organization, or a custom field. Decide where the mailing address should come from before you map the Scribeless action.
Recommended Zap structure
For a simple sales milestone send:
Trigger:
Pipedrive-Updated Deal Stage.Optional filter: continue only when the new stage is closed won, renewal risk, demo completed, or another send trigger.
Action:
Scribeless-Add Recipients.
For higher-control workflows, add these steps before Scribeless when needed:
Filter: continue only for the right stage, pipeline, deal value, owner, account tier, country, or customer segment.
Delay: wait until the next business day, a renewal date, or a defined follow-up window.
Lookup or enrichment: pull the person, organization, address, or account fields if the trigger payload does not include everything Scribeless needs.
Build the Pipedrive trigger
In Zapier, create a new Zap.
Set the trigger app to
Pipedrive.Choose
Updated Deal Stageif the send should start when a deal moves through the pipeline.Connect or reconnect your Pipedrive account.
Test the trigger so Zapier can load a recent deal with the same fields your campaign will use.
Use a test deal that includes the person, organization, owner, stage, and address fields you expect to map into Scribeless. If the trigger is broader than your send rule, add a filter before the Scribeless action.
Add optional filters
Add a filter if only some Pipedrive events should trigger handwritten mail. Common B2B filters include:
Deal stage changed to
Won,Demo completed,Renewal due,Upsell opportunity, or another milestone.Pipeline equals your target sales, onboarding, renewal, or expansion pipeline.
Deal value, expected close date, renewal date, account tier, or owner team meets your send criteria.
Person or organization country is one Scribeless can mail to for the campaign.
Address fields are present before the recipient reaches Scribeless.
Place the filter after the Pipedrive trigger and before the Scribeless action. If the filter does not pass, Zapier stops the run and no recipient is added to Scribeless.
Add an optional delay
Add a delay when the handwritten note should arrive after the milestone rather than immediately when the Pipedrive update happens.
Useful delay patterns include:
Wait until the next business day after a demo before sending a thank-you note.
Wait a few days after closed won so the welcome letter supports onboarding.
Wait until a renewal or save-account date.
Space out sends if multiple deal updates happen at once.
In Zapier, add Delay by Zapier after the trigger or filter, then choose the timing rule that matches your workflow. If your Scribeless account uses a suitable flow, you can also handle timing in Scribeless.
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 has the campaign you want to use.
The Scribeless action should come after any filters, delays, routing, or enrichment steps that decide whether the Pipedrive contact should receive mail.
Map the fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map Pipedrive's person first name and last name to
First NameandLast Name.Map postal fields into
Address line 1,Address line 2, city, state or region, postal code, and country code.Map organization name, deal title, owner, pipeline, stage, close date, renewal date, demo date, or customer success owner if your Scribeless campaign uses those values as merge variables.
Optionally map email or phone if your team uses them for reconciliation, tracking, or later reporting.
If a field does not appear in the picker, retest the Pipedrive trigger with a deal that includes data in that field. If Pipedrive stores address data on a related person or organization rather than the deal itself, add a lookup step before Scribeless and map the address from that step.
Send QR scan activity back to Pipedrive
If your Scribeless note includes a QR code, create a separate automation for offline response signals. The exact trigger depends on how your Scribeless account exports QR scan events, but the destination action in Pipedrive is usually one of:
Create an activity for the deal owner.
Add a note to the deal, person, or organization.
Update a custom deal field such as
Last direct mail QR scan date.Move the deal to a follow-up stage if your team uses pipeline stages for response handling.
Keep this as a separate Zap from the send workflow. The first Zap adds recipients to Scribeless; the second Zap records the response signal back in Pipedrive.
Test and turn on
Test the Zap with a safe internal Pipedrive deal.
Confirm the recipient appears in the correct Scribeless campaign.
Check that the name, address, company, deal context, and merge variables are complete.
Review your filter and delay logic if the recipient should only be added after a qualification or timing step.
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 custom fields, related records, or enrichment steps.
Troubleshooting
The deal 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
Pipedrive deal triggers may not include every field from the related person or organization. Add a lookup step, sync postal fields into Pipedrive, or add enrichment before Scribeless.
Every stage change is triggering mail
Use a filter based on the new stage, pipeline, status, owner team, deal value, renewal date, or account tier.
QR scan activity is not updating Pipedrive
Keep the QR response workflow separate from the send workflow. Confirm the QR scan trigger is receiving events, then confirm the Pipedrive action updates the intended deal, person, or organization by a stable ID or email.