Olark
CommunicationKeep Olark live chat staffed correctly: agents provision and update chat operators, remove departing ones, and manage group membership so incoming conversations route to the right team.
What This Integration Enables
Live chat staffing is an access-control problem wearing a support hat. Who can take chats, which queues they sit in, and when their access ends: that is identity lifecycle work, and Olark's agent and group model is where it lives for chat. This connector lets FlowRunner agents run that lifecycle from the systems that already know the truth, the HR platform, the CRM, the org chart, so Olark's roster stops being a thing someone remembers to update. - Provision an operator when a new teammate appears in the HR or identity system, and route them to the right group - Keep queue routing synced as roles change, adding and removing group membership by rule - Offboard departing staff completely: out of every group, account deleted, access revoked - Audit agents and groups on a schedule, pushing the roster to a reporting sheet - Reset credentials and update names and emails programmatically Deletion is permanent, which is why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration puts a person in front of it every time. The reason to automate this at all is that chat access reviews fail quietly. Nobody notices the operator who left in March still has a login until an audit, or an incident, makes it everyone's problem. Wiring Olark's roster to the systems that know who works here, and on what team, turns access from a checklist item into a property the flow maintains: joiners provisioned, movers rerouted, leavers deleted, and the evidence in the log. It is unglamorous automation with an outsized compliance payoff, which is usually the kind worth building first.
Without FlowRunner
With FlowRunner
Use Case Scenarios
New hire, chat-ready before the first standup
An onboarding event for a new support hire fires from the HR workflow. The agent calls Create Agent with their email, a generated password, and display name, then List Groups to find the Support queue and Add Agent to Group to route them in. A welcome message with login instructions posts to [Slack](/integrations/slack). The new teammate takes their first chat on day one instead of day four.
The roster audit that runs itself
Weekly, List Agents and List Groups pull the full roster and its group structure into [Google Sheets](/integrations/google-sheets): every operator, every queue they route into, every group's membership. The agent diffs against the HR system's active-employee list and flags mismatches, an operator with no matching employee, an employee in the wrong queue. Access review stops being a quarterly scramble and becomes a standing report with exceptions called out.
Role changes propagate to the queue
When account ownership shifts in [HubSpot](/integrations/hubspot), the agent updates chat routing to match: Remove Agent from Group takes the former owner out of that team's queue, Add Agent to Group routes the new owner in, and the change posts to the operations channel. Chats about an account land with the person who actually owns it, and the routing table never quietly diverges from the CRM.
Human-in-Loop Highlight
Delete Agent permanently removes an operator: access revoked, every group membership gone, and the catalog is explicit that it cannot be undone. The dangerous part is how reasonable it always looks, offboarding flows run on names and emails, and support teams accumulate similar names, shared inboxes, and rehires. Delete the wrong operator and a working teammate is locked out mid-shift with their queue routing erased. So FlowRunner agents stage the evidence before the act: Get Agent pulls the exact profile, List Groups shows which queues lose a member, and the support manager confirms the person and that their active conversations are handed off. Only then do Remove Agent from Group and Delete Agent execute, in that order, with the record logged. Revoking access should be fast. It should never be unsupervised, and with the evidence staged in advance, it does not have to choose between the two.
Agent Capabilities
8 actionsOperators
5- List Agents Lists every operator on the account with name, email, and ID. The resolution step behind provisioning, audits, and offboarding.
- Get Agent Retrieves one operator's full profile by ID: name, email, nickname, enabled status. The identity check before any destructive action.
- Create Agent Creates an operator with email, password, and display name, ready for immediate group assignment. The provisioning write.
- Update Agent Updates an operator's fields by ID, changing only what you provide. The maintenance write for renames, email changes, and password resets.
- Delete Agent Permanently removes an operator, revoking access and clearing all group membership. Cannot be undone. The operation this page's human gate exists for.
Groups and Routing
3- List Groups Lists every group with name and ID. The map of the routing structure.
- Add Agent to Group Adds an operator to a group, routing them into that team's chat queue. The step that turns an account into a working teammate.
- Remove Agent from Group Takes an operator out of a group's queue without deleting their account. The routing change for role moves and the first step of every offboarding.
Frequently Asked Questions
What can FlowRunner do with Olark?
FlowRunner agents can run List Agents, Get Agent, and Create Agent in Olark, plus 5 more actions.
Does connecting Olark to FlowRunner require OAuth?
No. Olark connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Olark trigger a FlowRunner workflow automatically?
Olark doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Olark
$100 in credits. No card required. Connect in minutes.