Marketing Automation · Integration
RollWorks
Add RollWorks to your product for your customers, and give your AI agents governed access to it.
RollWorks runs account based advertising, so the unit of work is a company rather than a person, and that changes what an embedded RollWorks integration is for. Your product reads target account lists, audience membership, account scores and campaign results, and it can add or remove accounts from an audience when something happens in your app. The detail that catches teams out is that audience activation is not instant: an account added now is matched and pushed to the ad exchanges over the following hours, so a write is eventually consistent and your product should not promise otherwise. Each customer authorises their own RollWorks organisation, so spend and results land on the advertiser that caused them. fastn keeps the per-tenant credentials, paces the calls and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own RollWorks organisation so their target account lists and audiences are usable inside your product.
Add or remove accounts from an audience when a signal fires in your app, so advertising follows what your product actually observed.
Read campaign delivery and account engagement per tenant to show which accounts an ad programme reached.
Surface account scores and engagement next to the company records your users already work with.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which target accounts moved in engagement this week, reading only that customer's organisation.
An agent adds a shortlist of accounts to an audience within governed permissions, with the write logged.
An agent explains how a campaign is delivering against an account list before anyone changes budget.
Example prompt
Which target accounts in this list have risen in engagement but are not in any active RollWorks audience?
Set up RollWorks in 4 steps
- 01Enable the RollWorks connector in your fastn dashboard.
- 02Have each customer authorise their own RollWorks organisation so spend and results stay with that advertiser.
- 03Map the target account, audience and campaign fields your product uses, and agree how long audience activation is expected to take.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the RollWorks integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a RollWorks integration without building it. Your customers connect their own RollWorks 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 RollWorks update is not your on-call problem.
- One integration serves your product and your agents. The same governed RollWorks 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
Demandbase
MarketoWorks well with
LinkedInOften used alongside
Tools the same teams tend to run next to RollWorks, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMRollWorks integration FAQ
How do I add a RollWorks integration to my product?
Enable the RollWorks connector in your fastn dashboard, then let each customer authenticate their own RollWorks account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no RollWorks client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own RollWorks account?
Yes. Every connection is scoped to the individual customer, so each authorises their own RollWorks 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 RollWorks 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 target accounts moved in engagement this week, reading only that customer's organisation.
Who maintains the RollWorks integration?
fastn does. When RollWorks 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 RollWorks 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 RollWorks?
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 RollWorks integration?
A common starting point: connect their own RollWorks organisation so their target account lists and audiences are usable inside 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 RollWorks integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding RollWorks does not change your per-connector cost. You can start free with 3 connected accounts.
Add RollWorks to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.