> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/ashby/faq.md).

# FAQ

<details>

<summary>Where do I find my Ashby API key?</summary>

Go to **Settings → Integrations → API Keys** in your Ashby account. Click **Add API Key**, give it a descriptive name (e.g., "Coupler.io integration"), and copy the key that's generated. You need admin access to create API keys — if you don't see this option, ask your Ashby administrator.

</details>

<details>

<summary>Can I export data from multiple Ashby accounts into one destination?</summary>

Yes. Add multiple sources to the same data flow — one for each Ashby account using its own API key. Use the **Append** transformation to stack the data into a single table in your destination, with a column to identify which account each row came from.

</details>

<details>

<summary>Why does the Applications entity show different numbers than Ashby's pipeline reports?</summary>

Ashby's built-in reports apply filters by default — for example, they may only show active applications or exclude certain stages. Coupler.io exports all records matching your start date filter without additional filtering. Remove all filters in Ashby's report view to compare like-for-like.

</details>

<details>

<summary>Can I track how application statuses change over time?</summary>

The Ashby API returns the current state of each record, not a changelog. To track changes over time, use the **Append** transformation in Coupler.io so each scheduled run adds a new snapshot of your data. Comparing snapshots lets you calculate things like time-in-stage or identify when offers were accepted or declined.

</details>

<details>

<summary>What's the best way to analyze source-of-hire from Ashby data?</summary>

Export both the **Applications** and **Sources** entities, then use the **Join** transformation to connect them on the source ID field. This gives you application counts broken down by source name, which you can then filter by job, department, or hire status in your destination.

</details>

<details>

<summary>Can I use Ashby data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send your recruiting data — such as candidate feedback, archive reason patterns, or offer outcomes — directly to these tools for summarization, trend analysis, or report drafting.

</details>

<details>

<summary>Does Coupler.io support all custom fields I've created in Ashby?</summary>

Yes, as long as those custom fields have values populated on at least some records. Export the **Custom fields** entity to see all defined fields, then look for those fields as columns in your Candidates, Applications, or Jobs exports. Fields with no populated values may not appear as columns.

</details>

{% hint style="info" %}
For details on what data each entity contains, see the [Data Overview](/sources/category/other/ashby/data-overview.md) article. If you're running into connection or data problems, check [Common Issues](/sources/category/other/ashby/common-issues.md). For tips on structuring your data flow efficiently, visit [Best Practices](/sources/category/other/ashby/best-practices.md).
{% 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.coupler.io/sources/category/other/ashby/faq.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.