Marketing Automation · Integration
Encharge
Add Encharge to your product for your customers, and give your AI agents governed access to it.
Encharge authenticates with an X-Encharge-Token header against api.encharge.io/v1 rather than a Bearer token, and its central object is the person, identified by email or by your own userId, with POST to /people behaving as an upsert rather than a create, so a repeated write updates instead of duplicating. Tags are handled through their own endpoint and are sent as a comma-separated string on a person rather than as an array, which is an easy shape mistake to make. Segments are computed from person fields and event history and are read-only over the API, so the way to move someone into a segment is to write the field or send the event that the segment's conditions match. Events posted to the ingest endpoint are what trigger flows, and a flow only fires for a person who already exists, so ordering the person write before the event matters. Custom fields have to exist on the account before a write to them will stick. fastn holds each customer's Encharge token and keeps the per-tenant connection current so your app never stores their key.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Encharge account so their flows and their sending domain are used.
Upsert people from your product with the traits their segments depend on.
Send product events into Encharge so their onboarding and re-engagement flows trigger on real usage.
Read segment membership back so your app can show which lifecycle stage a user sits in.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent apply or remove tags on people based on an agreed rule, with each write audited per tenant.
Have an agent report which segments a person belongs to and which event put them there.
Allow an agent to draft a broadcast for a named segment and leave sending to a human.
Example prompt
Which Encharge segments is this customer in, and which event moved them into the trial-ending one?
Set up Encharge in 4 steps
- 01Enable the Encharge connector from your fastn dashboard.
- 02Have each customer authorise their own Encharge account, so calls run under their credentials rather than a shared key.
- 03Decide which campaigns, segments and subscribers 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 Encharge integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Encharge integration without building it. Your customers connect their own Encharge 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 an Encharge update is not your on-call problem.
- One integration serves your product and your agents. The same governed Encharge 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
Mailchimp
Marketo
Google AdsOften used alongside
Tools the same teams tend to run next to Encharge, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMEncharge integration FAQ
How do I add an Encharge integration to my product?
Enable the Encharge connector in your fastn dashboard, then let each customer authenticate their own Encharge account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Encharge client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Encharge account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Encharge 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 Encharge 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 apply or remove tags on people based on an agreed rule, with each write audited per tenant.
Who maintains the Encharge integration?
fastn does. When Encharge 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 an Encharge 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 Encharge?
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 Encharge integration?
A common starting point: let a customer connect their own Encharge account so their flows and their sending domain are used. 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 Encharge integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Encharge does not change your per-connector cost. You can start free with 3 connected accounts.
Add Encharge to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.