> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/integrations/calendar-integrations/calendly.md).

# Calendly

### Data flows

Unfortunately, Calendly only provides partial support for data prepopulating their calendar form, and no support for reading information from their calendars. Because of this, we do not recommend Calendly as a calendar solution.

<table data-full-width="true"><thead><tr><th>Spara can prepopulate...</th><th>Spara can read from submitted calendar...</th><th>Integration Notes</th></tr></thead><tbody><tr><td><ul><li>Email</li><li>First name</li><li>Last name</li><li>Name</li></ul></td><td><em>None</em></td><td><p>Spara should capture email address before showing a Calendly calendar.</p><p>Spara will prepopulate Calendly's form email field with this info.</p></td></tr></tbody></table>

### Implementation

{% hint style="info" %}
How Spara's AI uses your Calendly calendar must be configured by Spara internally. Please contact your customer service representative to get started.
{% endhint %}

Calendly calendars are embedded as an iFrame within Spara's interface. All Calendly UX can be used by your lead in this format.

Spara requires a Calendly calendar URL in the form:

`https://calendly.com/your-name/calendar-name`

To find this URL, log into the Calendly website. Click the “Share” button for a specific calendar to find this URL.

### Multiple sales reps with separate calendars

If you have multiple sales reps and want bookings to land on the correct rep's calendar, you can pass the specific Calendly URL on a **per-lead basis** as a field. The Voice agent uses the field-supplied URL when booking, so the meeting lands on the assigned rep's calendar.

This requires you to **assign the rep (and their calendar URL) on each lead ahead of time** — for example, via your CRM sync or when creating the lead through the API. Spara does not currently support round-robin assignment or automatically choosing a rep on Spara's side.

{% hint style="warning" %}
This pattern requires configuration work on Spara's side to fully set up. Contact your Spara representative before relying on it for a live use case.
{% endhint %}

{% hint style="info" %}
This pattern works well for high-touch outgoing flows where leads are pre-assigned to a rep before the call. For inbound flows where any rep is acceptable, a single shared calendar is usually simpler.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spara.com/integrations/calendar-integrations/calendly.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.