Skip to main content
Providers are the external services Fluents.ai connects to so your agents can:
  • Make and receive phone calls
  • Use different TTS / STT / LLM engines
  • Send emails or calendar invites
  • Sync data with your CRM or other workflows
Instead of hard‑coding credentials in many places, you add account connections once in Providers, then reuse them across agents, numbers, actions, and workflows.

​
Video: Providers

​
Providers page overview

Go to Providers in the left sidebar to see all account connections for your workspace. For each row you’ll typically see:
  • ID – Internal identifier of the account connection.
  • Provider – The external service (for example, Twilio, Telnyx, OpenAI, ElevenLabs, HubSpot, Gmail, Outlook, Cal.com).
  • Type – What this account is used for, such as:
    • Voice (TTS / STT / LLM)
    • Telephony
    • Workflow / CRM / Email / Calendar
    • Auth
  • Provider Info – Key details like masked API keys or connection status.
  • Actions – A menu with Edit and Delete.
On the top‑right you’ll see an Add Account button for creating new connections.

​
Types of providers

Fluents.ai supports several categories of providers. The exact list you see may evolve over time, but common types include:

​
Voice and AI providers

Used to power:
  • Text‑to‑speech (TTS) voices
  • Speech‑to‑text (STT) transcription
  • Large language models (LLMs)
Examples include:
  • ElevenLabs, Cartesia (voices)
  • OpenAI and other LLM / STT providers
You connect these once in Providers, then select them when configuring Voices or advanced agent settings.

​
Telephony providers

Used to:
  • Buy or link phone numbers
  • Make and receive phone calls
  • Control caller ID and call routing
Examples include:
  • Twilio
  • Telnyx
  • Other carrier or telephony partners
You connect telephony accounts here, then use them on the Numbers page and in calling features.

​
Workflow, CRM, and communication providers

Used when you want your agents or post‑call workflows to:
  • Create or update CRM records
  • Schedule meetings
  • Send emails
  • Sync data to external systems
Examples include:
  • HubSpot and other CRMs
  • Cal.com (for scheduling)
  • Gmail, Microsoft Outlook (for email and calendar)
  • GoHighLevel and other marketing platforms
These are typically used by Actions or post‑call workflows to “push” data out of Fluents.ai.

​
Auth / generic API providers

Some provider entries are used purely for authentication, not for a specific product integration. A common example is an API Key Auth provider, which you can attach to Custom External Actions when calling your own APIs. This lets you:
  • Store an API key or token once in Providers
  • Reuse it safely across multiple actions
  • Rotate or remove it centrally without editing each action

​
Add a new provider account

To add a new account connection:
  1. Go to Providers in the left sidebar.
  2. Click Add Account (top‑right).
  3. In the New Account Connection modal:
    • Open the Provider dropdown.
    • Choose the service you want to connect (for example, Twilio, Telnyx, OpenAI, ElevenLabs, HubSpot, Gmail, Outlook, Cal.com, etc.).
  4. Fill in the required fields for that provider.
    These vary by provider but typically include one or more of:
    • API key or access token
    • Client ID and Client Secret
    • Account or project identifiers
  5. (Optional) If the provider supports OAuth or a “Connect” flow, follow the on‑screen steps to sign in and authorize Fluents.ai.
  6. Click Add Account.
The new connection will appear in the Providers list and can immediately be used elsewhere in the platform. If you’re unsure how to obtain credentials for a specific provider, refer to that provider’s own documentation (for example, “Create API keys in Twilio”) or click any contextual help links in the Fluents UI.

​
Using providers across Fluents.ai

Once configured, providers are reused in several parts of the product:
  • Voices
    Choose which TTS / STT / LLM provider powers each voice or agent configuration.
  • Numbers and Calls
    Select which telephony provider account is used for buying, linking, and using phone numbers.
  • Actions and Workflows
    Use CRM, scheduling, email, and other workflow providers in:
    • Custom External Actions
    • Post‑call workflows
    • Integrations like “send an email,” “create a CRM record,” or “schedule a meeting.”
  • Auth for your own APIs
    Attach Auth‑type providers (for example, an API Key Auth connection) to your own HTTP actions so the platform sends the right headers and credentials automatically.
Because everything points back to Providers, you can change or rotate credentials in one place and have dependent features pick up the new configuration.

​
Edit or delete a provider account

Each row in the Providers list has an actions menu with:
  • Edit
    Update credentials or settings for that provider account.     Use this when:
    • An API key was rotated or expired.
    • You want to switch a connection to a different project or sub‑account.
    • The provider asked you to update credentials for security reasons.
  • Delete
    Remove the provider account connection from your workspace.     Use this with care:
    • Any Voices, Numbers, or Actions that depend on this provider may stop working until they are reconfigured.
    • Make sure you update or remove any dependent configurations first.
If you’re not sure who uses a provider, coordinate with your team before deleting it.

​
Security best practices

When working with providers and API keys:
  • Treat credentials as secrets
    Only paste API keys or tokens into the Providers UI, not into prompts or notes.
    Never share them in screenshots or public channels.
  • Use least privilege
    Create API users or keys that have only the permissions required for your use case (for example, a “call‑only” telephony key or a CRM key limited to the needed objects).
  • Separate environments
    Use different provider accounts or keys for testing and production where possible.
    This prevents test traffic from polluting real CRMs or billing.
  • Rotate keys periodically
    Follow the provider’s rotation recommendations.
    When rotating, use Edit on the provider connection to update keys without changing references elsewhere.
If you suspect a key is compromised, immediately rotate it at the provider and then update or delete the corresponding entry in Providers.

​
Where to go next