SurveyTale
FormsSurveyTale is an interactive, story-driven survey platform that runs surveys as hosted links, in-app widgets and in email. Agents read responses, manage contacts and attributes, build personalized survey links, manage webhooks and organization resources, and react to new responses.
What This Integration Enables
SurveyTale is built for teams who run surveys inside the product and inside the email, not as a link they send once a quarter. A response is not a row that appears when someone clicks submit. It is a live record that grows answer by answer, which is why the connector carries three separate triggers on the same object and why reading the record back is more reliable than trusting a webhook payload. FlowRunner agents read responses and their capture metadata, mint personalized links per contact or per segment, keep the contact list and its attribute schema in step with the systems that own customer data, and manage the workspace grants that decide who can see which surveys.
The connector also makes SurveyTale's response pipeline visible instead of implicit. Writing a response is not a database insert in this product: it fires webhooks, integrations and the survey's follow-up email. That is exactly the class of operation FlowRunner's human-in-the-loop discipline exists for. The agent gathers, matches, maps and drafts at machine speed, and the call that reaches a real inbox waits for a person. Every action here is built and verified against SurveyTale's own Management API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Escalating on the first answer, not the last
A customer opens an in-app survey and rates the onboarding experience poorly on question one, then keeps going. On Response Created has already fired. The agent calls Get Response for the authoritative record, uses Get Survey to resolve the answer key back to the question text, and reads the contact attributes recorded with the response so it knows the plan, the account age and the assigned CSM. A ticket opens in Zendesk with the verbatim comment, and the CSM gets the full picture in Slack. By the time the respondent reaches the last question, a person already knows.
-
One unique link per recipient, merged from your own list
An outbound campaign needs a survey link that opens already knowing who is answering. The agent pulls the target audience from HubSpot, reconciles it into the workspace with Upload Bulk Contacts after confirming with List Contact Attribute Keys that every field it intends to send already exists, then calls Get Segment Survey Links to mint one signed URL per contact with the merge fields attached to each row. The campaign sends without anyone building a mail merge, and each response arrives already attributed to a known customer rather than to an email address someone typed.
-
A migration that does not mail your customers twice
A team moves two years of survey history into SurveyTale so the reporting is continuous. Create Response is the right operation, but in this product it runs the whole response pipeline, so a straight import would fire every integration on that survey and send the follow-up email to everybody in the file. The agent prepares the import, counts the rows, reads which triggers and integrations are subscribed with List Webhooks, and stops. A person confirms the survey has been quieted before a single historical response is written. Then the load runs unattended, and Delete Response is available for the handful that need correcting.
Human-in-Loop Highlight
In most connectors, writing a record is a write. In SurveyTale it is an event. Create Response fires the survey's webhooks, its integrations and its follow-up emails, and Update Response marking a response finished is precisely what sends that follow-up. So a backfill agent does not start writing. It posts what it is about to do: "Ready to import 1,840 historical responses into the Q3 onboarding survey. That survey has three active integrations and a completion email attached, so importing as is will send 1,840 people a thank-you note for a survey they answered last year. Import now, or hold while you disable the survey's integrations?" The CX owner answers, and only then does the load run. Nothing in this API unsends an email, so the decision to send one is not the agent's to make.
Agent Capabilities
36 actionsResponses
5- List Responses Lists responses newest first, filtered to one survey, one contact or a date window. The read behind reporting, reconciliation and any sweep that has to catch what a webhook missed.
- Get Response Retrieves one response with its full answer map, variables, per question timing and capture metadata. Used after a trigger fires, because the record is authoritative and the delivery is not.
- Create Response Records a response collected outside the SurveyTale runtime, for historical imports or for a front end you rendered yourself. This runs the full response pipeline, which is why it sits behind this page's human gate.
- Update Response Updates an existing response, which is how a partial answer set is completed or corrected. Marking a response finished sends the survey's follow-up email, so treat it as an outbound act.
- Delete Response Permanently deletes one response and hands back the record as it stood immediately before removal, so the answers can still be archived downstream. It also removes the response from the survey's summary statistics.
Surveys
2- List Surveys Lists the surveys the key can reach with their name, type, status and question set. The starting point for any workflow that has to resolve a survey by name rather than by ID.
- Get Survey Retrieves one survey with its questions, endings, variables and styling. Used to map a response's answer keys back to the questions that produced them.
Survey Links
2- Get Personalized Survey Link Builds a signed link for one contact so the survey opens already knowing who is answering, with an optional expiry. Used when a flow hands a survey to a specific person mid-conversation.
- Get Segment Survey Links Generates one unique link for every contact in a segment in a single call, optionally carrying merge fields alongside each URL. This is what turns an outbound campaign into a set of attributed responses.
Contacts
2- Create Contact Creates one contact in a workspace from a flat attribute map keyed on email. Used for single additions arriving from a signup or a CRM webhook.
- Upload Bulk Contacts Imports a batch of contacts into a workspace, creating new ones and updating existing ones matched on email. The body shape differs from Create Contact on purpose, so a flow picks one path and stays on it.
Contact Attributes
5- List Contact Attribute Keys Lists the attribute definitions contact data is validated against. Run it before any import, because an attribute that does not exist in the workspace rejects the whole row.
- Get Contact Attribute Key Retrieves one attribute definition with its wire key, display name, data type and uniqueness flag.
- Create Contact Attribute Key Defines a new contact attribute in a workspace. The machine name is fixed at creation, so this is the operation that decides the schema an integration will write against for good.
- Update Contact Attribute Key Renames an attribute or changes its description without touching the wire key or data type, so stored contact data is never invalidated by it.
- Delete Contact Attribute Key Permanently deletes an attribute definition. Contacts keep their stored values, but segment rules and imports that still reference the key stop working.
Webhooks
5- List Webhooks Lists the webhooks registered in reachable workspaces with their target URL, subscribed triggers and watched surveys. The audit read before anyone asks why an event went missing.
- Get Webhook Retrieves one webhook's URL, triggers and watched surveys, so a debugging flow can confirm what an endpoint is actually subscribed to.
- Create Webhook Registers a webhook that delivers response events to an endpoint of your own, for systems FlowRunner does not reach. The three triggers manage their own webhooks separately.
- Update Webhook Replaces a webhook's configuration. SurveyTale requires the full field set here, so anything omitted is written as sent rather than merged. Read the current values first.
- Delete Webhook Removes a webhook and returns the record as it stood before removal, so the URL and trigger list can be logged. Deliveries stop immediately.
Organization and Access
13- List Roles Lists the membership roles this instance recognizes, which are the values a member's role can be set to.
- List Teams Lists the teams in an organization. A team is the unit that gets granted access to a workspace, so this is where an access audit starts.
- Get Team Retrieves one team with its name, owning organization and timestamps.
- Create Team Creates a team. It holds no workspace access and no members until both are granted.
- Update Team Renames a team without touching its workspace grants or its membership.
- Delete Team Permanently deletes a team and every workspace grant it held. Members lose the access the team gave them while keeping their organization membership.
- List Users Lists organization members with role, team memberships, active flag and last sign in. Exposed on self hosted instances only.
- Create User Adds a member to an organization with a role and optional team memberships. Self hosted only, because the hosted product invites members through its own interface.
- Update User Updates a member's name, role, team memberships or active flag. The member is identified by email rather than by ID, so email travels on every call.
- List Workspace Teams Lists which team holds which permission on which workspace. The access audit view, and the source of the exact identifier trio a revocation needs.
- Create Workspace Team Grants a team access to a workspace at read, read and write, or manage level. This is what makes a newly created team able to see anything at all.
- Update Workspace Team Changes the permission a team holds on a workspace, matched on the team and workspace pair rather than on a grant ID.
- Delete Workspace Team Revokes a team's access to a workspace. It requires the full identifier trio, so read the exact values before calling it.
Connection and Scope
2- Get API Key Scope Reports the organization the key belongs to and every workspace it can see with the permission it holds there. Run this first, because a workspace is a tenant here rather than optional context.
- Check Health Reports whether the instance can reach its database and cache. Needs no credentials, so it separates a genuine outage from a permission problem and doubles as a reachability probe for a self hosted install.
Triggers
3 triggersEvent Triggers
3- On Response Created Fires the moment a respondent submits their first answer, before they reach the end. This is the trigger for reacting to a bad rating while the customer is still in the survey.
- On Response Finished Fires when a respondent reaches the end and the response is marked complete. Use it for scoring, routing and reporting, because the answer map is whole. It also fires when an earlier partial response is later completed.
- On Response Updated Fires on every change to an existing response, including each additional answer as the respondent moves through the survey. Useful for live progress tracking, and noisier than the other two by design.
Frequently Asked Questions
What can FlowRunner do with SurveyTale?
FlowRunner agents can run List Responses, Get Response, and Create Response in SurveyTale, plus 33 more actions.
Does connecting SurveyTale to FlowRunner require OAuth?
No. SurveyTale connects to FlowRunner with an API key, no OAuth flow required.
Can SurveyTale trigger a FlowRunner workflow automatically?
Yes. SurveyTale supports 3 triggers that can start a FlowRunner workflow automatically.
Other Forms integrations
Start building with SurveyTale
Free plan, no card required. Connect in minutes.