Messaging & BYOK
Messaging & BYOK
Connecting your own messaging providers and API keys to EzFlow.
EzFlow is bring-your-own-keys: it does not bundle a messaging or AI provider. Instead, you connect your own provider accounts and API keys to unlock each channel. Every credential is encrypted at rest with AES-256-GCM and only decrypted at execution time — keys never enter a Workflow's DAG.
This section covers the five credential types that power EzFlow's messaging and AI nodes.
What you connect
- WhatsApp providers — Connect Twilio, Meta Cloud API, or a generic webhook to send WhatsApp messages with the SEND_WHATSAPP node. See WhatsApp providers.
- Senders — Define email sender identities (display name and address) used by the SEND_MAIL node and resolved by the SENDER node. See Senders.
- Sending domains — Verify a custom domain with DNS records to improve email deliverability and branding. See Sending domains.
- LLM API keys — Add your OpenAI, Anthropic, or Gemini API key for the LLM_COMPLETION node. See LLM API keys.
- Integrations — Store encrypted credentials for third-party services and surface them at execution time via the INTEGRATION node. See Integrations.
Related
WhatsApp providers
Connect Twilio, Meta Cloud API, or a custom webhook to send WhatsApp messages.
Senders
Define email sender identities used by the SEND_MAIL and SENDER nodes.
Sending domains
Verify a custom domain with DNS to improve email deliverability.
LLM API keys
Add your own OpenAI, Anthropic, or Gemini API key for AI nodes.
Integrations
Store and manage encrypted credentials for third-party services.