Survicate

Pull customer feedback out of Survicate through its Data Export API. Agents list surveys and questions, export NPS and CSAT responses for incremental syncs, look up respondents, and enrich them with custom attributes for segmentation.

6 actions Basic auth available

Survicate website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

An hourly sync job wakes up with the timestamp of its last successful run

List Survey Responses pulls the NPS survey's responses with the since filter set, so only new and updated feedback moves

Get Respondent resolves each response's respondent record with their known attributes

Each response lands in the warehouse table and on the respondent's CRM record with score and answers attached

Responses scoring in the detractor range are separated from the stream

Each detractor posts to the customer success channel with score, verbatim answer, and the respondent's plan and lifecycle attributes

The CS manager reads the verbatim, weighs the account context, and decides whether this is a save call, a product ticket, or a pattern worth escalating

What This Integration Enables

Survicate's Data Export API is honest about what a feedback platform owes the rest of your stack: everything, incrementally, with the respondent attached. FlowRunner agents use it as a pipeline, not a dashboard: the since filter makes hourly syncs cheap, Get Respondent joins each answer to a known person with traits, and Add Respondent Attributes closes the loop by writing your systems' truth back into the segmentation Survicate targets on. Feedback stops being a quarterly report and becomes a stream your workflows act on, with the question structure read from the API so parsing survives every survey edit. - Export NPS, CSAT, CES, and other survey responses on a schedule, incrementally via the since filter - Read a survey's question structure and answer options before processing its results, so parsing survives survey edits - Join responses to respondent records with their known attributes and identifying details - Enrich respondents with custom attributes like plan, signup date, and lifecycle stage for future targeting - Route low scores and negative verbatims to the channel and queue where follow-up happens

Without FlowRunner

Feedback exports are a monthly chore Someone downloads a CSV, reshapes it, and the warehouse is always weeks stale

Scores arrive without people attached A 2 out of 10 sits in the dashboard with no plan, tenure, or owner context

Segmentation attributes rot The plan and lifecycle traits Survicate targets on were set once and never updated

With FlowRunner

Syncs are incremental and hourly The since filter moves only new and updated responses, so the warehouse tracks reality

Every response carries its respondent Agents join score, verbatim, and traits before anything reaches a human

Attributes update from source systems Billing and CRM changes flow into respondent traits, and targeting stays honest

Use Case Scenarios

The warehouse sync that never re-exports

Every hour, an agent runs List Survey Responses per active survey with since set to the last run's timestamp. New and updated responses are shaped against the structure from Get Survey Questions, which the agent refreshes whenever parsing fails, and appended to the feedback table alongside [Google Sheets](/integrations/google-sheets) for the team's working view. Because the sync is incremental, a workspace with years of history costs the same to sync as one week does. The BI dashboards read fresh feedback without anyone touching an export button.

Detractors reach a person while the feeling is fresh

The hourly sweep splits NPS responses by score band. Promoters log quietly. Detractors trigger the join: Get Respondent pulls the person's traits, the agent matches them to their record in [HubSpot](/integrations/hubspot), and the packet posts to [Slack](/integrations/slack): score, verbatim answer, plan, tenure, and account owner. The owner decides the response, a call, a credit, or a documented product complaint, while the customer still remembers writing it. The agent guarantees the delivery; the human owns the judgment.

Segmentation that inherits the billing system's truth

Survey targeting is only as good as the traits it filters on. A nightly agent reads plan changes and lifecycle transitions from the billing and CRM systems, resolves each customer to their Survicate respondent, and drafts the updates for Add Respondent Attributes: plan, renewal quarter, lifecycle stage. The batch summary goes to the research owner before it writes, because these traits decide who gets asked what. Approved batches apply, and the next churn-risk survey targets people who are actually at risk, not people who were at risk in March.

Human-in-Loop Highlight

Add Respondent Attributes is the only write in this connector, and it overwrites: an attribute with a matching name is replaced, and the previous value is gone without a version history to recover from. That makes a bulk enrichment run quietly dangerous, because these traits are what Survicate targets surveys with. Write the wrong plan value across ten thousand respondents and the damage is not one bad field: it is every future survey asking the wrong people the wrong questions, and a research program that no longer knows its segments are fiction. So bulk attribute writes run as drafted batches: "Updating lifecycle_stage on 9,400 respondents from the billing export. 312 records would change from active to churned. Sample attached. Apply?" The research owner spot-checks the sample, catches that the export included trial expirations, corrects the mapping, and approves. Reads are free to automate. The write that decides who gets asked deserves a witness.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

6 actions

Surveys

List Surveys Retrieves all surveys in the workspace with each survey's ID, name, type, status, language, and timestamps, paginated. The inventory step that scopes sync jobs.
Get Survey Retrieves a single survey's full details by ID, including name, type, status, language, theme, and configuration. Used to confirm a survey's state before processing its responses.
Get Survey Questions Retrieves the questions that make up a survey, with each question's ID, type such as nps, single, multiple, text, or rating, label, and answer options. The structure map that keeps response parsing correct as surveys evolve.

Responses

List Survey Responses Retrieves a survey's responses with respondent, submission status, per-question answers, and timestamps, paginated, with an optional since filter for fetching only responses created or updated after a given time. The engine of incremental syncs.

Respondents

Get Respondent Retrieves a single respondent by ID, including their known attributes and identifying details. The join step that turns an anonymous score into a person with context.
Add Respondent Attributes Adds or updates custom attributes on a respondent as name and value pairs, overwriting attributes with matching names while preserving the rest. The segmentation write this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Survicate?

FlowRunner agents can run List Surveys, Get Survey, and Get Survey Questions in Survicate, plus 3 more actions.

Does connecting Survicate to FlowRunner require OAuth?

No. Survicate connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Survicate trigger a FlowRunner workflow automatically?

Survicate doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Survicate

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us