CRM & Sales · Integration
Streak
Add Streak to your product for your customers, and give your AI agents governed access to it.
Streak's API sits at api.streak.com/api/v1, with a newer v2 for the larger collections, and it authenticates with HTTP basic where the API key is the username and the password is blank. Everything is a box: a deal, a candidate and a support case are all boxes inside a pipeline, and the pipeline defines the stages and the fields those boxes can carry. Custom fields are referenced by generated field keys rather than by their display names, so a connector has to fetch the pipeline's field definitions first and remap on every read and write. Because Streak lives inside Gmail, boxes carry thread and email references, and the key belongs to one Google account, so you only see the pipelines shared with that user. fastn holds each customer's Streak key in its own tenant and keeps the pipeline and field mapping current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Streak account so your product can create a box in the pipeline they choose
Move a box to a different stage when the matching event happens in your app, using the pipeline's real stage keys
Read box fields to show deal context beside a customer record without asking users to switch to Gmail
Link the email threads Streak has attached to a box into your own activity timeline
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent update box fields or stage after a call summary, with the pipeline, box key and field change recorded per tenant
Have an agent list boxes stuck in a stage past a threshold and propose next actions
Let an agent create a box from an inbound enquiry, filling only fields it can source from verified data
Example prompt
Which boxes in our sales pipeline have not moved stage in the last three weeks?
Set up Streak in 4 steps
- 01Enable the Streak connector from your fastn dashboard.
- 02Have each customer authorise their own Streak 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 Streak integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Streak integration without building it. Your customers connect their own Streak 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 Streak update is not your on-call problem.
- One integration serves your product and your agents. The same governed Streak 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 Streak, across other categories.
Slack
Mailchimp
Marketo
Google AdsStreak integration FAQ
How do I add a Streak integration to my product?
Enable the Streak connector in your fastn dashboard, then let each customer authenticate their own Streak account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Streak client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Streak account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Streak 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 Streak 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 update box fields or stage after a call summary, with the pipeline, box key and field change recorded per tenant
Who maintains the Streak integration?
fastn does. When Streak 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 Streak 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 Streak schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Streak, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Streak do not drift apart.
What can I build with the Streak integration?
A common starting point: let a customer connect their own Streak account so your product can create a box in the pipeline they choose. 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 Streak integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Streak does not change your per-connector cost. You can start free with 3 connected accounts.
Add Streak to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.