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

# Emma

Send Perkville leads to Emma for follow-up.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

* **Lead delivery** — Push Perkville leads to Emma.
* **Connection** — Use the API keys for the intended regular or agency account; confirm the destination account before launch.

Your configured rules determine which eligible activities award points and which workflows are enabled.

{% embed url="<https://api.myemma.com/#quickstart>" %}

You will need a set of API keys to connect your Emma instance. These keys will either need to be provided to your Perkville representative via a secure method, such as [OneTimeSecret](https://onetimesecret.com/).

{% embed url="<https://onetimesecret.com/>" %}

## Regular account

1. Go to account settings
2. Find the **API Key** tab
3. Click **Generate API Key**

## Agency account

1. Go to **Menu** and select **Accounts**
2. Click the downward-pointing arrow to the right of the account you need a key for and select its settings
3. Scroll to the API key section to generate the key

## FAQ

### Is authorizing Emma enough to send leads?

Agree the lead criteria, destination account and workflow with your CSR as part of setup. Credentials alone do not define that mapping.

See the [Emma partner profile](https://partners.perkville.com/partners/emma) for additional integration information.


---

# 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.perkville.com/integrations/integration-reference/emma.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.
