Marketing Automation · Integration
Curated
Add Curated to your product for your customers, and give your AI agents governed access to it.
Curated's v3 API is scoped to a single publication and the key is issued per publication, so a customer running several newsletters holds several keys and needs a connection for each. The working objects are issues, items and subscribers: an item is a curated link with a title, url and summary that is placed into a category inside a draft issue, and the available categories come from the publication's template rather than from the API. Queuing content therefore means creating items against an issue; there is no generic campaign object to address. Subscriber operations cover create, lookup by email and unsubscribe, but Curated has no segmentation layer, so the segments implied by this category do not exist and audience splitting has to happen on your side or across separate publications. Item ordering within a category is positional and set at creation rather than sorted at send. fastn holds each publication's key, keeps the scoping straight 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 Curated publication so links captured in your product queue straight into a draft issue.
Push a curated item with title, url and summary into the correct issue category automatically.
Subscribe or unsubscribe readers from your own preference centre and keep both sides in step.
Read past issues and their items to build an archive page inside your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent what is currently queued in the next issue, with every Curated call audited per tenant.
Have an agent add an approved link to a named category in the draft issue.
Let an agent check whether an email address is already subscribed before a signup is written.
Example prompt
What links are queued in the next issue of our newsletter?
Set up Curated in 4 steps
- 01Enable the Curated connector from your fastn dashboard.
- 02Have each customer authorise their own Curated 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 Curated integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Curated integration without building it. Your customers connect their own Curated 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 Curated update is not your on-call problem.
- One integration serves your product and your agents. The same governed Curated 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 Curated, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMCurated integration FAQ
How do I add a Curated integration to my product?
Enable the Curated connector in your fastn dashboard, then let each customer authenticate their own Curated account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Curated client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Curated account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Curated 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 Curated 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 what is currently queued in the next issue, with every Curated call audited per tenant.
Who maintains the Curated integration?
fastn does. When Curated 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 Curated 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 Curated?
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 Curated integration?
A common starting point: let a customer connect their own Curated publication so links captured in your product queue straight into a draft issue. 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 Curated integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Curated does not change your per-connector cost. You can start free with 3 connected accounts.
Add Curated to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.