Connect Zunoform to Calendly via Zapier
This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Calendly button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.
Connects form responses to Calendly — most often by inviting the respondent to book, or by pushing their details somewhere else once they have.
The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.
Read this before building it. Zunoform has a native scheduler question: the respondent picks a time inside the form, it syncs with Google or Outlook Calendar, and a unique database constraint prevents double-booking. It is on the free plan. If the only reason you want Calendly is booking a meeting from a form, you do not need Calendly, Zapier, or this page — use the scheduler question and skip all three.
Example workflow
Qualify an enquiry before sharing a booking link
If your team already manages availability in Calendly, use the form to collect context and then provide the appropriate booking link. The enquiry and the booking are separate events: submitting the form does not prove that the respondent selected a meeting time.
Prepare your Calendly account
Decide whether a fixed booking link is enough; you can place one on the ending page without Zapier. For an automated handoff, inspect Calendly's current actions and add an email step if that is how you intend to deliver the link.
Four steps, start to finish
Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.
Create a Zap with a Catch Hook trigger
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.
Paste the URL on the Zapier card in Zunoform
Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.
Submit a test response so Zapier learns the shape
Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.
Map your fields to Calendly
Add an action step and choose Calendly. Connect your account, then pick the action that matches what Calendly currently exposes for invitees and scheduled events. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.
Suggested field mapping
Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.
- Reply email
- Destination: Recipient in your email step
- Only needed when the workflow sends an invitation.
- Meeting purpose
- Destination: Routing condition
- Choose an existing event type that fits the enquiry.
- Configured Calendly booking URL
- Destination: Ending button or invitation body
- A link invites booking; it does not reserve a slot.
- Enquiry reference
- Destination: Your tracking record
- Use a separate booking signal to mark the meeting as scheduled.
What Zapier receives
The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.
Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Calendly action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.
Test before sharing your form
Complete the form, follow the invitation and book a test meeting. Then repeat without booking: your process should keep that second enquiry unbooked rather than counting both as appointments.
If the result is missing or wrong
A Calendly trigger such as a newly created invitee starts a Zap from Calendly; it is not an action that creates a meeting from a form response. Check the direction of each step before configuring the workflow.
Check the current Calendly actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.
Questions people ask
Why does this page recommend against itself?
Because a form that ends by sending someone to a second site to book loses people, and because we have the feature. The scheduler is a native question type with calendar sync and double-booking protection, included on the free plan. Keeping Calendly makes sense if your whole team's availability logic already lives there.
Can Zunoform replace Calendly entirely?
For booking a time as part of a form, yes — see our Calendly alternative page for where it does and does not match up. For standalone booking pages with complex routing and team round-robin, Calendly is the more complete product and we are not going to claim otherwise.
Is this a native Zunoform integration?
No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.
Ready when you are
Better forms.
Better data.
Start with a conversation, a document or a single page.
Unlimited forms and 500 responses per month on Free.
No card required.
- No credit card
- Unlimited forms
- 500 responses / month