Add SavvyCal 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 scheduled in SavvyCal, optionally qualify 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 card or note format, handwriting style, message, sender details, 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 SavvyCal meeting, Zapier sends the invitee's details to Scribeless and adds that person to the campaign you choose.
Use this for B2B scheduling and lead-capture workflows such as:
Sending a confirmation postcard after a qualified 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.
The automation is most useful when SavvyCal is already collecting or routing high-intent meetings: demo requests, account expansion calls, onboarding calls, executive briefings, partner introductions, or donor conversations.
What you need
A SavvyCal account connected to Zapier.
A SavvyCal scheduling link or routing flow that captures the fields Scribeless needs.
A Scribeless campaign that is ready to receive recipients.
A Zapier account connected to both SavvyCal and Scribeless.
A paid Zapier plan if you want to add
Filter by Zapier,Delay by Zapier, or Paths.
SavvyCal usually provides meeting details such as invitee name, email, selected time, calendar link, and answers to booking questions. If your campaign sends physical mail, collect postal address fields in the booking flow or add a CRM lookup before the Scribeless action.
Recommended Zap structure
For a simple meeting-booked follow-up:
Trigger:
SavvyCal- meeting scheduled.Action:
Scribeless- add recipient to campaign.
For a more controlled workflow, add these steps before Scribeless:
Filter: continue only for the right meeting type, routing answer, territory, account tier, or lead score.
Delay: wait until the best send moment, such as after the scheduled meeting time.
Lookup: retrieve the contact, company, or postal address from your CRM if SavvyCal does not collect every field directly.
Build the SavvyCal trigger
In Zapier, create a new Zap.
Set the trigger app to
SavvyCal.Choose the meeting scheduled trigger event available in your Zapier account.
Connect your SavvyCal account.
Choose the scheduling link, event type, or booking source if Zapier asks you to narrow the trigger.
Test the trigger so Zapier can load a recent booked meeting.
Use a test booking that looks like a real recipient. If your campaign needs postal address, company name, meeting owner, or qualification answers, include those values in the test event.
Add optional filters
Add a filter if only some booked meetings should receive handwritten mail. Common filters include:
Meeting type is
Enterprise demo,Renewal review,Partner intro, or another high-value event.A routing answer shows the person is a qualified prospect or customer.
Company size, account tier, or lead score meets your threshold.
Country or region is supported by the Scribeless campaign.
Place the filter after the SavvyCal 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 milestone rather than immediately after booking. For example, send a confirmation postcard right away, wait until after the meeting for a next-step note, or 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.
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.
Map the fields
In the Scribeless Configure tab:
Choose the campaign in
Campaign ID.Map the invitee's first name and last name from SavvyCal.
Map address fields from SavvyCal booking questions, a CRM lookup step, or another enrichment step.
Map company name if you collect it in SavvyCal or retrieve it from your CRM.
Optionally map email, phone, meeting type, owner, scheduled time, routing answers, or qualification fields if your campaign uses those values as merge variables.
If SavvyCal provides the invitee's full name as one field, use Zapier Formatter or your CRM data to split it before the Scribeless action. If an answer does not appear in the field picker, retest the trigger with a booking that includes that answer.
Test and turn on
Test the Zap with a safe internal SavvyCal 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 mail should only send after qualification or meeting attendance.
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 booking 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 points at the right Scribeless organization and campaign.
Address fields are missing
SavvyCal may not collect postal address fields by default. Add address questions to the booking flow, or add a CRM lookup step before Scribeless.
Only some SavvyCal meetings should send mail
Use a filter based on meeting type, routing answers, owner, region, account tier, or qualification fields.
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.