Scheduling, SMS & spam integration

Create Calendly booking links from form responses

CA

Ask the qualifying questions in HelloForms and paste a Calendly personal access token plus the event type URI. Each submission creates a single-use booking link for that event type, so only qualified respondents can take a slot.

What the Calendly integration does

  • One booking link per submission, created through Calendly's API rather than a shared public link.
  • Qualify before booking, so bad-fit calls drop out before they reach your calendar.
  • The structured answers stay in your HelloForms inbox alongside the link that was issued.

What it looks like

A single-use Calendly booking link for your chosen event type, recorded with the submission.

HelloForms — response

Removals enquiry · #4821

Full name
Priya Raman
Email
priya@northgate.co
Service needed
Office move
Budget
£2,000 – £5,000

Calendly — record created

Priya Raman

Created from Removals enquiry · #4821

Full name
Priya Raman
Email
priya@northgate.co
Service needed
Office move
Budget
£2,000 – £5,000
Demo data: a HelloForms response on the left, and how it arrives in Calendly on the right.

How to connect Calendly to your form

  1. 1

    In Calendly, create a personal access token with scheduling access.

  2. 2

    Copy the API URI of the event type submissions should book into.

  3. 3

    Paste both below and send a test event — Calendly returns a one-time booking link.

What you’ll need

  • Calendly personal access token.
  • Event type URI — Copy it from GET /event_types, or from the event type's API details.

Credentials are stored server-side and never rendered in your published form. Every delivery attempt is logged, transient failures are retried with backoff, and repeated failures disable the destination instead of retrying forever.

Configuration template and sample payload

Download a filled-in checklist of every value the Calendly destination asks for, plus an example of exactly what Calendly receives for one submission — useful for planning a mapping or handing the setup to a developer.

Every field the "Add integration" dialog asks for, with placeholders to fill in. Keep it as documentation of your Calendly mapping — do not commit a completed copy to a public repository.

{
  "$schema": "https://helloforms.net/integrations/config-template.schema.json",
  "helloforms": {
    "destination": "calendly",
    "label": "Calendly",
    "docs": "https://helloforms.net/integrations/calendly"
  },
  "enabled": true,
  "events": [
    "submission.created"
  ],
  "credential": {
    "label": "Calendly personal access token",
    "value": "<paste-your-token-here>"
  },
  "config": {
    "eventTypeUri": "https://api.calendly.com/event_types/AAAAAAAAAAAAAAAA"
  },
  "includedQuestions": [
    "Full name",
    "Email",
    "How can we help?"
  ],
  "notes": [
    "Never commit a filled-in copy of this file to a public repository.",
    "Values are entered in HelloForms → your form → Integrations; this file is a checklist and a record of your mapping."
  ]
}

Calendly integration FAQs

Who uses it

  • Demo requests that need budget and use-case answers before a call.
  • Agencies screening project enquiries before scheduling.
  • Support escalations that only warrant a call after triage questions.

Build a form that feeds Calendly today

Every destination is included on every plan — no per-integration add-ons.