Marketing Automation · Integration
Circa
Add Circa to your product for your customers, and give your AI agents governed access to it.
Embed a Circa integration so your customers can manage their own events and registrations from inside your product and get engagement data back as events your app can act on. A product event can register a contact or update their status, so event follow-up follows what someone actually did rather than a manual export. Registration data is delivered per tenant, and fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own events and registration lists into your product, mapped to their records.
Register or update a contact from a product event so signups land without manual entry.
Read attendance and engagement data so event reporting sits alongside the rest of your funnel.
Trigger your product when someone registers, attends, or cancels.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists who registered but did not attend before a follow-up campaign is built.
An agent registers or updates a contact within governed permissions, with the action audited.
An agent reacts to a registration event and adds the contact to the right nurture path.
Example prompt
List registrations for next month's events and flag any contact who is not in the CRM yet.
Set up Circa in 4 steps
- 01Open the Circa connector from your fastn dashboard.
- 02Have each customer authenticate their own Circa account with least-privilege credentials.
- 03Map the event and registration fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Circa integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Circa integration without building it. Your customers connect their own Circa 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 Circa update is not your on-call problem.
- One integration serves your product and your agents. The same governed Circa 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
Campaign MonitorWorks well with
HubSpot
SalesforceOften used alongside
Tools the same teams tend to run next to Circa, across other categories.
Pipedrive
Zoho CRM
Apollo
ClassyCirca integration FAQ
How do I add a Circa integration to my product?
Enable the Circa connector in your fastn dashboard, then let each customer authenticate their own Circa account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Circa client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Circa account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Circa 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 Circa 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 lists who registered but did not attend before a follow-up campaign is built.
Who maintains the Circa integration?
fastn does. When Circa 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 Circa 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 Circa?
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 Circa integration?
A common starting point: read their own events and registration lists into your product, mapped to their records. 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 Circa integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Circa does not change your per-connector cost. You can start free with 3 connected accounts.
Add Circa to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.