> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/brex.md).

# Brex

Manage Brex transactions, expenses, vendors, Cash transfers, and virtual cards.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Brex      | User token     |

#### Brex

Connect a scoped Brex user token to manage transactions, expenses, vendors, Cash transfers, and virtual cards.

**Set up in Brex**

1. Prepare the Brex account or service that the workflow will access. Grant access to the required resources and operations.
2. **User token:** Create a scoped user token in Brex Developer Settings. The token is shown once; grant the scopes required by the actions you enable.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Brex**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                   |
| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| User token    | Yes      | Create a scoped user token in Brex Developer Settings. The token is shown once; grant the scopes required by the actions you enable. [Provider instructions](https://developer.brex.com/guides/authentication). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Brex** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### List transactions

Retrieve recent settled transactions from the primary Brex card account.

**Required permissions:** `transactions.card.readonly`.

**Inputs**

| Field                | Type    | Required | Description                                                                  |
| -------------------- | ------- | -------- | ---------------------------------------------------------------------------- |
| Maximum transactions | integer | No       | Maximum number of settled transactions to return across pages. Default: 100. |
| Starting cursor      | string  | No       | Continue from a cursor returned by an earlier listing.                       |

**Outputs**

| Field        | Type          | Description                                                                                             |
| ------------ | ------------- | ------------------------------------------------------------------------------------------------------- |
| Transactions | object\_array | Settled card transactions with IDs, descriptions, amounts, posting dates, types, and optional card IDs. |
| Next cursor  | string        | Cursor for the next page when more transactions remain.                                                 |

#### Create cash transfer

Send a Brex Cash payment to an existing vendor payment method.

**Required permissions:** `accounts.cash.readonly`, `transfers`, `vendors.readonly`.

**Inputs**

| Field                 | Type            | Required | Description                                                                                        |
| --------------------- | --------------- | -------- | -------------------------------------------------------------------------------------------------- |
| Amount                | number          | Yes      | Payment amount in USD, such as 125.50 dollars.                                                     |
| Currency              | select (string) | Yes      | Currency for the transfer amount. Available values: USD. Default: USD.                             |
| Vendor payment method | select (string) | Yes      | Vendor payment method that should receive the transfer. Options load from the selected connection. |
| Brex Cash account     | select (string) | Yes      | Brex Cash account that funds the transfer. Options load from the selected connection.              |
| Description           | string          | Yes      | Internal description for the transfer.                                                             |
| External memo         | string          | No       | Optional memo visible with the payment.                                                            |
| Idempotency key       | string          | No       | Reuse this key only when retrying the same transfer.                                               |

**Outputs**

| Field           | Type   | Description                                                 |
| --------------- | ------ | ----------------------------------------------------------- |
| Transfer        | object | Created transfer with its ID, status, amount, and accounts. |
| Idempotency key | string | Key used to protect the transfer from duplicate retries.    |

#### Create vendor

Create a Brex vendor record for later bills and transfers.

**Required permissions:** `vendors`.

**Inputs**

| Field           | Type   | Required | Description                                                 |
| --------------- | ------ | -------- | ----------------------------------------------------------- |
| Company name    | string | Yes      | Vendor company name shown in Brex.                          |
| Idempotency key | string | No       | Reuse this key only when retrying the same vendor creation. |

**Outputs**

| Field  | Type   | Description                                       |
| ------ | ------ | ------------------------------------------------- |
| Vendor | object | Created Brex vendor with its ID and company name. |

#### List expenses

Retrieve consolidated Brex card expenses and receipt information.

**Required permissions:** `expenses.card.readonly`.

**Inputs**

| Field                  | Type            | Required | Description                                                                                                                                        |
| ---------------------- | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payment posted from    | datetime        | No       | Only include expenses posted at or after this time.                                                                                                |
| Payment posted through | datetime        | No       | Only include expenses posted at or before this time.                                                                                               |
| Status                 | select (string) | No       | Only include expenses with this Brex workflow status. Available values: Draft, Submitted, Approved, Out Of Policy, Void, Canceled, Split, Settled. |
| Spending account ID    | string          | No       | Only include expenses attributed to this Brex spending entity.                                                                                     |
| User ID                | string          | No       | Only include expenses belonging to this Brex user.                                                                                                 |
| Maximum expenses       | integer         | No       | Maximum number of expenses to return across pages. Default: 100.                                                                                   |
| Starting cursor        | string          | No       | Continue from a cursor returned by an earlier listing.                                                                                             |

**Outputs**

| Field       | Type          | Description                                              |
| ----------- | ------------- | -------------------------------------------------------- |
| Expenses    | object\_array | Consolidated expenses with returned receipt information. |
| Next cursor | string        | Cursor for the next page when more expenses remain.      |

#### Create card

Issue a virtual Brex card to an active user with optional spend controls.

**Required permissions:** `cards`, `users.readonly`.

**Inputs**

| Field              | Type            | Required | Description                                                                                                                 |
| ------------------ | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------- |
| Card owner         | select (string) | Yes      | Active Brex user who will own the card. Options load from the selected connection.                                          |
| Card name          | string          | Yes      | Name that identifies the card in Brex.                                                                                      |
| Limit type         | select (string) | Yes      | Use the owner's limit or configure a limit for this card. Available values: Use owner limit, Set card limit. Default: USER. |
| Card spend limit   | number          | No       | Maximum card spend for the selected duration.                                                                               |
| Spend limit period | select (string) | No       | How often the card spend limit resets. Available values: One time, Monthly, Quarterly, Yearly. Default: MONTHLY.            |
| Lock after date    | date            | No       | Optional date after which Brex locks the card.                                                                              |
| Idempotency key    | string          | No       | Reuse this key only when retrying the same card creation.                                                                   |

**Outputs**

| Field           | Type   | Description                                                    |
| --------------- | ------ | -------------------------------------------------------------- |
| Card            | object | Created card metadata without sensitive card numbers.          |
| Idempotency key | string | Key used to protect this card creation from duplicate retries. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/brex.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
