SEEN

SEEN renders one personalized film per recipient and delivers it by email, SMS, push, or landing page. Agents create data items in a workspace to trigger a render, list and retrieve items, and react as new recipients are added.

1 trigger 3 actions API key available

SEEN website Platform Documentation Capability data verified 2026-08-28

A milestone lands upstream, such as a renewal date, a policy anniversary, or a year in review

Agent assembles each recipient's fields from the CRM and the billing record

Agent checks every field name against the Properties the SEEN workspace actually defines

Create Data Item writes one record for a single internal reviewer, and the workspace Journey renders that film

Get Data Item reads back exactly what SEEN stored for that recipient

Agent posts the rendered film and the field mapping to the campaign owner

The campaign owner watches their own film, then releases the roster or corrects the mapping first

What This Integration Enables

SEEN is a mail merge whose merged output happens to be a film. That framing matters, because it explains why the connector is three operations wide rather than thirty. You do not ask SEEN to render a video. You write a data item into a workspace, and the Journey configured in the SEEN canvas decides what gets rendered, what it says, and whether it reaches the person by email, SMS, push, or a landing page. FlowRunner agents supply the record. SEEN supplies everything downstream of it.

The payload is a flat object whose field names must match the Properties configured in the workspace, and there is no fixed schema the connector can validate for you. That is exactly the kind of quiet coupling that rewards human-in-the-loop discipline. An agent can assemble, verify, and write records at machine speed. What it should not do is discover a mapping error one thousand named films after it started, because the connector offers no way to edit or withdraw a record once it has been written.

Without FlowRunner

Personalization stops at the salutation The video is identical for everyone and only the covering email changes

One film per campaign Producing a variant means going back to an editor, so variants do not get made

The list and the render live apart Someone exports a CSV, uploads it, and hopes the columns still line up

With FlowRunner

The film is the personalized part Each recipient's own numbers, name, and milestone are rendered into the footage

Variants are a data question A new segment is a different set of records against the same Journey

The roster stays where it is maintained Records are written straight from the system of record, one recipient at a time

Use Case Scenarios

A year in review nobody had to produce

At the close of a period, the agent queries the accounts that stayed active, pulls their usage and milestone figures from Google Sheets or the warehouse, and shapes one flat object per customer against the workspace Properties. Create Data Item writes each record, and the Journey renders a film that names the customer, shows their own numbers, and ends on a landing page tailored to them. Because SEEN accepts a single object per call rather than an array, the loop runs one recipient at a time, which is also what makes it easy to stop partway through when something looks wrong.

Renewal films triggered by the record, not the calendar

A renewal date in HubSpot or a paid invoice in Stripe moves the account into the renewal window. The agent resolves the account owner, gathers the tenure and plan details, and writes a data item carrying a distinct id so SEEN's duplicate protection applies. The Journey delivers the film through the channel that account prefers, and the agent logs the send back against the CRM record so the rep sees it before their next call.

Recipients arriving from three directions, reconciled in one place

Data items reach the workspace from this connector, from CSV imports the campaign team runs, and from people added directly in the SEEN Platform. The On New Data Item trigger fires for all three, so the agent can treat the workspace as the single roster of record. It reads each new item with Get Data Item, matches it back to a contact in Salesforce, and posts a running count to the campaign channel in Slack so the marketing owner can see the roster fill in real time rather than after the fact.

Human-in-Loop Highlight

This connector has no update, no delete, and no recall. Create Data Item, List Data Items, and Get Data Item are the whole surface, and the create is not a draft: if the workspace has a Journey with an On Create trigger, writing the record is what renders the film and delivers it. A wrong Property name does not fail loudly. It produces a film with a blank where the customer's name should be, and it produces one for every person in the loop. So the agent writes exactly one record first, for a reviewer inside the company, and stops. It posts: "Test film rendered for the roster of 1,240 renewals. Fields mapped: first_name, plan_name, tenure_months, renewal_date. Watch it and confirm the mapping, or tell me which field is wrong. Nothing else sends until you answer." The person watches thirty seconds of video and answers. What made this safe was not the agent's field validation, because SEEN's schema is defined outside the API and cannot be validated from here. It was that a human saw one finished film before the roster ran.

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

3 actions

Rendering a Film

Create Data Item Writes one data item into a workspace, which is what a personalized film is generated from. When the workspace has a Journey with an On Create trigger, this single call is the whole render and deliver step. SEEN takes one object per call rather than an array, so a recipient list is a loop, and an item carrying a distinct id gets SEEN's duplicate protection.

Reading the Workspace

List Data Items Lists the workspace's data items, optionally narrowed by a search query and paged with limit and offset. Used to reconcile the roster against the system of record.
Get Data Item Reads one data item by its id. Used to confirm exactly what SEEN holds for a recipient after a create, which is how a test render is verified before a batch runs.

Triggers

1 triggers

Event Triggers

On New Data Item Fires when a data item appears in the workspace, whether it was written through this connector, imported from a CSV, or added by hand in the SEEN Platform. The first poll records what is already present and emits nothing, so an existing workspace does not flood a new flow. To learn when a video has finished rather than when a recipient was added, place SEEN's own Webhook Node after the Player node in the Journey canvas and point it at FlowRunner.

Frequently Asked Questions

What can FlowRunner do with SEEN?

FlowRunner agents can run Create Data Item, List Data Items, and Get Data Item in SEEN.

Does connecting SEEN to FlowRunner require OAuth?

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

Can SEEN trigger a FlowRunner workflow automatically?

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

Start building with SEEN

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

Start Building Free Talk to us