Bonjoro

Queue personal video messages for your team to record and send with Bonjoro. Agents create a greet task when a signup, renewal, or milestone deserves a human face rather than another templated email.

1 trigger 18 actions OAuth available

Platform Documentation ↗ Capability data verified 2026-08-02

A trial account crosses the activation threshold that predicts a real evaluation

Agent pulls the account, the plan being trialled, and what the team has already done inside the product

List Greets To Do returns the recording backlog already sitting with the assigned owner

Agent confirms the contact is not already queued and has not converted since the event fired

Create Greet queues the recording task with a note explaining why this account, not just who

The owner films the video, reassigns it to a colleague who knows the account better, or deletes it because the moment has passed

What This Integration Enables

Bonjoro is the odd one out, and it is the clearest statement of what FlowRunner is for. A greet is a task asking a named colleague to record a personal video for a named contact. The agent cannot record it. There is no automated path to a finished video, by design, because the entire value of the thing is that a person's face is in it.

So what the agent actually does here is decide that a moment is worth a person's time and then hand it over with enough context to be useful. It watches the product, the CRM and the billing system, recognises the events that mean something, creates the greet, attaches the note that says why, assigns it to the right colleague, and gets out of the way. This is the human-in-the-loop pattern with the proportions reversed: normally the agent does the work and pauses for a decision, and here the agent makes the decision and pauses for the work. Both directions rest on the same commitment, which is that the platform knows which half belongs to a person.

One practical note before you build: Bonjoro's OAuth2 client ID and secret are issued directly by Bonjoro. There is no developer console and no self-service key page, so setup starts with a conversation rather than a signup.

Without FlowRunner

Videos for whoever is remembered Personal videos get recorded for the accounts that happen to come up in conversation

A queue with no ceiling Tasks accumulate faster than anyone can film them until the queue is abandoned

No reason attached The assignee opens a task and has to reconstruct why this person matters

With FlowRunner

Queued on a defined signal The task is created by the product event that suggests the account is worth a face

Backlog checked before adding The flow reads the existing queue before deciding whether another task helps

Context travels with the task The note explains what the account did, so filming starts with something to say

Use Case Scenarios

A welcome video that is earned rather than automatic

A trial signup on its own is not a reason to film. A trial account that invited two colleagues, connected a data source and ran something real is a different proposition. The agent watches for that combination in the product and in HubSpot, then calls Create Greet against the account owner with a note that names what the team actually did. Before creating it, the agent calls List Greets To Do and reads the owner's existing backlog, because a video queued behind thirty others is not a welcome, it is a chore with a name on it.

Rebalancing a queue when someone is away

A colleague goes on leave with recording tasks outstanding. Rather than letting the queue age, the agent calls List Greets filtered by assignee, calls Reassign Greets to move the batch to a covering colleague or a different workspace, and posts a summary to the team channel in Slack. Reassign Greets expects the numeric workspace ID rather than the UUID the greet actions take, which the connector handles. Anything whose moment has genuinely passed, such as a trial that converted before anyone filmed, is withdrawn with Delete Greet instead of being moved, because handing a colleague a stale task is worse than handing them nothing.

Picking up the conversation a video started

Bonjoro publishes no outbound webhooks at all, so delivery outcomes are read rather than pushed. A scheduled flow calls List Transmissions for sends, deliveries, opens, clicks, bounces and unsubscribes, and calls List Replies for the messages contacts sent back. When a contact replies to a video, that reply is a person raising their hand, and the agent routes it to the account owner with the original greet and the contact profile attached. Get Greet Results and Get Greet Result Stats close the loop at the campaign level, showing which videos were watched and replied to without anyone assembling a report by hand.

Human-in-Loop Highlight

The gate on this connector is not about something irreversible reaching a customer. Nothing the agent does here reaches anyone: only a colleague pressing record does that. The gate is on the queue itself, because human attention is the scarce resource in this workflow and Create Greets In Bulk can consume a week of it in one call, with up to 200 profiles attachable to a single greet. So the agent counts before it adds. It calls List Greets To Do, and when the backlog is already beyond what the assignee can clear, it stops and asks rather than piling on: "Priya has 14 greets outstanding, the oldest from 6 days ago, and 9 more accounts crossed the activation threshold overnight. Add all 9 to her queue, reassign the backlog across the team, or hold the new ones for tomorrow?" The team lead answers. That question exists because a recording queue nobody can clear is worse than no queue at all: it turns a personal gesture into a backlog, and the accounts at the bottom get a video three weeks after the moment that earned it, if they get one at all. An agent that keeps creating tasks regardless is not automating the work, it is moving the pile.

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

18 actions

Greets

Create Greet Creates a greet, which is a task asking a team member to record a personal video for one or more contacts. Up to 200 profiles can be attached to a single greet by email address or profile ID. The note is what tells the assignee why the video is being recorded.
Create Greets In Bulk Creates many greets in a single call from a list of contacts, each with their own name and reason. Far more efficient than looping Create Greet when seeding a day of recording tasks from a CRM export, and correspondingly worth checking capacity before calling.
List Greets Retrieves video tasks with their status, assignee, contact profiles and recording links. Filter by status, assignee or contact, search across names and emails, and order by when a greet was created, updated, uploaded or last replied to.
List Greets To Do Retrieves the greets still waiting to be recorded, which is the working queue a team member sees when they open Bonjoro. This is how a flow reads capacity before adding to it.
Reassign Greets Moves a batch of greets to a different assignee or workspace in one call. Used to redistribute a queue when someone is away or to rebalance recording load across a team. Expects the numeric workspace ID rather than the UUID the greet actions take.
Delete Greet Removes a greet from the queue. Used to withdraw a task that is no longer relevant, for example when a trial user converts before anyone films for them.

Results and Replies

Get Greet Results Retrieves greets that have been sent together with their engagement outcome, so a flow can see which videos were watched and replied to.
Get Greet Result Stats Returns aggregate figures across sent greets. Used for a periodic summary of how personal video is performing rather than per-greet detail.
List Transmissions Retrieves email delivery events for sent videos, covering sends, deliveries, opens, clicks, bounces, complaints and unsubscribes. Bonjoro has no outbound webhooks, so this is how delivery outcomes are read.
List Replies Retrieves the replies a contact has sent back in response to a video, so a conversation a video started can be picked up elsewhere. Both the greet and the contact profile must be supplied.

Contacts

List Profiles Retrieves the contact profiles known to Bonjoro with their names, emails and enrichment data such as job title and location. Used to reconcile Bonjoro contacts against your own CRM.
Create Profile Adds a contact to Bonjoro so greets can be created for them later. Creating profiles ahead of time keeps the recording queue tidy when contacts arrive from several systems.
Update Profile Updates a contact's email or name, keeping it in step with your CRM so personal videos address people correctly.

Workspaces and Team

List Workspaces Retrieves the workspaces on the account with their type, goal and privacy setting. Bonjoro's API calls workspaces campaigns, and the IDs returned here are what the greet operations expect.
Update Workspace Renames a workspace or changes its purpose, goal or privacy. Workspace type describes what the videos are for, which drives Bonjoro's own reporting groupings.
List Users Retrieves the team members on the account with their names, bios and avatars. User IDs from here are what the greet assignment operations expect.
Invite Team Member Invites a colleague as either an admin or a filmer. Filmers can record and send videos, admins can additionally manage the account. Used to keep Bonjoro access in step with your own onboarding process.
List Teams Retrieves the teams on the account with their landing page settings and owner. Team IDs from here are what Invite Team Member expects.

Triggers

1 triggers

Event Triggers

On New Greet Fires when a new video task appears in Bonjoro, delivering the greet with its contact profiles, note and assignee. Bonjoro publishes no webhook API, so this trigger polls the greets endpoint and compares against the previous cycle, with a configurable interval down to 30 seconds. Used to mirror the recording queue into a task system, or to nudge an assignee the moment work lands on them.

Frequently Asked Questions

What can FlowRunner do with Bonjoro?

FlowRunner agents can run Create Greet, Create Greets In Bulk, and List Greets in Bonjoro, plus 15 more actions.

Does connecting Bonjoro to FlowRunner require OAuth?

Yes. Bonjoro connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Bonjoro trigger a FlowRunner workflow automatically?

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

Start building with Bonjoro

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

Start Building Free Talk to us