Brex v2

Provides integration with Brex, a financial platform for company spending, cards, expenses, budgets and payments.

Use the Node to read financial records and execute supported account operations with a scoped customer API token.

Revision History

0.0.0.4 - Initial release.

Connection

Property Type Description
API Token Masked The scoped Brex customer user token, generated by an account administrator.

Setup Notes

This Node runs on Cloud Runtimes.

Obtain a customer API token from your Brex administrator and grant the permissions required by the selected operations. Enter it in API Token, then test the Connection. Replace expired or revoked tokens manually.

Methods

Query

Query Brex records using the selected template.

Parameter Type Description
Connection Connection Brex customer token credentials.
OperationId String Operation selected by the template.
Options Object Route and filter values. Cursor and limit are managed internally.
Return Type Description
Response Array One provider object per returned record, without Flowgear mutation metadata.

Create

Create Brex records using the selected template.

Parameter Type Description
Connection Connection Brex customer token credentials.
OperationId String Operation selected by the template.
Items Array One request object per streamed row.
Options Object Route and filter values. Cursor and limit are managed internally.
Return Type Description
Response Array Provider fields plus Flowgear.IsSuccess, Flowgear.Message and Flowgear.Request. Check success for each result.

Update

Update Brex records using the selected template.

Parameter Type Description
Connection Connection Brex customer token credentials.
OperationId String Operation selected by the template.
Items Array One request object per streamed row.
Options Object Route and filter values. Cursor and limit are managed internally.
Return Type Description
Response Array Provider fields plus Flowgear.IsSuccess, Flowgear.Message and Flowgear.Request. Check success for each result.

Delete

Delete Brex records using the selected template.

Parameter Type Description
Connection Connection Brex customer token credentials.
OperationId String Operation selected by the template.
Options Object Route and filter values. Cursor and limit are managed internally.
Return Type Description
Response Array Provider fields plus Flowgear.IsSuccess, Flowgear.Message and Flowgear.Request. Check success for each result.

Action

Execute the selected Brex action.

Parameter Type Description
Connection Connection Brex customer token credentials.
OperationId String Operation selected by the template.
Options Object Required route values for the selected action.
Return Type Description
Response Array Provider fields plus Flowgear.IsSuccess, Flowgear.Message and Flowgear.Request. Check success for each result.

DeleteValues

Delete custom field values using the selected template.

Parameter Type Description
Connection Connection Brex customer token credentials.
OperationId String Operation selected by the template.
Items Array One provider batch envelope per row, with at most 1000 values.
Options Object Required field route values.
Return Type Description
Response Array Provider fields plus Flowgear.IsSuccess, Flowgear.Message and Flowgear.Request. Check success for each result.

Usage Notes

  • Select a template to populate the operation GUID and its route, filter and body fields. Pagination is automatic.
  • Query results contain provider records without Flowgear mutation metadata. Writes return Flowgear.IsSuccess, Flowgear.Message and Flowgear.Request.
  • The first provider request runs when the Node starts; later pages and input items run as results are consumed. An empty connected input performs no writes.
  • Templates requiring idempotency use an input envelope containing IdempotencyKey and Request. Persist a distinct key for each logical write and reuse it only when retrying that write. The Node does not generate keys or automatically replay writes.
  • String and integer collections use CSV. Custom-field value operations accept complete provider batch envelopes, with at most 1000 nested items per request.
  • Sensitive card-number operations, receipt transfers and partner Onboarding APIs are outside the supported surface.

Examples

Supply an idempotent request

For a template that exposes IdempotencyKey and Request, supply each input row in this shape and populate Request with the selected template's required provider fields:

{
  "IdempotencyKey": "saved-key-for-this-logical-write",
  "Request": {}
}

Persist the key before submitting the write. Reuse it only for a retry of the same logical request.