BlockSurvey

BlockSurvey is a privacy-first survey and form platform that encrypts responses in the respondent's browser. Agents manage surveys and encrypted audience contacts, and keep contact lists in step with the rest of your stack.

13 actions API key available

BlockSurvey website Platform Documentation Capability data verified 2026-08-26

A new research cohort is approved in the CRM

Agent reads the cohort members and the segment tag each one carries

Create Contact adds every member to the audience list, encrypted with the list public key

Set Survey Text Variable pipes the wave and the source into the survey wording for this send

Update Survey Scheduled Start Date opens the study at the agreed time

The researcher receives the cohort size, the variables set, and the open date

The researcher reads the decrypted completion counts and decides when the study closes

What This Integration Enables

BlockSurvey is built for research where the results are the sensitive part. Responses are encrypted in the respondent's browser with the survey owner's public key, so BlockSurvey stores ciphertext it holds no key for and renders results client side. That is not a detail on a security page. It decides what this connector can be.

The vendor's public API publishes no response endpoint at all, and FlowRunner does not ship an action that would hand a workflow ciphertext dressed up as data. What agents get instead is the survey's frame and its audience: reading and moving the cut off date and the scheduled start date, raising or lowering the maximum response count, setting the text variables that carry campaign context into question wording, and keeping the audience list in step with the CRM, the billing system, or the event platform that owns the truth. These connectors are built and verified against the vendor's official API, including the asymmetry that matters most here: writing a contact needs only the list public key, while reading one back requires sending the list private key so BlockSurvey can decrypt server side. On a sensitive list, key your workflows on the record id a write returns rather than reading records back.

Everything an agent can do here changes the conditions under which data is collected, without ever seeing the data. That is exactly the case FlowRunner's human-in-the-loop model is built for, because the only person who can see the results is the one holding the key.

Without FlowRunner

Study administration by hand Opening, closing, and capping a study means someone logging in at the right moment

Audience drift The list in the survey tool and the list in the CRM stop agreeing the week after they are built

Erasure requests handled ad hoc Removing a contact on request is a manual lookup nobody has a repeatable path for

With FlowRunner

Study windows driven by real events A quota hit or a milestone in another system moves the start date without anyone watching a clock

Audience kept in step Contacts are added, updated, and removed as the upstream record changes, encrypted on write

Erasure as a workflow An opt-out routes to Delete Contact and completes without any key ever leaving your side

Use Case Scenarios

The study opens when the cohort is ready, not when someone remembers

A cohort clears recruitment screening in HubSpot. The agent reads the approved members, calls Create Contact for each one so the record is encrypted to the audience list on write, and calls Set Survey Text Variable to carry the wave number and the recruitment source into the survey's wording. Update Survey Scheduled Start Date then opens the study at the time the protocol specifies. The researcher gets a message in Slack confirming the cohort size and the open time. Nothing about the study's design changed, and nobody had to be at a keyboard at 08:00.
Quotas enforced from the system that owns them

A study is capped at a participant count agreed with the client, and the count that matters lives in the project record, not in BlockSurvey. On a schedule, the agent reads the current allocation from the project tracker, calls Get Survey Response Limit to see what the survey is currently set to accept, and calls Update Survey Response Limit when the two disagree. When the client buys another wave, lifting the cap reopens a study that had filled up, and the change happens the same hour the approval lands rather than the next time someone opens the platform.
An opt-out that completes without a key

A participant asks to be removed. The request arrives through a helpdesk ticket in Zendesk or a reply the agent classifies as an erasure request. The agent resolves the contact's record id from the write log it kept when the contact was created, calls Delete Contact, which deliberately requires no key at all, and closes the ticket with the confirmation. The suppression list in Mailchimp gets the same treatment in the same run. The erasure is complete and no private key was transmitted anywhere in the process.

Human-in-Loop Highlight

Update Survey Cut Off Date is the operation that ends data collection, and BlockSurvey's design means an agent has no way to check its own work before running it. There is no response endpoint anywhere in the API, no result count, no completion rate, no segment breakdown. The agent can see when the survey opens, when it is set to close, and how many responses it is willing to accept, and nothing else. Once the cut off passes, anyone holding a live link finds a closed survey, and what those partial responses would have contained is unknowable to every party except the respondent.

So the study agent brings evidence from outside and stops. It posts: "Recruitment in the CRM shows 412 invitations sent and 388 marked delivered for Wave 3, and the client quota is 350 completes. The survey cut off is currently set to Friday 23:59. I cannot read completion counts, because BlockSurvey holds no key for them. Move the cut off to tonight, hold it at Friday, or extend it?" The researcher opens BlockSurvey, where their own browser decrypts the real completion figures by segment, and answers. The agent then moves the date and lowers the cap in the same run. The scheduling, the audience sync, and the variable wiring were automatic. The judgment that required seeing the data stayed with the only person who can see it.

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

13 actions

Survey Scheduling

Get Survey Cut Off Date Reads the date and time after which a survey stops accepting responses. The check step before any workflow that changes a study's window, so a flow knows what it is about to overwrite.
Update Survey Cut Off Date Moves the date after which a survey closes. Used to end a study when an external quota is met, or to extend one when recruitment runs behind. The operation this page's human gate exists for, because no action in this connector can report what has been collected.
Get Survey Scheduled Start Date Reads the date and time a survey is set to open. Used to confirm a study is queued as expected before an upstream workflow commits to a send.
Update Survey Scheduled Start Date Sets when a survey becomes available. Used to open a study automatically when a cohort clears screening, a milestone lands, or a client approval comes through.

Response Caps

Get Survey Response Limit Reads the maximum number of responses a survey will accept. Used to compare the platform's cap against the quota recorded in the system that actually owns it.
Update Survey Response Limit Raises or lowers the maximum response count. Lowering it enforces a participant quota, and raising it reopens a study that filled up when another wave is bought.

Survey Variables

Get Survey Text Variable Reads the current value of a named text variable on a survey. Used to confirm what context the survey is currently piping into its question wording.
Set Survey Text Variable Sets a named text variable so campaign context reaches the respondent inside the question itself. Used to carry a wave, a source, or a segment into the survey per send, without editing the survey.
Delete Survey Text Variable Removes a text variable from a survey. Used at the end of a wave so stale context cannot leak into the next one.

Audience Contacts

Create Contact Adds a contact to an audience list, encrypted with the list public key so the server never receives a decryption key. Returns the record id, which is the safe handle to key later workflow steps on.
Update Contact Updates a contact on an audience list, encrypting the new values with the list public key. Used to keep the audience in step with a CRM, a billing system, or an event platform as the upstream record changes.
Get Contact Reads a contact back. This is the one operation that requires the list private key in the request, because BlockSurvey decrypts the record server side to answer it. Configure the private key only if a workflow genuinely needs this, and prefer keying on record ids on a sensitive list.
Delete Contact Removes a contact from an audience list. It deliberately requires no key at all, which makes it the natural endpoint for an opt-out or erasure workflow.

Frequently Asked Questions

What can FlowRunner do with BlockSurvey?

FlowRunner agents can run Get Survey Cut Off Date, Update Survey Cut Off Date, and Get Survey Scheduled Start Date in BlockSurvey, plus 10 more actions.

Does connecting BlockSurvey to FlowRunner require OAuth?

No. BlockSurvey connects to FlowRunner with an API key, no OAuth flow required.

Can BlockSurvey trigger a FlowRunner workflow automatically?

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

Start building with BlockSurvey

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us