Centiment
FormsCentiment pairs a survey builder with a profiled respondent panel spanning 100+ countries. Agents create and launch surveys, target audiences, pull responses and completion stats, and react when a new response lands.
What This Integration Enables
Centiment is a research platform where the respondents are the product. The survey builder is the front door, but what you are actually buying is reach into a profiled panel across a large number of targeting criteria and countries. That commercial shape has a direct consequence for automation: the survey is authored in Centiment's builder, and the API exists so the resulting data can get out and reach the systems that use it. Reads on surveys and workspaces are the whole surface, and webhooks are the only write.
So FlowRunner agents here are a delivery and reconciliation layer. They resolve a survey by name when the name comes from a project record rather than a picker, walk every page of a survey's responses, read a report's summary and its filtered response set, and manage the webhooks that decide where new responses go. These connectors are built and verified against the vendor's official API, including two facts the specification does not carry: Centiment runs two different response status vocabularies that disagree on how a disqualified respondent is spelled, and every delivery is signed with a key issued at webhook creation. FlowRunner maps the vocabularies for you and verifies the signature before a payload reaches a flow.
Because the panel is metered, every response that arrives is one somebody paid for. Changing where those responses land is not a configuration task, and it is the point where FlowRunner's human-in-the-loop discipline applies.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Fielding you can watch in real time
A panel study goes live. On New Response fires on each completion, the payload arrives with its signature already verified, and the agent writes the response into the analysis table in BigQuery. Every few responses it calls Get Report Summary and compares the running segment counts against the client's quota. When a segment reaches target, it posts to the research channel in Slack with the counts and the remaining segments called out. The team sees the shape of the study while it is still fielding, instead of learning it from a crosstab a week later.
-
A reconciliation pass that closes the study cleanly
When fielding ends, the agent resolves the study with Find Survey By Name and calls Get All Responses to walk every page of the survey's data, then Get Report Responses for the same study filtered to the statuses the client is paying for. It compares the two sets against what actually reached the warehouse and reports the difference. Anything that arrived while a delivery was failing shows up as a named gap rather than as a quiet undercount, and the analysis starts from a set somebody verified.
-
Cross-study reporting without a manual export
On a schedule, the agent walks List Organizations and List Workspaces to find every active study, calls List Surveys per workspace, and calls Get Report Summary for each study that has a shared report. The results append to a portfolio sheet in Google Sheets with completion rates, disqualification rates, and days in field per study. The research director opens one view instead of five, and nothing in it came from a screenshot.
Human-in-Loop Highlight
Delete Webhook is where a Centiment workflow can quietly cost real money. A webhook's signing key is issued when the webhook is created, and Centiment publishes no reset route on its public API, so rotating a key means deleting and recreating, which issues a new one that every receiving endpoint must be updated to expect. During that gap, responses keep arriving from a panel that is being billed, and they are delivered nowhere. No action in this connector can tell you afterwards which responses already fired and which did not, so recovering means a full reconciliation pass over List Responses.
So a webhook change on a fielding study stops for a person. The agent calls List Webhooks first and posts what it found: "Survey Q3 Category Usage is live and has taken 214 completes today. Two webhooks are enabled on it: the warehouse relay and the incentive payout endpoint. You asked me to point the relay at the new URL. Update Webhook changes the target in place and keeps the signing key, so the payout endpoint is untouched and nothing is missed. Deleting and recreating would issue a new key and drop anything arriving in between. Update in place, or replace it?" The research operations owner answers. The agent runs the update, then reconciles the day's responses against what the warehouse received so the answer is provable rather than assumed. The reading, the counting, and the reconciliation were automatic. The call that risked paid data belonged to a person.
Agent Capabilities
20 actionsAccount and Structure
5- Get Profile Returns the account the API key belongs to. Used as the connection check at the start of a workflow, and to resolve which organizations a key can reach.
- List Organizations Lists the organizations the key has access to. The top of the hierarchy every other lookup descends from.
- Get Organization Reads one organization by its identifier. Used to confirm a study belongs where a project record says it does.
- List Workspaces Lists the workspaces under an organization. Workspaces are how studies are grouped, so this is the step before enumerating surveys across a portfolio.
- Get Workspace Reads one workspace by its identifier, used to resolve its name and parent before reporting against it.
Surveys
3- List Surveys Lists the surveys in a workspace. The starting point for any workflow that reports across more than one study.
- Get Survey Reads one survey by its identifier, returning the record Centiment holds for it.
- Find Survey By Name Resolves a survey by its title rather than its identifier, by paging the listing and matching in FlowRunner. Used when the study name arrives from a project tracker, a message, or a person.
Responses
2- List Responses Returns one page of a survey's responses. Paged, with the page size limits the vendor publishes for its own read wrapper rather than in the API specification.
- Get All Responses Walks every page of a survey's responses and returns them as one set. The export step for analysis, reconciliation, and warehouse loads.
Reports
4- List Reports Lists the reports configured on a survey. A report is addressed by a short share key rather than an identifier, the same string that appears in a shared reporting link.
- Get Report Reads one report's configuration by its share key, so a workflow knows what the report is filtered to before it reads numbers from it.
- Get Report Summary Returns a report's summary figures. The cheap way to check completes and disqualification rates by segment while a study is still fielding.
- Get Report Responses Returns the responses behind a report, filtered to the statuses the report defines. Used when the analysis should see exactly what the shared report shows.
Response Delivery
5- List Webhooks Lists the webhooks configured on a survey with their targets and settings. The audit step that answers where a study's responses are actually going.
- Get Webhook Reads one webhook by its identifier, returning its target, its status filter, and its state.
- Create Webhook Adds a webhook to a survey so Centiment posts each new response to a URL of your choice, and returns the signing key deliveries will be verified against. To start a FlowRunner flow from new responses, use the trigger instead, which manages its own webhook and its own verification.
- Update Webhook Updates an existing webhook. Centiment's route is a full replacement, so this action reads the current record and merges your changes over it, which means a field left empty keeps its value rather than being blanked.
- Delete Webhook Permanently removes a webhook and the signing key issued with it. There is no reset route on the public API, so rotating a key means deleting and recreating, and every receiving endpoint must be updated to expect the new one.
Direct Access
1- Make API Call Sends an authorized request to any Centiment route with the connection's key. The escape hatch for anything the vendor adds after this connector was built.
Triggers
1 triggersEvent Triggers
1- On New Response Fires when a new response is recorded on a Centiment survey, delivering it as it arrives rather than polling for it. Choose which completion statuses should fire it, and FlowRunner registers and removes the underlying Centiment webhook for you. Every delivery is checked against its signature before it reaches the flow.
Frequently Asked Questions
What can FlowRunner do with Centiment?
FlowRunner agents can run Get Profile, List Organizations, and Get Organization in Centiment, plus 17 more actions.
Does connecting Centiment to FlowRunner require OAuth?
No. Centiment connects to FlowRunner with an API key, no OAuth flow required.
Can Centiment trigger a FlowRunner workflow automatically?
Yes. Centiment supports 1 trigger that can start a FlowRunner workflow automatically.
Other Forms integrations
Start building with Centiment
Free plan, no card required. Connect in minutes.