# RevenueHero

### Data flows

The following are the fields Spara can pre-populate and read from RevenueHero calendar

<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>Company</li><li>IP Country</li></ul></td><td><ul><li>Email</li><li>First name</li><li>Last name</li></ul></td><td>Spara will read email address and other fields after a meeting has been scheduled.</td></tr></tbody></table>

### Implementation

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

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

Spara requires a RevenueHero calendar URL , for example:

```yaml
https://meet.<yourdomain>.com/inbound/product-website-spara-chatbot
```


---

# Agent Instructions: 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:

```
GET https://docs.spara.com/integrations/calendar-integrations/revenuehero.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.