CRM & Sales · Integration
PartnerStack
Add PartnerStack to your product for your customers, and give your AI agents governed access to it.
Embed a PartnerStack integration so a customer's partner and affiliate programme runs alongside their direct pipeline inside your product instead of in a separate tab. PartnerStack holds partners and the groups they sit in, referral links, leads and deals a partner brought in, the customers those turned into, and the rewards owed as a result. Each customer authorises their own PartnerStack account, so writes are attributed to their programme and one company's partner data never mixes with another's. Programmes are configured differently everywhere, so groups, deal fields and reward structures are mapped per tenant as configuration rather than code. fastn owns the auth, token refresh, rate limits and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own PartnerStack account so partners, leads and deals are reachable inside your product with no per-customer code.
Push a lead or deal a partner referred into your product so it enters the same pipeline as direct business.
Report a converted customer back to PartnerStack so the right partner is credited without a spreadsheet.
Read partner, group and reward records per tenant so your product can show what a programme is actually producing.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which partners drove pipeline this quarter for one customer, with each read audited.
An agent updates a deal or lead a partner submitted within scoped permissions, with the write attributed.
An agent answers what a partner is owed and why, reading only that tenant's reward records.
Example prompt
Which partners referred deals that closed last month, and what rewards are outstanding on them?
Set up PartnerStack in 4 steps
- 01Enable the PartnerStack connector in your fastn dashboard.
- 02Have each customer authorise their own PartnerStack account so calls run under their credentials.
- 03Map the partner, group, lead, deal and reward fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the PartnerStack integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PartnerStack integration without building it. Your customers connect their own PartnerStack 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 PartnerStack update is not your on-call problem.
- One integration serves your product and your agents. The same governed PartnerStack 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
Crossbeam
Salesforce
HubSpotOften used alongside
Tools the same teams tend to run next to PartnerStack, across other categories.
Slack
Mailchimp
Marketo
Google AdsPartnerStack integration FAQ
How do I add a PartnerStack integration to my product?
Enable the PartnerStack connector in your fastn dashboard, then let each customer authenticate their own PartnerStack account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PartnerStack client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PartnerStack account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PartnerStack 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 PartnerStack 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 reports which partners drove pipeline this quarter for one customer, with each read audited.
Who maintains the PartnerStack integration?
fastn does. When PartnerStack 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 PartnerStack 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 PartnerStack schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from PartnerStack, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in PartnerStack do not drift apart.
What can I build with the PartnerStack integration?
A common starting point: let each customer connect their own PartnerStack account so partners, leads and deals are reachable inside your product with no per-customer code. 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 PartnerStack integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PartnerStack does not change your per-connector cost. You can start free with 3 connected accounts.
Add PartnerStack to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.