brex_skill

Overview

This skill integrates with Brex to manage corporate cards, accounts, vendors, bills, expenses, and budgets. It uses the Membrane CLI to handle authentication and credential refresh so you can focus on querying and mutating Brex data. The skill exposes common actions for listing and manipulating users, cards, expenses, vendors, transfers, and budgets.

How this skill works

The skill calls Brex through Membrane, which manages OAuth, tokens, pagination, and error handling. You create or reuse a Membrane connection, discover available actions, and run actions or proxy raw API requests when needed. Common operations include list/get/create/update/delete actions for core Brex resources and direct proxy requests for custom endpoints.

When to use it

• When you need to list or inspect Brex resources (users, cards, expenses, vendors, accounts, budgets).
• When you want to create or update vendors, cards, transfers, or expenses programmatically.
• When you prefer not to handle Brex auth flows or token refresh locally. Use Membrane-managed connections.
• When pre-built actions cover your use case and you want pagination and error handling handled automatically.
• When you need to call a Brex endpoint not covered by an action — use the proxy request feature.

Best practices

• Always use Membrane actions first; they handle auth, pagination, and edge cases.
• Check existing connections with membrane connection list before creating a new one to avoid duplicates.
• Run membrane action list with the appropriate intent to discover available action IDs and input schemas before coding.
• Use membrane request (proxy) only when no pre-built action exists; include method, headers, and body flags as needed.
• Never ask users for Brex API keys; create a Membrane connection so credentials are managed server-side.

Example use cases

• Sync all Brex card transactions into accounting system by listing transactions and mapping them to ledger entries.
• Bulk-create or update vendors from a procurement spreadsheet using create-vendor and update-vendor actions.
• Automate monthly budget checks by listing budgets and alerting on budget thresholds or overspend.
• Retrieve a specific expense, amend its memo or category, and save the update via update-card-expense.
• Make an uncommon API call (e.g., a new Brex endpoint) by proxying a request through Membrane when no action exists.