> 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/crm/agilecrm/faq.md).

# FAQ

<details>

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

Log in to your AgileCRM account and go to **Admin Settings → API & Analytics**. Your REST API key is listed there. Only admin users can access this section, so make sure you're logged in with an admin account.

</details>

<details>

<summary>What should I enter as my AgileCRM domain?</summary>

Enter just the subdomain part of your AgileCRM URL. For example, if your AgileCRM URL is `yourcompany.agilecrm.com`, enter `yourcompany` — not the full URL.

</details>

<details>

<summary>Why do my date fields show large numbers instead of readable dates?</summary>

AgileCRM stores dates as Unix timestamps in milliseconds. You'll need to convert them in your destination tool. In Google Sheets, use a formula to divide by 1000, then divide by 86400, and add the date origin. In BigQuery, use `TIMESTAMP_MILLIS()`. Check out the Data Overview article for more context on field formats.

</details>

<details>

<summary>Does Coupler.io support filtering AgileCRM data before import?</summary>

Coupler.io pulls all available records from each AgileCRM entity. Filtering isn't applied at the source level. You can filter and transform the data after it lands in your destination — for example, using spreadsheet formulas, BigQuery views, or your BI tool's built-in filters.

</details>

<details>

<summary>Which AgileCRM plan do I need to use the API?</summary>

API access is available on AgileCRM's paid plans. Free accounts have limited or no API access. If you're having trouble connecting, check whether your plan includes API access under your AgileCRM billing or admin settings.

</details>

<details>

<summary>Can non-admin users connect AgileCRM to Coupler.io?</summary>

Technically yes, but non-admin users have restricted API access in AgileCRM and may not be able to pull all entities. For the best results and full data access, use an admin account's API key. See the Common Issues article for more on permission errors.

</details>

<details>

<summary>How often can I sync my AgileCRM data?</summary>

This depends on your AgileCRM plan's API rate limits and your Coupler.io subscription. In general, daily or hourly syncs work well for most use cases. Avoid running multiple imports simultaneously to stay within rate limits.

</details>

<details>

<summary>What happens if I regenerate my AgileCRM API key?</summary>

If you regenerate your API key in AgileCRM, your existing Coupler.io data flows will stop working immediately. You'll need to update the API key in each of your AgileCRM data flows in Coupler.io to restore the connection.

</details>

{% hint style="info" %}
For details on what fields are available for each entity, see the [Data Overview](/sources/category/crm/agilecrm/data-overview.md) article. If you're running into sync errors or missing records, check the [Common Issues](/sources/category/crm/agilecrm/common-issues.md) article. For tips on getting the most out of your integration, visit [Best Practices](/sources/category/crm/agilecrm/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/crm/agilecrm/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.