Calendly lets visitors book time with you directly from a Formulayt gate. We pass details they’ve already entered so they don’t need to type them again, and we can also support Routing (round-robin) event types when enabled.


Important: If your Calendly event type includes required questions, make sure those fields are on your gate and/or mapped. If a required field isn’t provided via the mapping, the scheduler will still open—but the visitor will have to complete those questions in Calendly.

What you’ll need

  • A Calendly event type to use (or a Routing event, if you’re using round-robin).

  • The event’s share link (from Calendly → Share).

    • Standard event links start with https://calendly.com/...

    • Routing links include /d/ in the URL.

  • Access to your Formulayt workspace (Apps & Gate editor).

Step 1 — Activate the Calendly app

  1. Go to Apps → Calendly.

  2. Click Activate.


You’ll see Basic settings, Custom fields, and—if enabled—Routing tabs.

Step 2 — Fill in Basic settings

Field

What to enter

Default Calendly scheduler URL

Paste the Share link from your Calendly event type. It should start with https://calendly.com/....

Support routing (round robin) event types

Turn on if you’re using Routing links (they include /d/). This reveals extra routing options.

Tip: You can override the default link per gate later (see Step 5).

Step 3 — (Optional) Configure Routing event types


Turn Support routing on to see these fields:

  • Name / Email / Country positions – Pick where these appear in your Calendly Routing form (e.g., a1, a2, a3). These must match the order in Calendly’s routing questions.

  • Custom fields (routing event types) – Map any additional gate fields to positions in your routing form (e.g., a4, a5).


Minimum routing data: Most routing flows expect Name, Email, and often Country. Make sure you assign the correct positions and that those fields exist on your gate.

Step 4 — Map Custom fields (standard event types)


Under Custom fields, map any extra data you want to pass to Calendly (for non-routing events):

  • Left: your Formulayt field

  • Right: the Calendly parameter (usually a1, a2, …)


Automatically sent for standard events:

If present on your gate, we prefill name and email automatically (no mapping required).

Step 5 — (Optional) Override per gate


When building a gate:

  • Set Optional scheduler link override to use a different Calendly link for that gate (e.g., a different event type or routing flow).

  • If left blank, the Default Calendly scheduler URL from app settings is used.

Step 6 — Use the gate


When you choose Calendly as the gate type and the gate is submitted:

  1. We prefill Calendly with data from your gate.

    • Standard events: we send name and email plus any Custom fields you mapped (a1, a2, …).

    • Routing events: we send values into the positions you configured (e.g., a1 Name, a2 Email, a3 Country) and any additional routing custom fields.

  2. We open the Calendly popup so the visitor can pick a time.

Testing checklist

  • Default URL: In Basic settings, a valid https://calendly.com/... link is set.

  • Routing (if used):

    • Support routing is on.

    • Name/Email/Country positions match the order of questions in your Calendly routing form.

  • Custom fields: Any extra fields you expect are mapped to the correct a1, a2, … keys.

  • Per-gate override: If you’re testing a different event, paste its share link in the gate’s Optional scheduler link override.

  • End-to-end test:

    1. Submit the gate on a test page.

    2. Calendly opens.

    3. Prefilled values appear where expected.

    4. Complete a booking to verify your downstream notifications.


If the popup opens but some fields are blank, check your field presence (the fields must exist on the gate) and your mapping keys (a1, a2, …).

Important notes & limitations

  • UI & behaviour inside the widget (calendar, questions, styling) are controlled by Calendly. Edit those in Calendly, not Formulayt.

  • Routing detection: We treat a link as Routing when the URL contains /d/ and the Support routing toggle is on.

  • Autofill: For routing links, we add Calendly’s autofill=true parameter to prefill fields where possible.

  • Fields must exist on the gate: If a mapped field isn’t present on the gate, we can’t send its value to Calendly.

Troubleshooting


“The widget opens but prefill is missing.”

Check the field exists on the gate and your mapping uses the right key (a1, a2, …). For routing, confirm the position matches Calendly’s question order.


“Routing doesn’t seem to work.”

Confirm the URL contains /d/, the Support routing toggle is on, and the Name/Email/Country positions match your routing form. If you changed your routing form in Calendly, update the positions here too.


“We need a different event for this campaign.”

Use the gate’s Optional scheduler link override and paste the other event’s share link.

Need help?


If you’ve followed the steps and it’s still not behaving:

  1. Share the page URL and which gate you’re using.

  2. Paste the Calendly link you expect to load.

  3. If it’s a routing flow, share a screenshot of your routing form question order (so we can verify positions).


Raise a support ticket and we’ll help you get it over the line.