Add Calendly invitees 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 when a meeting is booked in Calendly, optionally filter or delay the workflow, then add the invitee 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 someone books a Calendly meeting, Zapier sends the invitee's name, company details, meeting details, and postal address fields to Scribeless and adds the person as a recipient in your chosen campaign.
Use this for B2B workflows such as:
Sending a confirmation postcard after a meeting is booked.
Sending a founder note when a high-value prospect books a demo.
Sending a reschedule postcard after a no-show.
Sending a handwritten next-step note after an attended sales, customer success, partner, or donor meeting.
What you need
A Calendly account connected to Zapier.
A Calendly event type that collects the fields Scribeless needs, especially recipient name and postal address.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to both Calendly and Scribeless.
A paid Zapier plan if you want to add
Filter by Zapier,Delay by Zapier, or Paths.
Calendly usually provides the invitee's name, email, event type, scheduled time, and answers to invitee questions. If your campaign sends physical mail, add required address questions to the Calendly booking form or enrich the address in an earlier CRM step before the Scribeless action.
Recommended Zap structure
For a simple meeting-booked follow-up:
Trigger:
Calendly-Invitee Created.Action:
Scribeless- add recipient to campaign.
For a more controlled sales or customer success workflow, add these steps before Scribeless:
Filter: continue only for the right event type, routing form answer, account tier, region, or qualification status.
Delay: wait until the right send moment, such as after the scheduled meeting time.
For no-show follow-up, use Calendly's no-show trigger or add a CRM step that only continues when the meeting outcome is marked as no-show.
Build the Calendly trigger
In Zapier, create a new Zap.
Set the trigger app to
Calendly.Choose
Invitee Createdas the trigger event. This starts the Zap when an invitee schedules an event.Connect your Calendly account.
Choose the event type if Zapier asks you to narrow the trigger.
Test the trigger so Zapier can load a recent booked meeting.
Use a test booking that includes the same fields your real recipients will provide. If your Scribeless campaign needs a postal address, make sure the test booking includes address answers.
Add optional filters
Add a filter if only some booked meetings should receive handwritten mail. Common B2B filters include:
Event type is
Enterprise demo,ABM consultation,Renewal review, or another high-value meeting.Company size, account tier, or lead score meets your threshold.
Country is one Scribeless can mail to for the campaign.
A Calendly routing form answer indicates the person is a qualified prospect.
The meeting owner is a specific sales, customer success, or partnerships team.
Place the filter after the Calendly 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 a specific milestone rather than immediately after booking.
Useful delay patterns include:
Send a confirmation postcard immediately after booking.
Wait until after the scheduled meeting time before sending a next-step note.
Wait one business day after a demo before sending a founder or account executive note.
Wait after a no-show before sending a reschedule postcard.
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 invitee should receive mail.
Map the fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map the invitee's first name and last name from Calendly.
Map address fields from Calendly invitee questions, a previous CRM lookup step, or another enrichment step.
Map company name if you collect it in Calendly or retrieve it from your CRM.
Optionally map email, phone, event type, meeting owner, meeting date, or qualification answers if your Scribeless campaign uses those values as merge variables.
If Calendly provides the invitee's full name as one field, use Zapier Formatter or your CRM data to split it into first and last name before the Scribeless action.
If a Calendly answer does not appear in the field picker, retest the trigger with a booking that includes that answer. Zapier often needs a complete sample event before all fields are available for mapping.
Test and turn on
Test the Zap with a safe internal Calendly booking.
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 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 Calendly custom questions or a CRM lookup.
Troubleshooting
The invitee 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
Calendly does not collect postal address fields by default. Add address questions to the Calendly booking form, or add a CRM lookup step before Scribeless and map the address from the CRM record.
Only some Calendly events should send mail
Use a filter based on event type, routing form answers, owner, region, account tier, or qualification fields. For more complex branching, use Zapier Paths or separate Zaps for each event type.
The note should be sent after the meeting, not when it is booked
Add a delay until after the scheduled event time, or trigger from the system where your team records the meeting outcome. For attended meetings, many teams use CRM meeting status as the more reliable trigger.