--- title: "Kixie Integration" description: "Put Kixie's sales dialer to work in your flows. Agents trigger click-to-call from a rep's line the moment a lead arrives, queue calls into PowerLists, and send personal or shared-number SMS follow-ups after forms, purchases, or bookings." url: https://flowrunner.ai/integrations/kixie date_modified: 2026-08-04T10:04:16-07:00 --- # Kixie [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Put Kixie's sales dialer to work in your flows. Agents trigger click-to-call from a rep's line the moment a lead arrives, queue calls into PowerLists, and send personal or shared-number SMS follow-ups after forms, purchases, or bookings. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 4 actions · API key · available [Kixie website](https://kixie.com/) · [Platform Documentation](https://developer.kixie.com/) · Capability data verified 2026-07-27 1. A new inbound lead submits the demo request form 2. Agent enriches the lead and resolves the assigned rep by territory from the CRM 3. Lead score and business hours decide the play, immediate call or SMS-first touch 4. Make Call rings the assigned rep's Kixie device, then dials the prospect the moment the rep answers 5. The rep runs the conversation, the part of the workflow that was always meant to be human 6. If the call goes unanswered, Send SMS follows up from the same rep's line with a scheduling link 7. The touch sequence and outcome log to the CRM and the sales channel ## What This Integration Enables Kixie's premise is that sales calls should start with one click; FlowRunner's is that they should start with zero. The connector wires Kixie's PowerCall and SMS Business API into workflows so that the events that justify a call, a demo request, a booked meeting, a hot signup, place the call themselves: the rep's device rings, then the prospect's. This is the rare integration where the human is not a gate bolted onto the automation, the human is the payload. Everything around the conversation is machinery; the conversation is the product. What the orchestration layer adds: - Speed-to-lead becomes structural, because the call is triggered by the lead event, not by queue-checking - Missed calls degrade gracefully into SMS from the same rep's line, keeping the thread personal - PowerLists fill from CRM segments and spreadsheets, so prioritization logic lives in the workflow, not in a rep's head - Team SMS from a shared number handles the operational traffic, reminders and confirmations, that should not consume a personal thread - Every touch is logged back to the systems where pipeline reporting actually happens The scarce resources here are rep hours and prospect goodwill, and FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline protects both: single-lead plays run autonomously, list-scale plays get approved by a person first. ### Without FlowRunner **Speed-to-lead is a leaderboard fiction**: The form fires, the lead sits in a queue, and the first call happens when a rep next checks the list **Follow-up texts depend on rep discipline**: Some reps text after every missed call, some never, and nobody can see the difference **Call lists are built by hand**: Someone exports a segment, sorts it in a spreadsheet, and reads numbers to the team ### With FlowRunner **The phone rings while interest is real**: A form submission becomes a live rep-to-prospect call in the time it takes the rep to pick up **Every missed call has an automatic next touch**: The SMS follows from the rep's own number, so the reply lands where the relationship lives **PowerLists load themselves**: Agents queue prioritized calls from CRM segments, and reps just work the list ## Use Case Scenarios ### The demo request that gets a ringing phone A lead lands in [HubSpot](https://flowrunner.ai/integrations/hubspot) from the pricing page. The agent scores it, resolves the territory owner, and fires Make Call: the rep's browser extension rings, they answer, and Kixie dials the prospect while the form submission is still warm. If the prospect does not pick up, Send SMS follows from the rep's line: a short intro and a booking link. The workflow codifies the play every sales leader preaches and few teams execute, because execution used to depend on someone watching a queue. ### The PowerList that builds itself overnight Each evening the agent pulls tomorrow's call-down segment, renewal risks, trial expiries, re-engagement targets, from [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and the CRM. After the sales ops lead approves the list and its size, the agent walks it with Send to Queue, routing each number into the right rep's PowerList by territory. Dispatches log to [Slack](https://flowrunner.ai/integrations/slack). Reps start the morning with a full, prioritized list, and the question "who should I call today" was answered by the workflow before anyone logged in. ### Bookings confirmed by the machine, worked by the rep A [Calendly](https://flowrunner.ai/integrations/calendly) booking triggers Send SMS from the assigned rep's number: confirmation now, reminder the morning of the call. Operational reminders for group events go out via Send Team SMS from the shared number instead, keeping personal threads for personal conversations. When a prospect replies to reschedule, the thread is already with their rep. The distinction between relationship traffic and logistics traffic is enforced by which action the workflow calls, not by rep judgment under time pressure. ## Human-in-Loop Highlight Send to Queue spends the most expensive resource a sales org has: rep hours. One workflow call queues one dial, but a loop over a bad segment loads five hundred, and the team spends the day calling a list that should never have shipped, while real pipeline waits. Send Team SMS carries the parallel risk on the prospect side, a shared-number blast to a mis-built segment that no one can unsend. So FlowRunner gates both at scale: any workflow queuing beyond a handful of calls or texting beyond a single recipient presents the segment definition, the count, and a sample to the sales ops owner before dispatch. Single-lead actions, the instant call, the missed-call text, run ungated because each one is authorized by the lead's own behavior. The dialer goes fast; the decision to point the whole team at a list stays human. 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 4 actions ### Calls 2 - **Make Call** Initiates a click-to-call from a Kixie agent to a target phone number. The agent's Kixie device (browser extension, mobile, or desk phone) rings first, then dials the target once answered. Identify the agent by their Kixie login email. The target must be in E.164 format (e.g. +14155551234). Requires the Professional billing tier or higher. - **Send to Queue** Queues an outbound call for a Kixie agent to be routed through a call queue/PowerList. The agent (identified by login email) receives the queued call when available. The target must be in E.164 format. Provide the queue ID from your Kixie Dashboard. Requires the Professional billing tier or higher. ### Messaging 2 - **Send SMS** Sends a direct (personal) SMS text message to a target phone number from a Kixie agent's line. The target must be in E.164 format (e.g. +14155551234). Message length follows standard carrier SMS limits (long messages are split into segments). Requires the Professional billing tier or higher. - **Send Team SMS** Sends a Business/Team SMS from a shared Team SMS number rather than an individual agent's line. Provide the Team SMS ID from your Kixie Dashboard; optionally override the sending number with From Number (otherwise the first number attached to the Team SMS ID is used). The target must be in E.164 format. Requires the Professional billing tier or higher. ## Frequently Asked Questions ### What can FlowRunner do with Kixie? FlowRunner agents can run Make Call, Send to Queue, and Send SMS in Kixie, plus 1 more action. ### Does connecting Kixie to FlowRunner require OAuth? No. Kixie connects to FlowRunner with an API key, no OAuth flow required. ### Can Kixie trigger a FlowRunner workflow automatically? Kixie doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Kixie?** This integration exposes Kixie to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/kixie. Site index: https://flowrunner.ai/llms.txt