Orsay AI
AIConnect AI agents to Orsay AI, an AI lead capture platform that runs outreach and replies across social channels. Agents create and activate sequences, read the AI profiles and agents behind them, and read the conversations those agents held with prospects.
What This Integration Enables
Orsay AI runs AI-driven outreach and replies on Instagram and WhatsApp, and this connector is deliberately not a messaging API. There is no send action. What it gives a flow is a control plane over sequences and a read tap on the conversations those sequences produced. Create Sequence, Update Sequence, Get Sequence, List Sequences, and Delete Sequence cover the full lifecycle of the thing that does the talking. List Conversations and Get Conversation Messages let a flow read what happened afterwards, filtered by the classifications Orsay assigns: Positive, Negative, Undetermined, and Engaged.
That shape has a consequence worth designing around. Because the connector configures the sequence rather than sending each message, the review moment is at publication, not at send time. A sequence is defined as an ordered array of step objects, each carrying a delay, a delay unit of Seconds, Minutes or Hours, an array of follow-up delays, content, an optional template identifier, and an action. Once it is live, the AI conducts the conversations on its own. The Orsay trigger types that start a sequence, meaning Instagram Message, Instagram Comment, Instagram Story Reply, WhatsApp Message, Contact Created, and Contact Subscribed To Sequence, are configuration values on the sequence itself. They are events inside Orsay AI. They do not reach FlowRunner and they are not FlowRunner triggers.
The read side is narrower than the vendor's product surface, and honesty about that is useful. List Agents and List Profiles are read-only: this connector inspects which AI agents exist and which social profiles are connected, but it does not create or configure them. Sequence writes are the only writes. Update Sequence changes only the fields supplied and leaves everything else untouched, which makes it the natural way to flip a live sequence on or off without rebuilding it. Delete Sequence cannot be undone. Conversation paging is cursor based, returning a next cursor to pass as the Last Lead ID of the following call, with a page size that defaults to 20 and caps at 50. The organisation is limited to 200 requests per hour, so a full history export is a paced job rather than a single sweep.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A campaign that switches itself off
An outbound team runs seasonal promotions on Instagram, and the failure mode is never the launch, it is the sequence still replying to people three weeks after the offer expired. A flow owns both ends. On the approved start date the agent calls Create Sequence with the reviewed step list and the Instagram Message trigger type. On the end date, or when a budget threshold is crossed in the finance system, the same flow calls Update Sequence to deactivate it, changing only that field and leaving the content and step timings intact so the sequence can be reactivated next season without being rebuilt. Delete Sequence is reserved for sequences that will genuinely never run again, because it cannot be undone.
Getting the transcript to the person who has to make the call
Orsay classifies conversations, and Positive is the classification that costs money to ignore. A flow polls List Conversations filtered to Positive, using the returned next cursor as the Last Lead ID on the next call and stopping when the cursor comes back null. For each new lead it calls Get Conversation Messages to pull the full exchange, then writes the lead and the transcript into Google Sheets and posts a summary to the sales channel in Slack so a human can take over the thread inside Instagram or WhatsApp. The AI opened the conversation. A person closes it, and they arrive already knowing what was said.
One qualified lead, three systems, no copy and paste
Engaged conversations are a different signal from Positive ones: interest without commitment. A nightly flow lists them, pulls each message history, and enriches the record before anyone sees it. Qualified leads are created as contacts in Brevo for nurture email, and the ones that match an existing account are attached to the account record in HubSpot with the transcript in the note field. Because the organisation rate limit is 200 requests per hour and a 429 comes back with a Retry-After header in seconds, the flow paces itself rather than racing through the backlog and getting throttled halfway.
Human-in-Loop Highlight
The gate here is unusual, and the reason is a missing capability rather than a dangerous one. Most outreach connectors let a flow send one message at a time, which means the review can sit on the message. This one does not. Create Sequence publishes an autonomous AI conversationalist that will speak first, to real people, on Instagram or WhatsApp, in your brand's name, and then keep talking as they reply. There is no send action to intercept, no per-message queue to inspect, and no action anywhere in this connector that stops a conversation already in progress. The only lever left after publication is Update Sequence to deactivate, and deactivating does not unsay a word that has already landed in someone's direct messages. So the review has to happen at the only moment it can: before Create Sequence runs. The agent does the assembly, reading the connected accounts through List Profiles, checking List Sequences for an overlapping campaign already targeting the same audience, and laying out the ordered steps with each delay and follow-up delay resolved into real elapsed time. Then it stops: "Sequence ready for the @brand Instagram profile, triggered on Instagram Message. Step 1 sends immediately, step 2 after 45 minutes, step 3 after 6 hours, with two follow-ups. Full text below. Publish?" That is the digital andon cord applied to outbound: the agent has assembled everything and stopped the line at the one point where a person still has a decision to make.
Agent Capabilities
9 actionsSequences
5- List Sequences Lists the sequences in the organisation. The first call in any flow that touches sequences, because it is how an agent finds out whether a live campaign already targets the audience it is about to target.
- Get Sequence Retrieves one sequence with its ordered flow steps, delays, content, and trigger type. Used to read a live campaign's configuration before changing it or cloning it into a new one.
- Create Sequence Creates a new sequence from an ordered array of step objects, each supporting a delay, a delay unit, follow-up delays, content, a template identifier, and an action, together with the Orsay trigger type that starts it. This is the action that puts an AI in front of real prospects, and the one worth gating.
- Update Sequence Changes only the fields supplied and leaves all others untouched. The right way to activate, deactivate, rename, or reassign a sequence without rebuilding its content, and the fastest way for a flow to stop a campaign when a budget or an end date says so.
- Delete Sequence Permanently removes a sequence. This cannot be undone, so a flow that only needs a campaign to stop should deactivate through Update Sequence instead.
Conversations
2- List Conversations Lists conversations with filters including the Orsay classification values Positive, Negative, Undetermined, and Engaged, plus a since filter for incremental polling. Returns a next cursor to pass as the Last Lead ID of the following call, with a page size that defaults to 20 and caps at 50. This is the polling surface that stands in for the triggers this connector does not have.
- Get Conversation Messages Retrieves the full message history of one conversation. Used to hand a human the entire exchange before they pick up the thread, and to attach the transcript to a CRM record.
Account
2- List Agents Lists the AI agents configured in the Orsay AI account. Read only: this connector inspects agents, it does not create or configure them.
- List Profiles Lists the connected Instagram and WhatsApp profiles a sequence can send from. Read only, and worth calling before creating a sequence so the flow knows which brand identity the messages will carry.
Frequently Asked Questions
What can FlowRunner do with Orsay AI?
FlowRunner agents can run List Agents, List Profiles, and List Sequences in Orsay AI, plus 6 more actions.
Does connecting Orsay AI to FlowRunner require OAuth?
No. Orsay AI connects to FlowRunner with an API key, no OAuth flow required.
Can Orsay AI trigger a FlowRunner workflow automatically?
Orsay AI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Orsay AI
$100 in credits. No card required. Connect in minutes.