--- title: "ResponseSuite Integration" description: "ResponseSuite is a survey marketing platform whose API exists to read surveys and submissions back out. Agents list and look up surveys, read completed submissions from a point in time, page a whole submission history into one array, and react when a new submission or survey appears." url: https://flowrunner.ai/integrations/responsesuite date_modified: 2026-09-04T19:20:34-07:00 --- # ResponseSuite [Forms](https://flowrunner.ai/integrations/category/documents-forms) ResponseSuite is a survey marketing platform whose API exists to read surveys and submissions back out. Agents list and look up surveys, read completed submissions from a point in time, page a whole submission history into one array, and react when a new submission or survey appears. 2 triggers · 9 actions · API key · available [ResponseSuite website](https://www.responsesuite.com/) · [Platform Documentation](https://www.responsesuite.com/) · Capability data verified 2026-08-26 1. On New Submission fires when a respondent finishes a survey 2. The agent reads the answers and whatever identifying fields the submission carries 3. The agent resolves the person in the platform that actually owns the contact record 4. The agent confirms the answer driving the segment is one it recognizes, not free text it is guessing at 5. The contact is synced and tagged with what the respondent actually said 6. Low satisfaction answers post to the account team with the full response attached 7. The owner decides whether that answer justifies moving the contact onto a different campaign track ## What This Integration Enables ResponseSuite is built for teams whose surveys exist to feed a marketing motion, not to produce a report. That shows up in the API, which the vendor deliberately kept one way: three read routes, no writes on any verb, and no webhook management at all. Surveys are designed and published inside the ResponseSuite editor, and the API exists so the answers can leave it. FlowRunner agents list and resolve surveys, read completed submissions by lookback window or from a point in time, page an entire submission history into a single array, and poll for new submissions and new surveys. That one way design decides how these workflows should be built. Nothing FlowRunner does inside ResponseSuite is reversible, because there is nothing to reverse: every consequence lands in the CRM, the email platform, or the channel that receives the escalation. So the [connectors](https://flowrunner.ai/concepts/connectors) doing the reading are the easy half, and the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step belongs at the boundary where an answer becomes an outbound act. ### Without FlowRunner **Answers sit where nobody acts**: The survey report is a separate destination from the tools that send the next message **Segments built by hand**: Someone reads responses and moves contacts between lists on a schedule that slips **Detractors found late**: A low score is noticed during the weekly review, days after the person gave it ### With FlowRunner **The answer travels**: Each completed submission reaches the CRM, the sheet, and the channel that needs it **Segments follow the response**: Tagging happens on the answer itself, so the next campaign targets what was said **Escalation on arrival**: A low score reaches a named owner while the experience is still recent ## Use Case Scenarios ### The answer becomes the segment On New Submission fires the moment a respondent finishes. The agent reads the answers, resolves the contact in [ActiveCampaign](https://flowrunner.ai/integrations/activecampaign) or [HubSpot](https://flowrunner.ai/integrations/hubspot), syncs the record, and applies the tag that matches the answer that matters. A person who said they are evaluating this quarter and a person who said they are researching for next year leave the same survey on different tracks, without anyone exporting a spreadsheet in between. ResponseSuite records completed submissions only, never partial ones, so every record the agent acts on is a finished thought rather than an abandoned form. ### The reporting sheet that never re-reads the survey On a schedule, the agent calls List Submissions Since with the previous run's finish time and appends the new records to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) or [Airtable](https://flowrunner.ai/integrations/airtable). ResponseSuite's only time filter is a lookback window measured in minutes rather than a from and to range, so the action converts the timestamp into that window and reports the window it used alongside the results. The reporting sheet grows by exactly what arrived, and a run that finds nothing costs one request. ### A detractor reaches a person, not a dashboard A submission carrying a low satisfaction answer fires the trigger. The agent posts the response into the account team's [Slack](https://flowrunner.ai/integrations/slack) channel with the answers laid out, then writes the detractor answer onto the contact record so the next person who opens it sees the context. The customer success owner reads the actual words and decides who reaches out. The agent moved the answer to where a human could act on it within minutes, and stopped there. ## Human-in-Loop Highlight The risky operation on this connector is not a write, because there are none. It is Get All Submissions on a backfill. That action pages the submissions route until it runs out, stops at fifty pages, and reports `truncated: true` when it hits the ceiling. ResponseSuite offers no way to mark a submission as handled, so a backfill that gets truncated and then feeds tagging rules produces a segment built on part of the history, and a re-run tags people a second time. So the agent stops before the first tag: "Get All Submissions returned 4,800 records for the Q3 pricing survey and reported truncated: true. Tagging on a partial history will move contacts onto tracks the rest of the history may contradict, and nothing in ResponseSuite records that a submission was already acted on. Proceed with what came back, or narrow the survey and re-read first?" The marketing ops owner answers in Slack. The agent does the reading, the paging, and the matching. The decision to act on an incomplete picture stays with a person. Agent processes routinely Detects the ceiling Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Surveys 3 - **List Surveys** Returns the surveys in the account with their identifiers and published settings. The starting point for any flow that has to pick a survey to read from. - **Get Survey** Returns a single survey by identifier. ResponseSuite publishes no route for one survey, so this applies the survey filter to the list and returns the record that comes back. - **Find Survey By Name** Looks a survey up by its title, which is what a flow usually holds when a person chose the survey. Matching happens in FlowRunner, because the API offers no name filter. ### Submissions 3 - **List Submissions** Returns completed submissions with their answers, optionally narrowed to one survey and to a lookback window in minutes. - **List Submissions Since** Returns everything received since a point in time by converting that timestamp into the vendor's minutes window, and reports the window it used. The action behind an incremental sync. - **Get All Submissions** Pages the submissions route and returns every record in one array, for an export or a bulk sync. Reports when it stopped early rather than presenting a partial history as a whole one. ### Account and Connection 3 - **Get Current User** Returns the user the token belongs to. The cheapest way to confirm which ResponseSuite account a credential actually reaches when several are in play. - **Test Connection** Reads the current user and the first page of surveys and reports what the token can reach. An unknown account subdomain and an unknown route both answer with the same status, so this exists to tell them apart at design time. - **Make API Call** Sends an authorized request to any path below the account's API root, for a parameter or route the vendor adds later. ## Triggers 2 triggers ### Event Triggers 2 - **On New Submission** Fires when a survey receives a new completed submission, carrying the record and its answers. ResponseSuite stores no partially completed surveys, so this fires when the respondent finishes and never on the first answer. It polls a lookback window and remembers what it has already delivered, so a record fires once. - **On New Survey** Fires when a new survey appears in the account. Used to wire a freshly built survey into the rest of the stack, provision its reporting sheet, and tell the team it is live. ## Frequently Asked Questions ### What can FlowRunner do with ResponseSuite? FlowRunner agents can run List Surveys, Get Survey, and Find Survey By Name in ResponseSuite, plus 6 more actions. ### Does connecting ResponseSuite to FlowRunner require OAuth? No. ResponseSuite connects to FlowRunner with an API key, no OAuth flow required. ### Can ResponseSuite trigger a FlowRunner workflow automatically? Yes. ResponseSuite supports 2 triggers that can start a FlowRunner workflow automatically. **Work at ResponseSuite?** This integration exposes ResponseSuite to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/responsesuite. Site index: https://flowrunner.ai/llms.txt