Marketing Automation · Integration
Cyberimpact
Add Cyberimpact to your product for your customers, and give your AI agents governed access to it.
Cyberimpact is a Quebec-based email marketing platform built around Canadian anti-spam law, so a contact carries an explicit consent status and consent source, and creating a contact without them leaves it stored but unmailable rather than failing the call. Consent can be time-limited, which means an audience that was mailable last year can shrink without anyone editing it. Audiences are modelled as groups rather than tags, and membership is changed by posting group ids rather than by writing a field on the contact record. The API on api.cyberimpact.com uses key-based authentication and returns errors as JSON carrying a status_code field alongside the HTTP status, so error handling should read the body rather than trust the status line alone. The product and much of the content model are bilingual, with French and English versions of a mailing held side by side. fastn holds each customer's key, keeps group and consent writes consistent and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cyberimpact account so signups flow in with the consent source recorded.
Add or remove contacts from groups as their lifecycle stage changes in your product.
Write express consent captured in your own forms so mailings stay compliant with Canadian rules.
Read mailing results back onto the customer record to show what a contact has received.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent how many contacts in a group hold valid express consent, with each read audited per tenant.
Have an agent check a contact's consent status and expiry before a mailing is scheduled.
Let an agent move an approved list of contacts into a named group and report what changed.
Example prompt
How many contacts in our newsletter group still have valid express consent?
Set up Cyberimpact in 4 steps
- 01Enable the Cyberimpact connector from your fastn dashboard.
- 02Have each customer authorise their own Cyberimpact 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 Cyberimpact integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cyberimpact integration without building it. Your customers connect their own Cyberimpact 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 Cyberimpact update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cyberimpact 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 Cyberimpact, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMCyberimpact integration FAQ
How do I add a Cyberimpact integration to my product?
Enable the Cyberimpact connector in your fastn dashboard, then let each customer authenticate their own Cyberimpact account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cyberimpact client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cyberimpact account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cyberimpact 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 Cyberimpact 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 many contacts in a group hold valid express consent, with each read audited per tenant.
Who maintains the Cyberimpact integration?
fastn does. When Cyberimpact 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 Cyberimpact 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 Cyberimpact?
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 Cyberimpact integration?
A common starting point: let a customer connect their own Cyberimpact account so signups flow in with the consent source recorded. 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 Cyberimpact integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cyberimpact does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cyberimpact to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.