CRM & Sales · Integration
Agile CRM
Add Agile CRM to your product for your customers, and give your AI agents governed access to it.
Agile CRM is per tenant by hostname: every call goes to https://{domain}.agilecrm.com/dev/api, so the customer's account domain is part of the credential set alongside the login email and API key, which are sent as HTTP Basic. The contact model is the thing that surprises implementers, because fields are not flat: a contact carries a properties array of objects with name, value and subtype, so an email or phone is a typed entry inside that array and updating one means merging the array rather than setting a key. Companies are stored as contacts with type COMPANY rather than as a separate resource, and deals hang off contacts. Tags are plain strings applied to a contact and have their own add and remove calls, which is usually cleaner than rewriting properties. fastn holds each customer's domain, email and key together as one connection and keeps it working as credentials change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Agile CRM account, including their account domain, so records sync to their instance
Create or update a contact in the customer's CRM when someone signs up in your product
Write product activity back as notes or tasks against the matching contact
Apply and remove tags so your product's lifecycle stages stay in step with the customer's CRM segments
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent look up a contact by email and summarise the open deals and tasks attached to it
Have an agent create a follow up task on a contact after a support conversation ends
Audit per tenant which contacts and deals an agent read or changed, since the connection is scoped to one account domain
Example prompt
What deals are open on this contact and when is the next task due?
Set up Agile CRM in 4 steps
- 01Enable the Agile CRM connector from your fastn dashboard.
- 02Have each customer authorise their own Agile CRM account, so calls run under their credentials rather than a shared key.
- 03Decide which accounts, contacts and opportunities your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Agile CRM integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Agile CRM integration without building it. Your customers connect their own Agile CRM account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Agile CRM update is not your on-call problem.
- One integration serves your product and your agents. The same governed Agile CRM connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
Salesforce
HubSpot
PipedriveOften used alongside
Tools the same teams tend to run next to Agile CRM, across other categories.
Slack
Mailchimp
Marketo
Google AdsAgile CRM integration FAQ
How do I add an Agile CRM integration to my product?
Enable the Agile CRM connector in your fastn dashboard, then let each customer authenticate their own Agile CRM account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Agile CRM client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Agile CRM account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Agile CRM account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Agile CRM integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent look up a contact by email and summarise the open deals and tasks attached to it
Who maintains the Agile CRM integration?
fastn does. When Agile CRM changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Agile CRM integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual Agile CRM schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Agile CRM, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Agile CRM do not drift apart.
What can I build with the Agile CRM integration?
A common starting point: let a customer connect their own Agile CRM account, including their account domain, so records sync to their instance. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Agile CRM integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Agile CRM does not change your per-connector cost. You can start free with 3 connected accounts.
Add Agile CRM to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.