CRM & Sales · Integration
Lofty
Add Lofty to your product for your customers, and give your AI agents governed access to it.
Lofty, which agents knew as Chime until the 2023 rename, gives a real estate team a CRM, an IDX website, a dialer and an automation layer in one place, and it is that automation layer that shapes an integration. Leads are enrolled in smart plans, the drip sequences of calls, texts and emails a team designed, so the important write from your product is often not a field update but a decision about which plan somebody belongs in. Contacts carry the behaviour behind them, including the listings a lead viewed on the team's own site, which is what separates a lead worth a call this afternoon from one worth an email next month. Ownership matters too, since a lead sits with an agent inside a team and writing without respecting that puts a record where nobody is looking. fastn keeps each team's credentials per tenant and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each team connect their own Lofty account so leads captured in your product arrive with the right agent.
Create or update a contact with its source, so the team's own assignment rules decide who works it.
Move a lead between smart plans from your product when what you know about them changes.
Read a contact's listing activity and pipeline stage to show, in your product, where the relationship actually stands.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reviews a lead's activity and recommends the smart plan that fits it, leaving the enrolment to a person.
An agent reports which contacts have gone quiet since their last showing and drafts the follow-up.
An agent logs a call outcome or updates a stage under the permissions granted, with the change audited.
Example prompt
Which Lofty leads have viewed a property twice this week, and what smart plan is each one currently in?
Set up Lofty in 4 steps
- 01Enable the Lofty connector in your fastn dashboard.
- 02Have each team authorise their own Lofty account so records stay within their agent structure.
- 03Map the contact and lead fields your product writes, and confirm which smart plans it may enrol somebody in.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the Lofty integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lofty integration without building it. Your customers connect their own Lofty 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 Lofty update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lofty 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
kvCORE
PipedriveWorks well with
DocusignOften used alongside
Tools the same teams tend to run next to Lofty, across other categories.
Slack
Mailchimp
Marketo
Google AdsLofty integration FAQ
How do I add a Lofty integration to my product?
Enable the Lofty connector in your fastn dashboard, then let each customer authenticate their own Lofty account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lofty client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lofty account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lofty 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 Lofty 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 reviews a lead's activity and recommends the smart plan that fits it, leaving the enrolment to a person.
Who maintains the Lofty integration?
fastn does. When Lofty 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 Lofty 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 Lofty schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Lofty, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Lofty do not drift apart.
What can I build with the Lofty integration?
A common starting point: let each team connect their own Lofty account so leads captured in your product arrive with the right agent. 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 Lofty integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lofty does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lofty to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.