> 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/common-issues.md).
# Common Issues
## Connection issues
My API key isn't working
Double-check that you're using the **REST API key** from AgileCRM, not a different credential. You can find it under **Admin Settings → API & Analytics** in your AgileCRM account. Make sure there are no extra spaces when you paste the key into Coupler.io.
I get an authentication error even though my credentials look correct
Make sure you're entering your credentials exactly as follows:
* **Domain** — just the subdomain (e.g., `yourcompany`), not the full URL
* **Email** — the email address you use to log in to AgileCRM
* **API key** — copied directly from AgileCRM's Admin Settings page
If you recently reset your API key in AgileCRM, you'll need to update it in Coupler.io as well.
My data flow times out during the connection test
This can happen if your AgileCRM account has a very large dataset. Try running the data flow on a smaller entity first (like Milestones or Ticket Filters) to confirm the connection works. If the timeout persists on large entities, contact Coupler.io support.
## Missing data
Some contacts or deals are missing from my export
AgileCRM's API returns data in paginated batches. If your account has a very large number of records, occasional gaps can occur. Try re-running the data flow. If data is consistently missing, check whether the missing records are accessible to your user under their permissions in AgileCRM.
Custom fields aren't showing up in my data
Custom fields should appear in the exported data, but their names depend on how they're defined in your AgileCRM account. Check your AgileCRM custom field configuration under **Admin Settings** and look for matching field names in the exported columns.
The Tickets entity returns no data
Make sure your AgileCRM plan includes the helpdesk/ticketing feature — not all plans do. Also, confirm that tickets exist in your account and that your API key belongs to a user with access to the helpdesk module.
## Permission errors
I see a 403 Forbidden error
This usually means the AgileCRM user account associated with your API key doesn't have permission to access the entity you're trying to import. Check that your user has admin-level or appropriate role permissions in AgileCRM. Only admin users can access all entities via the API.
{% hint style="warning" %}
Non-admin users in AgileCRM may have restricted API access. Use an admin account's API key for full data access.
{% endhint %}
## Data discrepancies
Timestamps look wrong or unreadable
AgileCRM returns timestamps as Unix epoch values (milliseconds). You'll need to convert these in your destination tool. In Google Sheets, you can use a formula like `=(A1/1000/86400)+DATE(1970,1,1)` and format the cell as a date.
Deal counts in Coupler.io don't match what I see in AgileCRM
AgileCRM's UI may apply default filters (such as showing only open deals) that aren't applied in the API. Coupler.io returns all records unless filters are applied. Check whether deleted or archived deals are being included in your export.
## Rate limits
My sync fails with a rate limit error
AgileCRM enforces API rate limits that vary by plan. If you're hitting rate limits, try scheduling your syncs less frequently or during off-peak hours. Avoid running multiple AgileCRM data flows at the same time, as each one counts toward your API quota.
---
# 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/common-issues.md?ask=&goal=
```
`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.