Close

Enable the Close connector in your fastn dashboard, then let each customer authenticate their own Close account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Close client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Close 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.

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 reads a lead's recent activity before drafting a follow-up.

fastn does. When Close 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.

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 Close schema does not require a deploy on your side.

Yes. You can read from Close, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Close do not drift apart.

A common starting point: sync leads, contacts, and opportunities into your product both ways. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Close does not change your per-connector cost. You can start free with 3 connected accounts.