Porsline

Porsline is an online survey builder for forms, questionnaires, quizzes and lead capture. Agents build surveys across every question type, manage folders, settings and access codes, generate personalized response links, read results and exports, and react on every new response.

1 trigger 32 actions API key available

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

On New Response fires when a respondent submits the selected survey

Agent reads the answers and the hidden field variables carried in through the link

Agent scores the response and compares it against what the account already looks like

Agent updates the account record with the score and the verbatim comment

A detractor summary posts to the owning manager's channel with the answers inline

The owner decides whether this response changes the renewal plan before any outreach goes out

What This Integration Enables

Most survey connectors let you read results. Porsline's API goes further in the direction that actually matters for automation: it exposes the authoring surface. An agent can create a survey, add questions across all fourteen Porsline question types with their choices, validation, scale configuration, branching edges and scoring rules, organize them into folders, set the respondent-facing behavior, and open or close the survey to new responses by flipping one setting. The questionnaire becomes something your process owns rather than something a person maintains beside it.

Two design facts shape how flows should be built here. Porsline sends its own messages: Create Email Notification, Create SMS Notification and Create Webhook Notification configure sends that fire on every submission from Porsline's side, without FlowRunner in the path, which is useful and worth knowing about before you wonder where a message came from. And Porsline runs two independent installations, survey.porsline.com and survey.porsline.ir, which are separate deployments rather than locales, so an account and its key exist on exactly one of them. That regional split is often the reason a team chose Porsline in the first place, and the connection setting treats it as a first-class part of the connection rather than a detail. Every action is built and verified against the Porsline API, and the operations that destroy collected data are exactly where FlowRunner's human-in-the-loop discipline applies.

Without FlowRunner

Surveys built by hand, then frozen Changing a question means opening the builder, so the survey slowly stops matching the process it measures

Untargeted links Everyone receives the same URL, so a response arrives without saying who sent it or which account it belongs to

Results read on a delay Somebody exports a spreadsheet on Friday, and the answers worth reacting to are already a week old

With FlowRunner

Surveys authored from the flow Questions, branching, settings and access codes are created and adjusted by the same flow that runs the program

One encrypted link per respondent Hidden field variables carry the account, segment and campaign into every response as it is submitted

Responses acted on as they land Each submission starts a flow that routes, scores and escalates before anyone opens a dashboard

Use Case Scenarios

Closing the feedback loop while the feedback is warm

On New Response fires. The agent reads the answers and the hidden variables that came in through the link, so it already knows the account and the segment without asking. It classifies the free text, scores the response, and writes both onto the account record in HubSpot. A low score with a specific complaint opens a ticket in Zendesk and posts the verbatim comment to the owning manager in Slack. A high score with a quotable line routes somewhere else entirely. The response is acted on in the minute it arrives rather than in the weekly export.
A personalized survey campaign, end to end

The agent pulls a segment, calls Create Survey Variables to define the hidden fields the responses should carry, then Generate Personalized Links to encrypt those values into one ready-to-send URL per respondent. The links go out through Brevo. If the survey needs to be closed to everyone else, Update Survey Settings turns on access code login and Create Authentication Codes loads a single-use code per participant. When the window closes, Update Survey Settings shuts the survey and Delete Authentication Codes revokes what is left outstanding. Nobody had to open the dashboard to start or stop the campaign.
Editing a live questionnaire without losing the history

Before any edit to a running survey, the agent calls Duplicate Survey to snapshot the current version, so the questions, theme and settings as they stood are preserved under a new id even though the copy starts with no responses. Then it reads Get Question on every question the change would touch, and builds a plain-language diff of what would happen: which titles change, which choice lists get replaced wholesale, which questions would be removed and how many answers those questions already hold. That diff goes to the research owner. The edits run only after it comes back approved, and List Responses plus Export Responses hand the resulting dataset to Google Sheets on the schedule the team reads.

Human-in-Loop Highlight

Delete Question sounds like tidying and behaves like a deletion of evidence. Removing a question from a survey removes the answers already collected for it, and any branching rules that pointed at that question stop making sense, which changes what the next respondent is shown. An agent asked to "clean up the redundant questions" can therefore destroy a column of research data and quietly rewrite the survey's logic in the same call. So it does not make that call. It posts the case instead: "Question 7, the open comment field, is flagged as redundant. It holds 1,340 collected answers, and questions 9 and 11 branch off it. Deleting it removes those answers and breaks both branches. Remove it, retire it by making it optional with Update Question, or leave it?" The research owner answers. Update Question and Update Survey Settings can undo almost anything else on this connector. Delete Question is the one that cannot, which is why it belongs to a person.

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

32 actions

Surveys

List Surveys Lists the surveys in the account, optionally narrowed to a folder or filtered by name, with each survey's language, question count, view count and submitted response count.
Get Survey Retrieves one survey in full: its status flags, theme, general settings, hidden field variables, welcome and thank you pages and its questions.
Create Survey Creates an empty survey, optionally inside a folder and in a chosen language. The starting point for a questionnaire built from the flow rather than in the builder.
Update Survey Partially updates a survey's own fields, such as renaming it or moving it between folders. Only the values supplied are changed.
Duplicate Survey Copies a survey including its questions, theme and settings. The snapshot step before any edit to a live questionnaire, and the way to version a template without rebuilding it.
Delete Survey Deletes a survey to the Porsline Trash, where it can still be restored from the dashboard. Its responses go with it.

Folders

List Folders Lists every folder with its surveys embedded, which is also the fastest way to read the whole account in one call.
Get Folder Retrieves one folder with its sharing details and the full list of surveys it contains.
Create Folder Creates a folder. Folders are the unit Porsline shares between team members, so this is usually the first step in setting up a shared workspace.
Update Folder Renames a folder or changes its display position. The surveys inside it are unaffected.
Delete Folder Deletes a folder from the account. Read Get Folder first, because what the folder contains determines what the deletion affects.

Questions

Create Question Adds a question to a survey, across all fourteen Porsline question types from plain text and multiple choice through opinion scales, ratings, rankings and matrices, with its choices, validation and scoring.
Get Question Retrieves one question with every field that applies to its type, including its choices, validation rules, branching edges and scoring rules. Read it before an update so the flow knows what it is about to replace.
Update Question Partially updates a question. Note that sending Choices replaces the whole option set rather than adding to it, so send the complete list.
Delete Question Removes a question from a survey along with the answers already collected for it, and leaves any branching rules that pointed at it broken. The operation this page's human gate exists for.

Responses and Exports

List Responses Reads a survey's responses as a results table with a header row and answer rows, plus the total responder count, with date range limits, sorting and filtering.
Export Responses Requests a downloadable Excel or CSV spreadsheet of a survey's responses and returns the URL Porsline generates for it. The handoff into reporting and warehousing.

Respondent Access

Get Survey Settings Retrieves the respondent-facing settings: authentication method, captcha, respondent detail visibility, location capture and navigation behavior.
Update Survey Settings Changes those settings, including opening and closing the survey to new responses. The one call that starts or stops a campaign on a schedule.
List Authentication Codes Lists the access codes loaded on a survey using access code login, so a flow can audit which codes are still issued before adding or revoking any.
Create Authentication Codes Adds access codes to a survey so only code holders can respond. Turn the feature on first with Update Survey Settings.
Delete Authentication Codes Removes access codes, revoking their holders' ability to respond. The closing step of a gated campaign.

Personalized Links

List Survey Variables Lists a survey's hidden field variables, the values carried into a response through the URL or computed while answering.
Create Survey Variables Adds hidden field variables to a survey so external values are stored alongside each response. Define them before referencing them in personalized links.
Generate Personalized Links Encrypts hidden field values into one personalized survey URL per respondent, up to 5,000 in a single request. The step that makes every incoming response self-identifying.

Notifications

List Notifications Lists every notification configured on a survey, of all three kinds, with its enabled state, sending method, recipients and results filter.
Get Notification Retrieves one notification with all of its settings. Read it before an update so the flow knows what it is changing.
Create Email Notification Configures the survey to send an email on every submission, to a fixed list, to the respondent's own answer to an email question, or to an address carried in a hidden field.
Create SMS Notification Configures the survey to send an SMS on every submission, with the same recipient options. A standing send that fires from Porsline's side rather than from the flow, so treat it as a change to the survey's behavior.
Create Webhook Notification Configures the survey to call an HTTP endpoint on every submission with a body and headers you control. Used to push responses to a system outside FlowRunner.
Update Notification Partially updates a notification. The most common use is enabling or disabling one without deleting it, which is the reversible way to pause a standing send.
Delete Notification Removes a notification from a survey permanently. Use Update Notification to pause one instead.

Triggers

1 triggers

Event Triggers

On New Response Fires when a respondent submits a response to the selected survey. The trigger registers its own webhook on that survey when it is enabled and removes it again when it is disabled, so nothing has to be set up or cleaned up in the Porsline dashboard.

Frequently Asked Questions

What can FlowRunner do with Porsline?

FlowRunner agents can run List Surveys, Get Survey, and Create Survey in Porsline, plus 29 more actions.

Does connecting Porsline to FlowRunner require OAuth?

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

Can Porsline trigger a FlowRunner workflow automatically?

Yes. Porsline supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Porsline

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us