Brex

Expenses, cards, receipts, budgets, and payments.

You connect Brex with your Brex sign-in or an API key, and workflows can then read and update what that account can in Brex, through its API.

Use it in a workflow

Tell the architect, the AI that builds your workflows, what you want done in your own words. For example:

Each week, find Brex card expenses missing receipts and remind the cardholders.

With a sign-in, you grant access on Brex's own consent screen, and Malleable stores the resulting token, never your password.
An API key you enter never appears in chat and is hidden from the AI. A key saved as a reusable connection is stored with your Malleable account and only sent to Brex.
Every run uses the connection the workflow's owner set up, so anyone who can run the workflow acts with that account's access in Brex. Connect an account or key with only the access the workflow needs.
You can revoke access at any time in Brex's settings.

Malleable is SOC 2 Type II certified and doesn't train AI models on your data. More in Security & data handling and our Trust Center.

Connection details for IT

Workflows reach Brex through its public API, with the sign-in or API key you connect. Your Brex admin may need to turn on API access first.