Vaimero
SchedulingConnect AI agents to Vaimero, an AI meeting booker that contacts warm leads over email, SMS, voice, or webhook until a meeting is set. Agents pick up the booked meeting and prepare whoever is taking it.
What This Integration Enables
Vaimero's unit of work is not a lead and not a message. It is an operation: one outreach attempt against one person, with a status that moves through pending, active, confirmed, booked, booking_not_required, aborted, expired, booking_failed or pass_through. That framing is what separates it from the rest of this category. A scheduler gives you a slot. An appointment setter in a DM gives you a thread. Vaimero gives you a process that keeps going over email, SMS, voice or webhook until it reaches one of those terminal states, and then hands back everything it learned on the way: the plain and formatted conversation summaries, the message log, the event log of state changes, and the booking with its assigned team member and external calendar event ID.
That makes Vaimero a natural fit for the follow-up nobody has time to do properly. A demo request from six weeks ago, a trial that lapsed, a renewal conversation that stalled. For a FlowRunner agent the interesting part is the deduplication contract: supply externalSource and externalId on Create Lead, and repeated calls inside the deduplication window return the existing live operation instead of contacting the person again. A CRM that fires the same webhook twice does not become two phone calls. The connectors do the reaching out, the chasing and the recording. The decision about who gets reached out to, on which channel, and at what hour of their day stays with a person, because that is the part that cannot be taken back.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Reviving a stalled pipeline segment
Opportunities in Salesforce that have sat in the same stage past a threshold get pulled into a re-engagement batch. The agent reads each record's contact details, preferred language and channel, sets externalSource to the CRM and externalId to the opportunity ID so a re-run cannot double contact anyone, and calls Bulk Import Leads with up to fifty per batch. Each lead is validated independently, so one bad phone number does not block the rest of the batch. On Operation Status Changed writes every state transition back to the opportunity, so a rep opening the record sees active, aborted or booked rather than a silent gap.
The booked meeting that briefs its own attendee
On Booking Created fires the moment an operation books. The event carries the client name, phone and email, the plain and formatted conversation summaries, the start and end times, the assigned team member, the meeting channel and the external calendar event ID. The agent creates or updates the contact and deal in HubSpot, attaches the formatted summary to the record, and posts a briefing to the assigned rep in Slack with the summary and a link to the calendar event. If more detail is wanted, Get Operation Messages returns the actual conversation the bot had, so the rep can see the objection that was raised before they hear it again live.
Auditing what the bot said
Once a week the agent runs List Operations across the period and buckets them by status. Booked and confirmed go into a Google Sheets tab with their source, so the team can see which operation sources produce meetings. For aborted, expired and booking_failed operations the agent pulls Get Operation Events to see where the sequence stopped, and samples Get Operation Messages on a handful to read what the conversation actually looked like. Webhook delivery gets the same treatment: List Webhook Notifications shows deliveries a receiving endpoint did not acknowledge, and Replay Webhook Notification re-sends them once the endpoint is fixed, so a broken listener does not turn into a week of missing bookings.
Human-in-Loop Highlight
Bulk Import Leads accepts fifty leads in one call, and every one of them is created with initiation type Handled, which means the bot drives the outreach itself. One API call, fifty real people about to receive an email, a text or a phone call from an automated caller. The reason this needs a gate rather than a guardrail is what the connector does not contain: there is no action here that stops an operation in flight. The status vocabulary includes aborted, but the operation surface exposed to a flow is read-only. Delete Lead soft-deletes the lead record and can anonymize it immediately, and that is a data action, not a recall. A voice call that has been placed has been placed.
The second half of the same decision is when. Create Lead takes a schedule window, and a window computed in the account's timezone rather than the lead's is how an outbound program ends up dialling people at half past six in the morning. So before any batch goes out, the agent stops and asks the revenue owner in their channel: "Re-engagement batch ready: 47 leads from the Q1 stalled-demo segment, channel voice for 31 and email for 16, schedule window 09:00 to 17:00 resolved per lead timezone, meetings routed to Dana. Nothing here can be stopped once it starts and there is no cancel operation. Reply go, or name the leads to drop." The other half of the gate is capacity, because a booker that works until it succeeds will fill a calendar it cannot see. The owner confirms the assigned team member can carry the volume before the batch runs, not after four meetings land on the same Thursday. Agents can chase indefinitely and never get tired. Deciding who gets chased, on which channel, and at what hour is a judgment, and FlowRunner treats it as one.
Agent Capabilities
17 actionsLeads
5- Create Lead Creates a lead and starts an outreach operation, with the bot contacting the client on the chosen communication channel and working to book a meeting. Initiation type Handled lets the bot drive the outreach, and Delegated hands the conversation over with initial messages. Supplying both externalSource and externalId makes repeated calls inside the deduplication window return the existing live operation instead of contacting the person again.
- Bulk Import Leads Imports up to fifty leads in a single batch, each validated and processed on its own so one failure does not block the rest. All imported leads are created with initiation type Handled, which means this single call puts every lead in the batch into live outreach.
- List Leads Returns a paginated list of leads with contact name, language, communication email and phone, source and timestamps. Used for reconciliation against the CRM segment that produced them.
- Get Lead Retrieves a single lead by ID with its detailed information, including contact details, language, source and timestamps. Used when a flow has a lead reference from an event and needs the full record.
- Delete Lead Soft-deletes a lead by ID, with an Anonymize option that immediately anonymizes the lead and its related data rather than waiting for the account retention period. Used for erasure requests and list hygiene, and worth understanding as a data action rather than a way to call off outreach.
Operations
7- List Operations Returns a paginated list of operations, each carrying a status such as pending, active, confirmed, booked, aborted or expired, plus its source, context and tags. This is the reporting spine: booked against attempted, sliced by source.
- Get Operation Retrieves a single operation by ID with its status, type, source, context and tags. Used to check the current state of a specific outreach before a flow acts on it.
- List Operation Sources Returns the operation sources configured on the account. Source values label leads on creation and are what makes per source reporting meaningful later, so a flow should set them deliberately.
- Get Operation Events Returns the event log for an operation, showing the sequence of state changes and actions recorded while the bot worked the lead. Used to find where an aborted or expired operation actually stopped.
- Get Operation Messages Returns the conversation messages exchanged during an operation, each with its role, raw and structured content, message parts, and whether it originated in the conversation or was delegated. This is how a rep sees the objection before the call rather than during it.
- Get Operation Message Retrieves a single message from an operation conversation by its message ID, including the role, raw content and message parts. Used when an event references one message and the flow needs only that.
- Get Operation Booking Returns the booking created by an operation, including the scheduled start and end, the assigned team member, the meeting channel and the external calendar event ID when one exists. Used to reconcile a booking against the calendar it was written to.
Account and Webhooks
5- Get Account Returns the customer account the API key belongs to, including its configured settings. Used to confirm which account a key is scoped to before anything else runs against it.
- List Webhooks Returns a paginated list of the webhook subscriptions registered on the account, including those created by FlowRunner triggers. Used to audit what is currently listening.
- Get Webhook Retrieves a single webhook subscription by ID, including its target URL, name, description and subscribed events.
- List Webhook Notifications Returns the delivery notifications recorded for webhook subscriptions, scoped to one subscription or across all of them. Used to diagnose deliveries a receiving endpoint did not acknowledge, which is usually the real reason a booking never appeared downstream.
- Replay Webhook Notification Re-sends a previously generated webhook notification to the subscription's target URL. Used to redeliver events after fixing an endpoint that rejected or missed the original call, so a broken listener costs a replay rather than a week of lost bookings.
Triggers
4 triggersEvent Triggers
4- On Booking Created Fires when a meeting is booked for a lead, carrying the operation ID and status, the client name, phone and email, the plain and formatted conversation summaries, the booking start and end dates, the assigned team member, the meeting channel and the external calendar event ID. This is the trigger that turns a booked meeting into a briefed rep.
- On Message Created Fires each time a message is added to a conversation, by either the bot or the client, carrying the message content along with the lead and operation it belongs to. Used to mirror a live conversation into a CRM timeline, or to watch for a phrase that should pull a human in immediately.
- On Operation Created Fires when a new outreach operation is started for a lead, which happens as soon as a lead is created or re-engaged. Used to record on the CRM object that outreach is now live, so nobody sends a competing email while the bot is mid-conversation.
- On Operation Status Changed Fires whenever an operation moves to a new status, carrying the new status, the client details, the conversation summaries, the custom data and the tags. This is the workhorse: it keeps the CRM's view of an outreach attempt in step with reality without anyone polling for it.
Frequently Asked Questions
What can FlowRunner do with Vaimero?
FlowRunner agents can run Create Lead, Bulk Import Leads, and List Leads in Vaimero, plus 14 more actions.
Does connecting Vaimero to FlowRunner require OAuth?
No. Vaimero connects to FlowRunner with an API key, no OAuth flow required.
Can Vaimero trigger a FlowRunner workflow automatically?
Yes. Vaimero supports 4 triggers that can start a FlowRunner workflow automatically.
Start building with Vaimero
$100 in credits. No card required. Connect in minutes.