Components, not projects.
Every external capability in flow — a channel, an identity check, a fraud score, a payment, a core-system call — is a component with a contract: what it does, what agents may call it for, under which limits, and what gets logged. Install once, enable per tenant, and it's a tool every agent and every workflow can use.
Where conversations arrive and leave.
WhatsApp Business Platform
Official Cloud API or via a BSP. Templates, media, interactive buttons and lists, WhatsApp Flows, catalog and payments where available.
Voice
Inbound and outbound calls through flow's managed telephony or your carrier and PBX via SIP. Recording, transcription, IVR, voice agents.
SMS & RCS
Transactional and conversational SMS through your aggregator; RCS business messaging where the market supports it. Fallback channel for OTP and alerts.
Shared mailboxes via Google Workspace, Microsoft 365 or IMAP/SMTP. Threads matched to records; attachments into document intake.
Web & in-app chat
Embeddable widget and SDK for your site and apps, sharing identity with your logged-in session so the agent starts at the right level.
Other messaging
Telegram, Facebook Messenger and Instagram where your customers are; Apple and Google business messaging via partners.
Proving who's on the other end — at the level the request needs.
The identity agent orchestrates these. Deployments mix and match: a bank might use OTP + device for balances and a document + liveness vendor for new payees; a clinic might only need possession.
One-time passcodes
OTP over SMS, WhatsApp or voice, with rate limits and fallback. Built in.
Device & session signals
Device fingerprint, app session confirmation, SIM-swap and carrier signals via telecom data partners.
Document + liveness
ID document capture, authenticity checks and selfie liveness from IDV vendors, run inside the conversation via secure link.
Voice biometrics
Passive or active voice verification on calls, from specialist vendors, as a step-up or a primary factor for phone self-service.
Your identity provider
Customer IAM and national or bank ID schemes via OIDC — the agent sends a login link and receives the assertion.
Employee verification
Personal links with phone verification on first use and on return, for the employee desk. Built in.
Risk vendors get a vote on every action.
Fraud engines, device intelligence, behavioral biometrics and sanctions screening plug in as scoring components. The risk agent combines their signals with what it sees in the conversation itself — urgency, third-party instructions, inconsistent details — and the policy card decides what a score means for each action.
- Transaction and session scoring before any write action
- Step-up verification triggered by score
- Outbound alerts with structured confirmation; block, freeze, replace, case
- Analyst handover with the full session and the agent's reasoning
Fraud scoring engines
Transaction and account-takeover models.
Device intelligence
Fingerprint, emulator and bot detection, reputation.
Behavioral signals
Typing, navigation and conversation-pattern classifiers.
Screening
Sanctions, PEP and adverse-media checks on onboarding and payees.
Bring your carrier, or let flow be the phone system.
Managed telephony
Numbers, cloud PBX, queues, IVR and recording provided by flow, so a business has one supplier for messaging and calls.
SIP & contact-center platforms
Trunk into your existing switch or contact-center platform; flow handles the conversation layer, your platform keeps the calls.
Speech & voice agents
Real-time transcription, summarization and voice agents that verify, answer and route before a person picks up.
The transactional pieces of a conversation.
Payments & collections
Payment links, card and bank-transfer collection, direct-debit changes, installment plans — through your PSP or acquirer.
E-signature
Built-in signature with audit evidence, or qualified signature providers where regulation requires them.
Document intake & OCR
Classification and field extraction for IDs, invoices, statements, forms — built in, with specialist vendors for regulated document types.
Calendars & scheduling
Google and Microsoft calendars, clinic and field-service schedulers, resource booking.
Document storage
Your object storage or DMS as the system of record for documents; flow keeps the index and the audit.
Location & field
Technician tracking, ETA and geofencing from field-service and fleet systems for outbound updates.
The systems of record agents read from and write to.
Each connector declares read and write scopes separately. Policy cards reference those scopes, so “the agent may read balances but only propose transfers” is a configuration, not a custom build.
Core banking & cards
Accounts, transactions, transfers, card controls, disputes, limits — via your core's APIs or a solution partner's adapter.
Policy administration & claims
Policies, endorsements, claims, payouts — insurance cores and claims platforms.
OSS / BSS
Line status, diagnostics, provisioning, plans, billing — telecom and utility stacks.
ERP & accounting
Purchase orders, invoices, payments, inventory; accounting packages for professional services.
CRM & HRIS
Customer and employee records where they already live — flow syncs or federates rather than duplicating.
Clinical & practice systems
Scheduling, records and results release from health IT systems.
Your warehouse, your model contract, your knowledge.
Data warehouse export
Conversations, metrics and audit events streamed to your warehouse or lake.
Model providers
Claude from flow's cloud by default; your own Anthropic, OpenAI or other contract; private inference inside your boundary.
Knowledge sources
Policies, handbooks, product catalogs and FAQs from your intranet, DMS or CMS — indexed with source attribution.
Package your product as a component. Every agent can call it — in every tenant.
A component is a contract plus an adapter: the operations it exposes, the scopes agents need, the limits it supports, the events it emits and what gets logged. Build it once with our SDK — or describe it and let the build tooling generate the adapter against your API — and it appears in the catalog for every tenant to enable.
- Typed operations with read/write scopes, so policy cards can reference them
- Event emission into automations and the audit log
- Certification for the catalog; enablement per tenant with limits
- Usage metering and revenue share where you sell through flow
name: idv-vendor category: identity operations: - id: verify_document_liveness scope: identity.write level_granted: L3 inputs: [session_id, secure_link] outputs: [result, confidence, document_type] timeout_s: 180 events: [verification.completed, verification.failed] limits: per_customer_per_day: 3 audit: [inputs_hash, result, confidence, vendor_ref] data_residency: [eu-west, il-central] billing: per_verification
Have a product that belongs in the catalog?
Identity, fraud, telephony, payments, documents, vertical systems — talk to us about certification and distribution across the platform.