Marketing Automation · Integration
ActiveTrail
Add ActiveTrail to your product for your customers, and give your AI agents governed access to it.
ActiveTrail's REST API is served from webapi.mymarketing.co.il/api, which catches people out because it does not sit on activetrail.com at all. Tokens are created in the account settings, can be pinned to specific IP addresses and given an expiry date, so an integration key can stop working on a date nobody wrote down. The main resources are contacts, groups, campaigns and SMS campaigns, with groups acting as the segment container that contacts are added to and removed from. Operational or transactional messages have their own endpoint rather than going through the campaign endpoints, so triggered one to one mail should not be modelled as a campaign. The platform is strongest in the Israeli market, so expect Hebrew content and right to left templates in customer data and plan encoding accordingly. fastn holds each customer's token, notices expiry before a send fails and keeps the integration current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own ActiveTrail account so their contacts and groups sync from your product
Add and remove contacts from a group as their status changes in your app, so segments stay accurate without exports
Trigger operational messages such as receipts through the dedicated endpoint rather than creating a campaign for each one
Read campaign results back into your reporting so opens and clicks sit next to your own activity data
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent how the last SMS campaign performed against the previous one for a named group
Have an agent add a contact to a group after a qualifying event, with the write audited per tenant
Let an agent report which groups a given contact belongs to before anyone sends to them again
Example prompt
Which group had the best click rate on last week's newsletter, and how many contacts are in it now?
Set up ActiveTrail in 4 steps
- 01Enable the ActiveTrail connector from your fastn dashboard.
- 02Have each customer authorise their own ActiveTrail 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 ActiveTrail integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an ActiveTrail integration without building it. Your customers connect their own ActiveTrail 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 ActiveTrail update is not your on-call problem.
- One integration serves your product and your agents. The same governed ActiveTrail 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 ActiveTrail, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMActiveTrail integration FAQ
How do I add an ActiveTrail integration to my product?
Enable the ActiveTrail connector in your fastn dashboard, then let each customer authenticate their own ActiveTrail account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ActiveTrail client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ActiveTrail account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ActiveTrail 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 ActiveTrail integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent how the last SMS campaign performed against the previous one for a named group
Who maintains the ActiveTrail integration?
fastn does. When ActiveTrail 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 ActiveTrail 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 ActiveTrail?
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 ActiveTrail integration?
A common starting point: let a customer connect their own ActiveTrail account so their contacts and groups sync from your product. 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 ActiveTrail integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ActiveTrail does not change your per-connector cost. You can start free with 3 connected accounts.
Add ActiveTrail to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.