> For the complete documentation index, see [llms.txt](https://docs.growsurf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growsurf.com/integrations/calendly.md).
# Calendly
Add referral tracking to your Calendly form to automatically recognize new leads that come through referrals.
{% hint style="info" %}
**Requirements to make Calendly work with GrowSurf**:
* A *Calendly Standard* plan or higher is required.
* Your form must be embedded on your own webpage (you cannot use the stand-alone `https://calendly.com/xxxx/xxxx` webpage).
{% endhint %}
## Prep Your Form
If you have an embedded Calendly form on your website that you want to add referral tracking to, follow these instructions:
**Step 1:** Open the GrowSurf Program Editor and navigate to the *Installation* tab.
**Step 2:** Continue through the installation steps until you reach the step that asks how GrowSurf will know a referred friend signed up (see image below).
**Step 3:** Click the Calendly icon and follow the instructions GrowSurf shows (see image below).
**Step 4:** Then finish the remaining installation steps.
## Additional Tips
* While following the instructions GrowSurf shows, you may skip any steps that you have already completed in a previous setup in Calendly.
* If you run into issues or have any questions, please reach out to [GrowSurf support](https://support.growsurf.com/) for assistance.
---
# 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.growsurf.com/integrations/calendly.md?ask=&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.
