Integrations
Connecting third-party services and external APIs to EzFlow workflows.
Integrations are encrypted credential records for third-party services. Each integration stores an access token, an optional secret, and optional non-secret configuration. Credentials are encrypted at rest with AES-256-GCM and decrypted only at Workflow execution time — they never appear in node configurations or run logs.
What an Integration stores
| Field | What it is |
|---|---|
name | A human-readable label for the integration |
provider | A string identifying the service (e.g. openai, aws-ses, twilio) |
accessToken | The primary credential — encrypted at rest |
secretToken | An optional secondary credential (e.g. an API secret key) — encrypted at rest |
config | Non-secret configuration (e.g. region, host, domain) — stored in plain JSON |
Adding an integration
- Go to Integrations (
/integrations). - Click New integration.
- Enter a name, set the provider string, paste the access token, and add any optional fields.
- Save. EzFlow encrypts the tokens immediately.
Using an integration in a Workflow
There are two ways to reference an integration at run time:
Configure directly on a node — Nodes like LLM_COMPLETION accept an integrationId field. Select the integration from the dropdown when you configure the node. EzFlow resolves and decrypts the credential at execution time.
Wire via the INTEGRATION node — The INTEGRATION node surfaces a stored integration's id and provider as output values. Wire those outputs into downstream nodes when you need to select an integration dynamically rather than statically in node configuration.
Related
- INTEGRATION — surfaces a credential reference as node outputs
- LLM_COMPLETION — uses an integration to call an LLM provider
- LLM API keys — how to add an OpenAI, Anthropic, or Gemini key
- WhatsApp providers — WhatsApp-specific credential setup