Data & Storage · Integration
People.ai
Add People.ai to your product for your customers, and give your AI agents governed access to it.
Embed a People.ai integration so your product can use the go-to-market activity a customer already captures rather than reconstructing it from mailboxes. People.ai captures seller activity such as emails and meetings and matches it to the accounts, contacts and opportunities in the customer's CRM, which makes it an engagement data surface rather than the system of record for those records themselves. The company now operates as Backstory. Volumes are large and every customer's account and field model differs, so mapping is configuration per tenant and reads are paginated and rate limited for you. fastn handles per-customer authorisation and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own People.ai account so your product reads captured activity and engagement data per tenant.
Show engagement and relationship coverage on an account inside your product instead of sending users to another tool.
Use activity data to power your own scoring, reporting or alerting features without building capture yourself.
Handle each customer's own account and field model as mapping rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads the recent activity on an account before it drafts a follow-up.
An agent reports which contacts on a deal have gone quiet, with every read scoped and audited.
An agent pulls engagement detail per tenant and hands it to the next step of a workflow.
Example prompt
Summarise engagement on my top five open opportunities and flag the ones with no contact in three weeks.
Set up People.ai in 4 steps
- 01Open the People.ai connector from your fastn dashboard.
- 02Have each customer authorise their own People.ai account.
- 03Map the accounts, contacts and activity fields your product reads, then enable the queries you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the People.ai integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a People.ai integration without building it. Your customers connect their own People.ai account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a People.ai update is not your on-call problem.
- One integration serves your product and your agents. The same governed People.ai connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
Often used alongside
Tools the same teams tend to run next to People.ai, across other categories.
People.ai integration FAQ
How do I add a People.ai integration to my product?
Enable the People.ai connector in your fastn dashboard, then let each customer authenticate their own People.ai account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no People.ai client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own People.ai account?
Yes. Every connection is scoped to the individual customer, so each authorises their own People.ai account and only ever sees their own records, datasets and fields. 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 People.ai 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 the recent activity on an account before it drafts a follow-up.
Who maintains the People.ai integration?
fastn does. When People.ai 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 People.ai integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large People.ai reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the People.ai integration?
A common starting point: connect their own People.ai account so your product reads captured activity and engagement data per tenant. 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 People.ai integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding People.ai does not change your per-connector cost. You can start free with 3 connected accounts.
Add People.ai to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.