> 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/custom-calendar.md).

# Custom Calendar

How to integrate with a custom calendar routing page.

### Data flows

Custom calendar allows Spara to support advanced routing setups where a form platform (e.g., HubSpot or Marketo) triggers a separate scheduling platform (e.g., Chili Piper, Default, etc.), or where a scheduling tool can be directly embedded. The scheduler must fire a postMessage event upon booking, so Spara can track call scheduling within the platform.

> Note: This solution is intended for cases where a native Spara calendar integration alone will not work. Because this setup is fully configurable, capabilities depend on the scheduler being used.

<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>Any fields - customizable</td><td></td><td>Spara can detect a meeting scheduled only if the scheduler fires a success meeting booked event</td></tr></tbody></table>

### Implementation

{% hint style="info" %}
Spara builds your custom calendar so it can be configured within Spara agents. Please contact your customer success manager to get started.
{% endhint %}

#### How to use Custom Calendar in Spara

Spara hosts a standalone routing page that:

* Embeds your form
* Triggers your scheduling tool after submission
* Detects when a meeting is successfully booked

#### What to provide to Spara

To configure a custom calendar, provide your Customer Success representative with:

#### Form Details

* Form platform name
* Embed script
* Portal ID / Form ID (if applicable)
* Region (if applicable)

#### Scheduling Platform Details

* Scheduler name
* Embed script
* Any routing parameters required
* Documentation for the confirmed booking event (if available)

Spara will create a custom calendar HTML page that looks like below:

```yaml
https://spara-public.s3.amazonaws.com/custom_calendar.html
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
