Data & Storage · Integration
UserVoice
Add UserVoice to your product for your customers, and give your AI agents governed access to it.
UserVoice collects product feedback and keeps score. A suggestion sits in a forum, supporters vote for it, and the status attached to it is what tells everybody whether anything is going to happen about it. An embedded UserVoice integration reads those suggestions with their vote and supporter counts, reads the forums and statuses a team defined, and creates feedback on behalf of the person who gave it, so a comment made inside your product joins the same tally as one left on the portal. Two things shape the build: the feedback belongs to identified end users rather than to your own account, and every team names its own forums and statuses, so both are mapped per tenant. fastn stores the credentials, pages through the results and keeps the connector honest as the API shifts.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own UserVoice account so feedback captured in your product lands in the forum their team already watches.
Create a suggestion or add a supporter on behalf of the end user who raised it, so the vote count reflects real demand.
Read suggestions with their status so your product can tell somebody that what they asked for is already planned.
Map each team's own forums, statuses and custom fields as configuration rather than assuming everybody kept the defaults.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which suggestions gained the most supporters this quarter inside one customer's account.
An agent files feedback from a conversation into the right forum within scoped permissions, with the write attributed.
An agent groups similar suggestions and quotes the ones it grouped instead of summarising from memory.
Example prompt
Which UserVoice suggestions have the most supporters and still have no status set?
Set up UserVoice in 4 steps
- 01Enable the UserVoice connector in your fastn dashboard.
- 02Have each customer authorise their own UserVoice account so calls run under their credentials.
- 03Map the forums, suggestion fields, statuses and end user identifiers your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the UserVoice integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a UserVoice integration without building it. Your customers connect their own UserVoice account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a UserVoice update is not your on-call problem.
- One integration serves your product and your agents. The same governed UserVoice connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
SurveyMonkey
PendoWorks well with
IntercomOften used alongside
Tools the same teams tend to run next to UserVoice, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceUserVoice integration FAQ
How do I add a UserVoice integration to my product?
Enable the UserVoice connector in your fastn dashboard, then let each customer authenticate their own UserVoice account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no UserVoice client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own UserVoice account?
Yes. Every connection is scoped to the individual customer, so each authorises their own UserVoice account and only ever sees their own records, datasets and fields. 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 UserVoice 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 suggestions gained the most supporters this quarter inside one customer's account.
Who maintains the UserVoice integration?
fastn does. When UserVoice 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.
Does the UserVoice integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large UserVoice reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the UserVoice integration?
A common starting point: let each customer connect their own UserVoice account so feedback captured in your product lands in the forum their team already watches. 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 UserVoice integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding UserVoice does not change your per-connector cost. You can start free with 3 connected accounts.
Add UserVoice to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.