CRM & Sales · Integration
kvCORE
Add kvCORE to your product for your customers, and give your AI agents governed access to it.
kvCORE is the platform a brokerage runs rather than a CRM an individual agent buys, and that distinction decides how an integration behaves. Records belong somewhere in a hierarchy of brokerage, team and agent, routing rules decide who owns a new lead, and writing a contact without honouring that structure produces a record the right person never sees. The contact itself is richer than a name and a number, because kvCORE watches what a lead does on the brokerage's own IDX website and scores them on it, so property views and saved searches are part of the record and are usually the reason a lead is worth calling today. Inside Real Estate has brought the platform under its BoldTrail branding, and long-standing accounts are still very much kvCORE accounts. fastn keeps each brokerage's credentials per tenant and maintains the connector as the platform is renamed and revised.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each brokerage connect their own kvCORE account so leads created in your product land with the agent who should work them.
Write a lead with its source so the account's own routing rules decide ownership instead of you hard-coding it.
Read the property activity behind a contact, so your product can show why this lead is worth a call now.
Keep contact records aligned in both directions, since an agent updating a contact in kvCORE should not be overwritten by your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises a lead's recent property views and drafts the outreach that fits what they looked at.
An agent reports which new leads have gone unworked past the brokerage's own response window.
An agent updates a contact or logs an activity under the permissions granted, with the change attributed.
Example prompt
Which leads viewed a listing over $1m in the last week, and which of them has their agent not yet contacted?
Set up kvCORE in 4 steps
- 01Enable the kvCORE connector in your fastn dashboard.
- 02Have each brokerage authorise their own account so records stay inside their hierarchy.
- 03Map the contact and lead fields your product uses, and confirm how ownership and routing are decided.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the kvCORE integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a kvCORE integration without building it. Your customers connect their own kvCORE 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 kvCORE update is not your on-call problem.
- One integration serves your product and your agents. The same governed kvCORE 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
Lofty
HubSpotWorks well with
DocusignOften used alongside
Tools the same teams tend to run next to kvCORE, across other categories.
Slack
Mailchimp
Marketo
Google AdskvCORE integration FAQ
How do I add a kvCORE integration to my product?
Enable the kvCORE connector in your fastn dashboard, then let each customer authenticate their own kvCORE account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no kvCORE client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own kvCORE account?
Yes. Every connection is scoped to the individual customer, so each authorises their own kvCORE 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 kvCORE integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises a lead's recent property views and drafts the outreach that fits what they looked at.
Who maintains the kvCORE integration?
fastn does. When kvCORE 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 kvCORE 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 kvCORE schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from kvCORE, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in kvCORE do not drift apart.
What can I build with the kvCORE integration?
A common starting point: let each brokerage connect their own kvCORE account so leads created in your product land with the agent who should work them. 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 kvCORE integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding kvCORE does not change your per-connector cost. You can start free with 3 connected accounts.
Add kvCORE to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.