Marketing Automation · Integration
Refiner
Add Refiner to your product for your customers, and give your AI agents governed access to it.
Refiner runs in-product surveys for SaaS, so the closest fit here is Marketing Automation: there are contacts and segments, and surveys play the role campaigns do, though nobody at Refiner calls them campaigns. Contacts are keyed by your own user identifier rather than a Refiner id, which means the identify call both creates and updates, and traits you push are what segment targeting evaluates against. Surveys are shown by the client-side widget and targeted by segment, so the API is mainly used to set traits before a survey can qualify and to read responses after, not to trigger a survey directly. Responses come back keyed by the survey element identifier rather than the question text, so changing a question's wording is safe but replacing an element breaks your mapping. fastn holds each customer's Refiner key, keeps their identifier space separate, and handles reconnection when keys rotate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Refiner project so surveys target their users with traits from your product
Push plan, usage and lifecycle traits so segment targeting reflects live product state
Pull NPS and CSAT responses into your own reporting alongside account health
Trigger a follow-up workflow in your product when a detractor response comes in
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent read survey responses and summarise themes without editing any survey or segment
Have an agent update a contact's traits only for fields on an approved list
Audit per tenant which contacts an agent identified or updated and which responses it read
Example prompt
What are the common themes in this month's Refiner NPS responses from customers on the enterprise plan?
Set up Refiner in 4 steps
- 01Enable the Refiner connector from your fastn dashboard.
- 02Have each customer authorise their own Refiner 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 Refiner integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Refiner integration without building it. Your customers connect their own Refiner 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 Refiner update is not your on-call problem.
- One integration serves your product and your agents. The same governed Refiner 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 Refiner, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMRefiner integration FAQ
How do I add a Refiner integration to my product?
Enable the Refiner connector in your fastn dashboard, then let each customer authenticate their own Refiner account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Refiner client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Refiner account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Refiner 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 Refiner integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent read survey responses and summarise themes without editing any survey or segment
Who maintains the Refiner integration?
fastn does. When Refiner 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 Refiner 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 Refiner?
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 Refiner integration?
A common starting point: let a customer connect their own Refiner project so surveys target their users with traits from 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 Refiner integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Refiner does not change your per-connector cost. You can start free with 3 connected accounts.
Add Refiner to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.