CRM & Sales · Integration
Kizen
Add Kizen to your product for your customers, and give your AI agents governed access to it.
Embed a Kizen integration so your customers work their own CRM records inside your product and your agents get governed access to them. Kizen deployments are customised, so contact fields, custom objects and pipeline stages are mapped per tenant as configuration rather than code. fastn handles per-customer authentication, token refresh, rate limits and API upkeep, so you support the long tail of Kizen setups without an integration per customer.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync their own Kizen contacts, custom objects and activities into your product, mapped to their fields.
Create and update contacts from your product so a rep never retypes what your product already knows.
Read pipelines and stages so your product reflects how each customer actually sells.
Trigger your product when a Kizen record changes, instead of waiting for a nightly export.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a contact and its recent activity before drafting a reply.
An agent creates or updates a record within governed permissions, with each change audited.
An agent reacts to a stage change and runs the next step of a workflow.
Example prompt
Pull this contact's activity history and flag any open opportunity with no touch in 14 days.
Set up Kizen in 4 steps
- 01Open the Kizen connector from your fastn dashboard.
- 02Have each customer authenticate their own Kizen account.
- 03Map the contacts, custom objects and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Kizen integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Kizen integration without building it. Your customers connect their own Kizen 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 Kizen update is not your on-call problem.
- One integration serves your product and your agents. The same governed Kizen 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 Kizen, across other categories.
Slack
Mailchimp
Marketo
Google AdsKizen integration FAQ
How do I add a Kizen integration to my product?
Enable the Kizen connector in your fastn dashboard, then let each customer authenticate their own Kizen account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kizen client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Kizen account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Kizen 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 Kizen 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 reads a contact and its recent activity before drafting a reply.
Who maintains the Kizen integration?
fastn does. When Kizen 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 Kizen 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 Kizen schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Kizen, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Kizen do not drift apart.
What can I build with the Kizen integration?
A common starting point: sync their own Kizen contacts, custom objects and activities into your product, mapped to their fields. 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 Kizen integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kizen does not change your per-connector cost. You can start free with 3 connected accounts.
Add Kizen to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.