CRM & Sales · Integration
WhatConverts
Add WhatConverts to your product for your customers, and give your AI agents governed access to it.
WhatConverts exposes a REST API at app.whatconverts.com/api/v1 using HTTP basic auth, with the API token as the username and the secret as the password. The hierarchy matters: an account holds profiles, and reads are usually scoped by account_id and profile_id, so one token can span many client sites. Leads are the central object and carry a lead_type of phone_call, web_form, chat or transaction alongside attribution fields such as source, medium and campaign captured at the moment of conversion. CRM and Sales is the closest category fit, but note that sales values are not automatic: quotable, quote_value and sales_value are fields you write back, so leads act as the opportunity record rather than a separate object. Lead lists page with page_number and leads_per_page rather than cursors, so incremental sync needs a date filter to stay stable. fastn holds each customer's token pair, keeps profile scoping straight and absorbs endpoint changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own WhatConverts account so their calls, forms and chats appear as leads in your product without a CSV export
Write quote and sale values back from your own pipeline so WhatConverts ROI reporting reflects closed revenue
Show marketing attribution on each lead by pulling the source, medium and campaign fields into your reporting views
Run a nightly incremental sync across a customer's profiles so agency users see every client site in one place
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which lead sources produced quotable leads last month for a named profile, with the read scoped to that tenant's token
Have an agent update lead_status and sales_value on a lead after a deal closes, with every write audited per tenant
Let an agent summarise this week's missed phone call leads and flag the profiles with the largest drop
Example prompt
Which campaigns produced quotable leads for the Auckland profile last month, and what was the total sales value?
Set up WhatConverts in 4 steps
- 01Enable the WhatConverts connector from your fastn dashboard.
- 02Have each customer authorise their own WhatConverts 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 WhatConverts integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a WhatConverts integration without building it. Your customers connect their own WhatConverts 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 a WhatConverts update is not your on-call problem.
- One integration serves your product and your agents. The same governed WhatConverts 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
Often used alongside
Tools the same teams tend to run next to WhatConverts, across other categories.
WhatConverts integration FAQ
How do I add a WhatConverts integration to my product?
Enable the WhatConverts connector in your fastn dashboard, then let each customer authenticate their own WhatConverts account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no WhatConverts client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own WhatConverts account?
Yes. Every connection is scoped to the individual customer, so each authorises their own WhatConverts 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 WhatConverts integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which lead sources produced quotable leads last month for a named profile, with the read scoped to that tenant's token
Who maintains the WhatConverts integration?
fastn does. When WhatConverts 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 WhatConverts 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 WhatConverts schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from WhatConverts, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in WhatConverts do not drift apart.
What can I build with the WhatConverts integration?
A common starting point: let a customer connect their own WhatConverts account so their calls, forms and chats appear as leads in your product without a CSV export. 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 WhatConverts integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding WhatConverts does not change your per-connector cost. You can start free with 3 connected accounts.
Add WhatConverts to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.