Credentials and security

Credentials can be stored as Anthropic or OpenAI API keys, HTTP bearer tokens, or custom HTTP header values. Today, agent nodes use Anthropic credentials to call Claude.

Secrets are encrypted at rest with Fernet and write-only: once saved, the API never returns them to the browser. Credentials belong to one account and are only readable by that account's runs.

Runs store every node's resolved input so you can debug them, but known secret values are redacted before anything is written.

HTTP Request nodes refuse private, loopback and link-local addresses, and non-HTTP schemes, so a workflow cannot be used to probe the network it runs in. Self-hosters can allow private addresses with ALLOW_PRIVATE_NETWORK.

Templates and expressions run in a sandboxed Jinja environment with strict undefined values, so a template cannot reach Python internals, and a misspelled field fails loudly instead of rendering empty.

Accounts are managed by Supabase Auth. The API verifies each request's access token against the project's public signing keys. See the Privacy Policy for what is stored.