Floo APIv1

Integrations

Floo on Zapier

Connect Floo AI to 6,000+ apps with Zapier - wire call events into your CRM, fire calls from spreadsheet rows, branch on post-call extraction outcomes.

Private beta. The Floo Zapier app is currently in private beta. Email support@flooai.com with your workspace name to request access - we'll send an invite link to the unpublished app.

What you can build

  • When a Floo call ends → add lead to HubSpot

    Trigger on `call_ended`, filter on `extraction.intent = 'qualified_lead'`, then push the contact + summary into HubSpot.

  • New row in Google Sheets → start outbound Floo call

    Sales ops drops a phone number into a sheet; Zapier picks it up and fires `Create Outbound Call` with your SDR agent.

  • Stripe payment received → schedule follow-up call

    On a `charge.succeeded` event, fire a Floo outbound call to thank the customer and offer onboarding.

Triggers

Triggers fire a zap when something happens in Floo. Under the hood they use Zapier's REST hook model: Zapier subscribes once via the webhooks API, and we POST to its URL whenever the event fires.

Triggercall_endedCall Ended

Fires when a Floo call disconnects. Payload includes duration, sentiment, end reason, and a link to the recording / transcript.

Triggertranscript_turnTranscript Turn

Fires for each finalized turn during a call (one per speaker change). High volume - use only when you need real-time transcript routing.

Triggerextraction_completeExtraction Complete

Fires after the post-call LLM extraction finishes. Carries the structured `fields` object you defined on the agent (lead name, intent, summary, etc.).

Triggercall_failedCall Failed

Fires when an outbound dial cannot connect - no_answer, busy, voicemail (when AMD is on), or carrier error. Useful for retry workflows.

Actions

Actions let a zap call into Floo. All actions authenticate with a Floo API key minted from /dashboard/settings/api-keys.

Actioncreate_outbound_callCreate Outbound Call

Place an outbound call from one of your Floo agents. Takes a phone number, agent ID, and an optional `metadata` object that will be echoed back on all webhooks for the call.

Actionfind_callFind Call

Look up a single call by ID. Useful as a polling step in zaps that branch on call outcome.

Actionlist_agentsList Agents

Return all agents in the connected workspace. Used by other zap steps to populate dropdowns.

Setup

  1. Request access. Email support@flooai.com - we'll send you the unpublished Zapier app invite link.
  2. Install the Floo app on Zapier. Accept the invite from a logged-in Zapier account.
  3. Connect your workspace. Zapier will prompt for an API key. Mint one at /dashboard/settings/api-keys and paste it in.
  4. Build your zap. Pick a Floo trigger or action, map fields, and turn it on. Test events show up in real time on the Zapier task history.

For Floo team members

The Zapier CLI app definition lives in integrations/zapier/ in this repo - app.json holds the trigger/action manifest and README.md documents the publish workflow.

See also: Webhooks if you'd rather receive events directly without Zapier in the middle.