Marketing Automation · Integration
KARTE
Add KARTE to your product for your customers, and give your AI agents governed access to it.
Embed a KARTE integration so your customers can drive their own on-site and in-app experiences from events that happen inside your product, using their own KARTE project rather than a shared key you have to meter. KARTE is organised as several API surfaces (projects, accounts and members, actions, Datahub and Insight), and this one connector covers them together, so your product sends an event once and can trigger an action, read the resulting engagement data, or query a Datahub dataset without you wiring three separate integrations. Requests run per tenant so usage is attributable to the customer that caused it. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Send product events into a customer's KARTE project so their segments reflect what a user actually did rather than a nightly export.
Trigger a KARTE action from a milestone in your product so the message fires while the behaviour is still current.
Read a customer's segments and engagement data back so your product can show who is being targeted without a second reporting tool.
Query a customer's Datahub datasets so your product can join KARTE behaviour to records it already holds.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains which segment a user falls into and why, reading the customer's own project within governed permissions.
An agent proposes an action for a drop-off point and shows the engagement data behind the suggestion before anything is sent.
An agent summarises how a recent action performed, with the read audited against the customer that authorised it.
Example prompt
Which KARTE segments has this account entered in the last week, and did any action fire for them?
Set up KARTE in 4 steps
- 01Enable the KARTE connector in your fastn dashboard.
- 02Have each customer authorise their own KARTE project so calls run under their credentials, not a shared key.
- 03Map the product events you want to send and the KARTE surfaces you need to read.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the KARTE integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a KARTE integration without building it. Your customers connect their own KARTE account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a KARTE update is not your on-call problem.
- One integration serves your product and your agents. The same governed KARTE connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
InsiderWorks well with
AmplitudeOften used alongside
Tools the same teams tend to run next to KARTE, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMKARTE integration FAQ
How do I add a KARTE integration to my product?
Enable the KARTE connector in your fastn dashboard, then let each customer authenticate their own KARTE account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no KARTE client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own KARTE account?
Yes. Every connection is scoped to the individual customer, so each authorises their own KARTE account and only ever sees their own campaigns, segments and subscribers. 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 KARTE 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 explains which segment a user falls into and why, reading the customer's own project within governed permissions.
Who maintains the KARTE integration?
fastn does. When KARTE 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.
Can I trigger a KARTE campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from KARTE?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the KARTE integration?
A common starting point: send product events into a customer's KARTE project so their segments reflect what a user actually did rather than a nightly export. 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 KARTE integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding KARTE does not change your per-connector cost. You can start free with 3 connected accounts.
Add KARTE to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.