Marketing Automation · Integration
Onepage
Add Onepage to your product for your customers, and give your AI agents governed access to it.
Onepage builds fast landing pages, funnels and link pages without anybody writing markup, and the part your product cares about is not the page but what the page collects. A form submission is the event worth wiring, and Onepage keeps the resulting contacts itself, so a lead exists in two places from the start and the question is which system does something about it. An embedded integration takes each submission as it happens, carries the fields that page asked for rather than a fixed set, and reads contacts back when your product needs the current state. Fields differ per page because each customer designs their own, which makes mapping configuration rather than a release. Pages themselves are edited in Onepage, so this is a lead and contact integration rather than a content one. fastn keeps each account's credentials per tenant and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Onepage account so leads from their pages land in your product directly.
Map the fields a page asks for at connect time, since every customer designs their own form.
Act on a submission as it happens, so a follow-up goes out while somebody is still on the page they came from.
Read contact records back to show, inside your product, everything a page has collected about a person.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which pages produced leads this week and how they compare with last.
An agent qualifies a new submission against the customer's criteria and writes the outcome to your product.
An agent finds contacts missing the fields a follow-up needs and says what is absent.
Example prompt
Which Onepage landing pages produced leads this week, and which of those leads has nobody followed up?
Set up Onepage in 4 steps
- 01Enable the Onepage connector in your fastn dashboard.
- 02Have each customer authorise their own Onepage account so their pages and contacts stay theirs.
- 03Map each page's form fields to what your product stores, then enable the submission events you react to.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the Onepage integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Onepage integration without building it. Your customers connect their own Onepage 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 Onepage update is not your on-call problem.
- One integration serves your product and your agents. The same governed Onepage 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
Unbounce
PerspectiveWorks well with
HubSpotOften used alongside
Tools the same teams tend to run next to Onepage, across other categories.
Salesforce
Pipedrive
Zoho CRM
ApolloOnepage integration FAQ
How do I add a Onepage integration to my product?
Enable the Onepage connector in your fastn dashboard, then let each customer authenticate their own Onepage account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Onepage client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Onepage account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Onepage 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 Onepage 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 pages produced leads this week and how they compare with last.
Who maintains the Onepage integration?
fastn does. When Onepage 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 Onepage 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 Onepage?
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 Onepage integration?
A common starting point: let each customer connect their own Onepage account so leads from their pages land in your product directly. 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 Onepage integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Onepage does not change your per-connector cost. You can start free with 3 connected accounts.
Add Onepage to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.