Add Attio records 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 an Attio deal, lifecycle, or customer milestone, optionally filter or delay the workflow, then add the 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 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 the right record changes in Attio, Zapier sends the recipient's name, company, postal address, and deal or lifecycle context to Scribeless and adds the person to your chosen 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 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 also send scan engagement back into Attio in a separate automation. For example, a QR scan can create a task for the owner, update person or company attributes, or move the record into a higher-intent follow-up workflow.
What you need
An Attio account connected to Zapier.
A Scribeless campaign that is ready to receive recipients.
Attio person, company, 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 Attio and Scribeless.
A paid Zapier plan if you want to add
Filter by Zapier,Delay by Zapier, Paths, or multi-step enrichment.
Attio is often the CRM and workflow source of truth, but it may not hold every mailing address on every deal record. If the deal only has a linked person or company, add a lookup step before Scribeless so the Zap can retrieve the recipient and postal fields you need.
Recommended Zap structure
For a closed-won handwritten mail workflow:
Trigger:
Attio-Record Updated.Filter: continue only when the object is the deal object and the stage or status is
Closed won.Optional lookup: find the linked person or company if the trigger record does not include mailing fields.
Action:
Scribeless-Add Recipients.
For other lifecycle workflows, use the Attio record update that best represents the send moment, then filter on the relevant object, stage, list entry, owner, account tier, renewal date, or customer status.
Build the Attio trigger
In Zapier, create a new Zap.
Set the trigger app to
Attio.Choose
Record Updatedas the trigger event. Attio describes this trigger as firing when values on a record, such as a person, company, or deal, are updated.Connect your Attio account.
Choose the object that should start the workflow, such as deals, people, companies, or a custom object.
Test the trigger so Zapier can load a recent record with the same fields your Scribeless campaign will use.
Use a test record that includes the stage, owner, linked person or company, address fields, and any merge variables you expect to map into the handwritten note.
Add optional filters and delays
Add a filter if only some Attio updates should trigger handwritten mail. Common B2B filters include:
Deal stage changed to
Closed won,Demo completed,Renewal risk, or another direct mail trigger.Object is the deal, person, company, or custom object your workflow expects.
Account tier, contract value, lifecycle stage, owner team, or region matches the campaign.
Renewal date, upsell date, or customer milestone is present.
Postal address fields are complete, or an address lookup step returned a valid result.
Place the filter after the Attio trigger and before the Scribeless action. If the filter does not pass, Zapier stops the run and no recipient is added to Scribeless.
Add Delay by Zapier when the handwritten note should arrive after a specific milestone rather than immediately after the Attio update. Useful delay patterns include waiting until the next business day after a demo, waiting a few days after closed won before onboarding mail, or delaying renewal outreach until the right account-review 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 has the campaign you want to use.
The Scribeless action should come after any filters, delays, routing, lookup, or enrichment steps that decide whether the Attio record should receive mail.
Map the recipient fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map Attio'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 company, deal name, owner, pipeline, stage, renewal date, account tier, or customer success manager if your Scribeless campaign uses those values as merge variables.
Optionally map email or phone if your team uses them for reconciliation, tracking, or reporting.
If the trigger record is a deal, the mailing fields may live on the linked person or company rather than the deal itself. Add an Attio lookup step or another data lookup before Scribeless, then map the address from that step.
If a field does not appear in the picker, retest the Attio trigger with a record that has that attribute populated. Zapier often needs a complete sample record before all fields are available for mapping.
Send QR scan activity back to Attio
If your Scribeless campaign uses a QR code, keep the response workflow separate from the send workflow. The first Zap adds recipients to Scribeless; the second Zap records the offline intent signal back in Attio.
Common Attio follow-up actions include:
Create a task for the account owner or customer success manager.
Update a person or company attribute such as
Last direct mail QR scan date.Add the record to a follow-up list.
Update a deal, renewal, or expansion workflow field so the next team action is visible in Attio.
Use a stable matching key such as email, Attio record ID, company domain, or another unique attribute so the QR response updates the right person or company.
Test and turn on
Test the Zap with a safe internal Attio record.
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 linked records, custom attributes, or enrichment steps.
Troubleshooting
The Attio record 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 Attio trigger record may not be the record that stores postal data. Add a lookup step for the linked person or company, retest with a complete sample record, or add address attributes to the object your Zap uses.
Every record update is triggering mail
Use a filter based on object type, list, pipeline, stage, lifecycle status, renewal date, owner, or account tier. For more complex branching, use Zapier Paths or separate Zaps for each Scribeless campaign.
QR scan activity is not updating Attio
Keep the QR response workflow separate from the send workflow. Confirm the QR scan trigger is receiving events, then confirm the Attio action finds the intended record by email, record ID, domain, or another unique matching attribute.