Tripetto

Tripetto studio is the hosted half of Tripetto's conversational form and survey product. Agents manage workspaces and forms, read definitions, styling, localization and connections, pull submitted responses, and react on each new response.

1 trigger 23 actions Session available

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

A campaign needs a new conversational form wired into the stack, and List Forms picks it up

Get Form returns the definition, the current connections and the concurrency token

The agent reads which destination already occupies the form's single custom webhook slot

Get Form Share Tokens confirms the public link the campaign is about to publish

Update Form Connections writes the full destination set the campaign needs

The marketing owner receives the before and after connection map for the form

The owner confirms which destination keeps the one custom webhook slot before the write lands

What This Integration Enables

Tripetto is for teams who want a conversational form they actually own the structure of. A form here is a JSON definition with blocks and logic branches, presented through one of three faces, and the studio that holds it is a saved canvas rather than a list. That design is the reason this connector is worth having: because every form artifact is a document, an agent can read a working form, adapt it, and stand up the next one without a person opening a builder. FlowRunner agents walk the workspace tree, read and replace a form's definition, styling, localization, tracking and connections, mint the share and template links a campaign publishes, and pull completed responses with each answer already rendered as a string a flow can bind to.

Two facts belong on this page rather than in a footnote. The credential is a studio email address and password rather than an API key, because Tripetto issues no account-level key, and the studio is currently closed to new registrations, so this connector serves accounts that already exist. And every write in this connector replaces the object it targets rather than merging into it. That is not a limitation to work around quietly. It is the reason human-in-the-loop belongs in the middle of the flow: an agent can read a form, compose the exact document it intends to write, and show a person the difference before anything is saved. Every action is built and verified against the studio's own API.

Without FlowRunner

Wiring done by hand in the studio Every new campaign form is connected click by click, and nobody records what it was connected to

Partial edits that erase A change to one setting is saved over a document that holds every other setting too

Responses read in the studio Answers are exported or read on screen, so downstream systems learn about a lead late

With FlowRunner

Wiring described once and applied The agent reads the whole form document, changes what it needs and writes the rest back unchanged

Concurrent edits refused, not overwritten A stale write is rejected rather than quietly clobbering what someone else just saved

Completed responses routed on arrival The finished conversation reaches the CRM and the owning rep as one structured record

Use Case Scenarios

Standing up a campaign form without breaking the one already running

A new campaign reuses the structure of a form that is already collecting. The agent calls Get Form on the original, keeps the definition and the concurrency token, creates the variant with Create Form and Update Form Definition, applies the brand with Update Form Styles, and sets the language with Update Form Localization. Then it reaches the connections. Tripetto gives a form one custom webhook slot, and the destination set is a single document, so the agent composes the full object it intends to write, shows the marketing owner what each of the six slots will hold afterwards, and waits. Update Form Connections runs once the owner has answered.
A finished conversation lands in the CRM as a record

New Form Response fires when a respondent completes the form. The agent calls Get Response for the answers, which arrive as a fields array carrying the question name, the raw value and a string rendering of each. Questions the respondent skipped through a logic branch are absent rather than empty, so the agent treats a missing field as a branch that was not taken rather than as a blank answer. The contact and its answers are written into HubSpot, the transcript posts to the owning rep in Slack in the order the respondent gave it, and a row appends to Google Sheets for the campaign report.
Localizing one form into a family

A form that works in one market needs to run in four. The agent reads the source form once with Get Form, then for each target language creates a new form, writes the same definition, and calls Update Form Localization with that language's wording for the runner's own buttons and messages. Update Form Trackers points each variant at the right property in Google Analytics so the campaign reports separately per market. Get Form Share Tokens hands back the four public links, and the campaign publishes them in one pass rather than four sessions in the studio.

Human-in-Loop Highlight

Update Form Connections is the operation on this connector that can break something silently. Tripetto stores a form's outbound destinations as a single object with one slot each for email, Slack, the three partner integrations and one custom webhook, and the write replaces that object whole. A form already delivering to a customer's own endpoint has that endpoint sitting in the only custom webhook slot there is. So the agent composes the write and stops: "Form Enterprise Demo Request currently posts to hooks.internal.acme.com in its custom webhook slot, and its email and Slack slots are enabled. The change you asked for needs that same slot. Applying it stops deliveries to hooks.internal.acme.com. Keep the existing endpoint, or hand the slot to the new destination?" The marketing owner decides. No log in this API tells you what a connection used to be, which is precisely why a person, not an agent, chooses what gets displaced.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

23 actions

Account

Get Account Returns the studio account the configured credentials belong to. The cheapest confirmation that the sign in works before a flow does real work.

Workspaces

Get Root Workspace Returns the account's root workspace with its name, item count, concurrency token and raw board layout. The starting point for walking the studio tree.
Get Workspace Returns one nested workspace by ID with its layout and concurrency token. Keep the token if a write is coming, because it is what detects a concurrent change.
List Workspaces Lists the workspaces inside the root or inside a named workspace, optionally descending recursively. The walk is bounded and reports when it stopped early.
Create Workspace Creates an empty workspace and returns its ID and concurrency token. It has no name and no tile on any parent board until a write supplies them.
Update Workspace Renames a workspace and replaces its board layout. Both are written on every call, so read first and send back a modified copy rather than a fragment.
Delete Workspace Permanently deletes a workspace. The studio offers this only for an empty one, so move or delete the forms inside it first.

Forms

List Forms Lists the forms on a workspace board with their ID and, usually, the name, face and response count the studio cached on each tile. Optionally descends into sub workspaces.
Get Form Returns everything the studio stores for one form: definition, face, styling, localization, connections, trackers, share tokens and concurrency token. The read that every write in this connector should start from.
Get Form Summary Returns a form's name, face and total response count without the full definition. The cheap way to watch a response count move.
Create Form Creates an empty form with the chosen face and returns its ID and concurrency token. It holds no questions until a definition is written and no tile until a board layout references it.
Delete Form Permanently deletes a form and every response collected for it. The studio itself offers this only once a form has no results, so read or export anything you need first.

Form Configuration

Update Form Definition Replaces the JSON document holding every question, cluster and logic branch. Written whole rather than merged, and refused outright if the concurrency token is stale.
Update Form Face Switches the form between Autoscroll, Classic and Chat. Questions and logic are untouched, but styling is stored per face, so the new face starts from its own defaults.
Update Form Styles Replaces the styling document for the current face: colors, fonts, spacing and background. Written whole, so read the current values before changing one of them.
Update Form Localization Replaces the language, locale and translated wording of the runner's own buttons and messages. A form that has never been customized reads back empty, which is the correct starting point.
Update Form Trackers Replaces the activity tracking configuration that wires a form to analytics and pixel services. Tracking fires in the respondent's browser, so this changes what the published form reports rather than what a flow sees.
Update Form Connections Replaces the whole set of outbound destinations a form fires on each response. There is exactly one custom webhook slot per form, which is what this page's human gate exists to protect.

Sharing

Get Form Share Tokens Returns the public share tokens and the shareable link built from them. Treat both as public, because anyone holding them can open the form and submit to it.
Get Form Template Token Returns the template token and link that let someone copy the form's structure into their own account. It carries no responses, and comes back empty for a form never shared as a template.

Responses

List Responses Lists every response for a form, newest first, with the submission timestamp and the form version fingerprint. Answers are not included here.
Get Response Returns one response's answers as a fields array carrying each question name, its raw value and a string rendering. Questions skipped by a logic branch are absent rather than empty.
Delete Response Permanently deletes one response and lowers the form's response count. Used to honor a respondent's deletion request or to clear test submissions before a form goes live.

Triggers

1 triggers

Event Triggers

New Form Response Fires when a respondent completes the chosen form, delivering the raw response JSON with one entry per answered question. Starting the flow points the form's custom webhook at FlowRunner and stopping it puts the previous webhook back, so a form watched by this trigger cannot also carry a custom webhook of its own. Only completed submissions are delivered.

Frequently Asked Questions

What can FlowRunner do with Tripetto?

FlowRunner agents can run Get Account, Get Root Workspace, and Get Workspace in Tripetto, plus 20 more actions.

Does connecting Tripetto to FlowRunner require OAuth?

No. Tripetto connects to FlowRunner with session-based authentication, no OAuth flow required.

Can Tripetto trigger a FlowRunner workflow automatically?

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

Start building with Tripetto

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us