CRM & Sales · Integration
folk
Add folk to your product for your customers, and give your AI agents governed access to it.
folk's API at api.folk.app/v1 uses a bearer token and its own model built around people, companies and groups, where a group is closer to a workspace-scoped pipeline or list than to a tag. The detail that catches most implementers is that custom fields belong to a group rather than to the contact record, so the same person carries different field sets depending on which groups they are in, and writing a field means addressing it through the group it was defined on. People and companies are linked records, so updating a company's attributes does not touch the people attached to it and vice versa. Emails, calendar events and LinkedIn history that appear in the folk UI come from each user's connected mailbox and browser extension rather than from the API, so an integration reading contacts will not see the interaction timeline that a user sees. Errors return a structured code with a documentation URL, which makes failures easy to route. fastn holds each customer's own token, keeps it refreshed, and keeps contact writes attributed to the right tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own folk workspace so contacts your product creates land in their groups
Write custom field values through the group they were defined on when a deal stage changes in your product
Sync companies and their linked people into your own account model without flattening the relationship
Create a person in a named group when a new lead signs up, and keep their status field in step
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent add a person to a group and set the group's custom fields, with every write audited per tenant against that tenant's own token
Have an agent look up a company and its linked people before drafting an account summary
Allow an agent to report which contacts in a group are missing required custom field values
Example prompt
Which people in our prospects group in folk are missing a status value, and what companies are they at?
Set up folk in 4 steps
- 01Enable the folk connector from your fastn dashboard.
- 02Have each customer authorise their own folk 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 folk integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a folk integration without building it. Your customers connect their own folk 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 folk update is not your on-call problem.
- One integration serves your product and your agents. The same governed folk 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 folk, across other categories.
Slack
Mailchimp
Marketo
Google Adsfolk integration FAQ
How do I add a folk integration to my product?
Enable the folk connector in your fastn dashboard, then let each customer authenticate their own folk account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no folk client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own folk account?
Yes. Every connection is scoped to the individual customer, so each authorises their own folk 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 folk integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent add a person to a group and set the group's custom fields, with every write audited per tenant against that tenant's own token
Who maintains the folk integration?
fastn does. When folk 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 folk 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 folk schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from folk, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in folk do not drift apart.
What can I build with the folk integration?
A common starting point: let a customer connect their own folk workspace so contacts your product creates land in their groups. 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 folk integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding folk does not change your per-connector cost. You can start free with 3 connected accounts.
Add folk to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.