Brex and ShipMonk Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build finance workflows between Brex and ShipMonk on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Brex and ShipMonk

Detailed info you need to know about Brex and ShipMonk integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Brex

    • Finance
    • 4 triggers
    • 59 searches
    • 56 actions

    Corporate cards, spend management and business banking.[5]

  • ShipMonk

    • Finance
    • 4 triggers
    • 7 searches
    • 8 actions

    Third-party logistics for ecommerce orders, receivings, and returns.[6]

How to connect Brex to ShipMonk

Set up your Brex and ShipMonk integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Brex and ShipMonk work in WEXTL?

WEXTL exposes actions and triggers for Brex and ShipMonk that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Brex triggersShipMonk actions

Brex modules

  • Archive a Budget Moves a budget into the archive using the v2 budgets endpoint.
  • Archive a Spend Limit Archives a spend limit through the v2 endpoint. Limits made through the older endpoint need Archive a Spend Limit (v1) instead.
  • Archive a Spend Limit (v1) Archives a spend limit that was made on the older v1 budgets endpoint. Spend limits from the v2 endpoint use Archive a Spend Limit.
  • Create a Budget Opens a budget under a Parent Budget, with a Name, Description, Period and Amount. Brex rejects Hard as the Limit Type for budgets, so use Create a Spend Limit for a hard limit. Bound it with Start Date and End Date.
  • Create a Card Issues a card to a Card Owner. A physical card needs a mailing address and a vendor card must be virtual with its own Spend Limit and refresh. Set Limit Type to User to follow the limit of the user.
  • Create a Custom Field Defines a custom field for the Accounting, User, ERP or Travel Group. Use Remote ID to tie it to an ID in an outside system. The ERP group also needs an Accounting Integration.
  • Create a Department Registers a department in Brex, ready for people to be placed in.
  • Create a Location Creates a location in Brex. Create a User and Update a User can then assign users to it.
  • Create a Spend Limit Creates a spend limit with its Name, Period and Base Limit. Use Authorization Type to decline card authorizations once the balance runs out or to allow going over, and Rollover Refresh Rate to set how often unused rolled-over funds reset.
  • Create a Spend Limit (v1) Sets up a spend limit on the older v1 budgets endpoint, from a Name, Parent Budget, Period and Limit. Use Spend Type to control which cards can spend from it and Limit Visibility to set whether members can see the limit.
  • Create a Tax Code (Alpha) Defines a tax code inside an accounting integration, with its Name and percentage Rate. Use Subsidiary IDs to limit it to certain subsidiaries and Remote ID to match the code in your accounting system.
  • Create a Tax Group (Alpha) Groups tax codes under one Name for an accounting integration. The names Not Eligible and Custom are reserved and cannot be used.
  • Create a Title Adds a job title to Brex for users to hold.
  • Create a Transfer Sends an Amount out of a Brex cash account, either to a vendor payment account or to another Brex account through Send To. Use External Memo for wire instructions or the ACH entry description and Description for an internal note.
  • Create a User Registers a person from a First Name, Last Name and Email. Use Manager, Department, Location, Title, Cost Center and Legal Entity to place the user in your organization.
  • Create a Vendor Registers a vendor in Brex under a unique Company Name, in ASCII characters only. Use Payment Accounts to set how it gets paid, by ACH, Domestic Wire or Cheque, and add an Email or Phone.
  • Create an Accounting Integration Links Brex to an accounting system, Campfire, Dualentry, Hanover Park, Inkle or Rillet, through your Vendor Account ID. Turn on Amortization to set up the amortization fields as well.
  • Create an Amortization Template (Alpha) Defines an amortization template for an accounting integration. Use Remote ID to link it to the same template in your accounting system.
  • Create an Incoming Transfer Pulls an Amount from a linked bank account into a Brex cash account, with a Description for internal use. Transfers are in USD.
  • Create Custom Field Values Fills a custom field with up to 1000 values. Each Values entry takes a display Value, and you can link it to an outside system through a Value ID or Remote ID. Enable Disabled to block a value from being picked.
  • Delete a Custom Field Deletes a custom field by removing its definition from Brex.
  • Delete a Department Deletes a department from the organization in Brex.
  • Delete a Location Removes a location from the places Brex users can be assigned to.
  • Delete a Tax Code (Alpha) Deletes a tax code of one accounting integration.
  • Delete a Tax Group (Alpha) Removes a tax group that sits under an accounting integration.
  • Delete a Title Deletes a job title from the titles Brex users can hold.
  • Delete a Vendor Removes a vendor you pay through Brex.
  • Delete an Amortization Template (Alpha) Removes the amortization template of an accounting integration.
  • Delete Custom Field Values Deletes values from a custom field. Use Identify By to say whether the IDs are Brex IDs, Value IDs or Remote IDs.
  • Disconnect an Accounting Integration Disconnects an accounting integration and returns its Status, Vendor and Vendor Account ID.
  • Email a Card Number Emails a secure link to the details of a card, with your Sender Name in the subject of the email. The link works for 30 days unless a different number of days is given. Use Message to include a note.
  • Get a Budget Loads a budget, showing its Name, Description, Parent Budget ID and Owner User Ids.
  • Get a Budget Program Retrieves a budget program with its Budget Blueprints, Existing Budget Ids and Employee Filter.
  • Get a Card Pulls a card, showing its Owner, Status, Last Four and Card Type.
  • Get a Cash Account Reads one cash account and returns its Current Balance and Available Balance.
  • Get a Cost Center Reads one cost center and returns its ID and Name.
  • Get a Custom Field Shows how a custom field is set up: Name, Remote ID and whether it Is Disabled.
  • Get a Custom Field Value Reads one value of a custom field, giving its Value, Remote ID and Updated At.
  • Get a Department Looks up a department, returning its ID, Name and Description.
  • Get a Legal Entity Looks up a legal entity: Display Name, Billing Address, Status and Is Default.
  • Get a Location Reads a location and returns its ID, Name and Description.
  • Get a Spend Limit Loads a spend limit from the v2 endpoint, showing its Name, Parent Budget ID and Status.
  • Get a Spend Limit (v1) Loads a spend limit on the v1 budgets endpoint, showing Name, Creator User ID and Parent Budget ID.
  • Get a Tax Code Shows a tax code for an accounting integration, returning its Name, Rate and Subsidiaries.
  • Get a Tax Group Shows a tax group for an accounting integration, returning its Name, Tax Codes and Subsidiaries.
  • Get a Title Shows one job title with its ID and Name.
  • Get a Transfer Looks up a transfer, showing its Counterparty, Payment Type, Amount and Process Date.
  • Get a Trip Opens a trip, showing its Name, Booker User ID and Status.
  • Get a Trip Booking Reads one booking on a trip, showing its Type, Version and Created At. Turn on Load Custom Fields to include its custom field values.
  • Get a User Loads a Brex user with First Name, Last Name, Email, Status and Manager ID. Turn on Load Custom Fields to add custom field values.

ShipMonk modules

  • Complete a Receiving Finishes an inbound receiving inside the ShipMonk sandbox. Use Completion Mode to end it as fully, short, excess or partially received, and give the Receiving Key or the ASN to say which one.
  • Complete an Order Finishes an order inside the ShipMonk sandbox. Use Pack Type to complete it as a single pack or a multipack, and give the Store ID of the store the order belongs to.
  • Create or Update a Product Saves a product to the ShipMonk catalog with a Product Key, SKU, Name, Country of Origin and Customs Declaration Value. Add Weight (Lb) and Dimensions (Inches) for its size, and an HS Code for customs.
  • Create or Update a Receiving Announces an inbound shipment to a ShipMonk Warehouse, with an ASN, Supplier Name and Estimated Delivery. Fill Handling Unit Type and Handling Unit Quantity to say what is arriving, and Items for the expected SKUs.
  • Create or Update a Return Records a customer return in ShipMonk under an RMA, listing the Items coming back and a Return Reason. Fill Order Key to link it to the original order, and Tracking Number to follow the parcel.
  • Create or Update an Order Sends an order to ShipMonk: Items, Order Number, Requested Shipping Service and Order Status. Reuse an Order Key to update that order. Use Submit At for a delayed submission.
  • Get a Receiving Reads one inbound receiving. Look it up with either a Receiving Key or an ASN, and read its Receiving lines and the arrival and receipt dates.
  • Get an Order Looks up one ShipMonk order by Order Key or Order Number, with its Items and destination address. Use it to read the Tracking URL, Packages and Processing status of the order.
  • List Warehouses Fetches the warehouses on your ShipMonk account, each with an Identifier, Timezone, Enabled flag and Address. Order the list with Sort By and Sort Order, and stop it early with Limit.
  • Make an API Call Runs a free-form request against the ShipMonk REST API using your saved credential.
  • Search Orders Looks up orders by Order Status, or by lists of Order Keys and Order Numbers. Use Sort Order to reverse the direction, and read the Tracking URL and Packages of each order found.
  • Search Products Lists products matching a Search term or a Status. Use Date Updated Start to find products changed since a date, and Sort By to order the results.
  • Search Receivings Pulls receivings matching an ASN or a Warehouse ID. Use Created At or Updated At to limit them by time, and read the Supplier name and Receiving lines of each one.
  • Search Returns Checks returns against an RMA, Return Status, Return Reason or Desired Action. Add Warehouse ID to stay within one warehouse, and read the Tracking number of each return found.
  • Submit an Order Passes an existing ShipMonk order on for fulfillment. Use Submit At with a past or a future date and time.
  • Watch Orders Polls ShipMonk for orders created since the previous run and passes each into the workflow. Use Order Status to restrict it to one status, and Limit to choose how many are handled in a run.
  • Watch Products Looks at the product list on a schedule. Use Trigger on to react to products as they are created or as they are updated, and Limit to cap each run. Every product arrives with its SKU and Name.
  • Watch Receivings Finds receivings added since the last scheduled run, one workflow start for each. Use Warehouse ID to follow a single warehouse, and Limit for the most taken per run.
  • Watch Returns Collects returns created since the last run, one workflow start per return. Use Return Status to react only to returns in one state, and Limit for the batch size of a run.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Brex and ShipMonk integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Brex and ShipMonk on WEXTL®

Claim your 3-day trial to build Brex with ShipMonk integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Brex and ShipMonk.

How do I connect Brex and ShipMonk?

Connect your Brex and ShipMonk accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Brex and ShipMonk?

Example: when the "Watch Card Transactions" trigger in Brex fires, WEXTL can "Complete a Receiving" in ShipMonk. Brex has 4 triggers (including Watch Card Transactions, Watch Cash Transactions, and Watch Events). ShipMonk has 15 actions (including Complete a Receiving, Complete an Order, and Create or Update a Product). Add filters and transforms between steps when you need them.[1]

Can Brex trigger actions in ShipMonk, and ShipMonk in Brex?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Brex and ShipMonk?

No. Brex-to-ShipMonk automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Brex integrate with ShipMonk in real time?

Yes. Trigger-based automations start the moment Brex (or ShipMonk) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Brex + ShipMonk integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Brex with ShipMonk?

You can build your Brex + ShipMonk automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Brex and ShipMonk integration.

  1. Brex and ShipMonk integration source code, module specs and credentials implementation.
  2. Our Brex and ShipMonk integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Brex and ShipMonk, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Brex integration information
  6. ShipMonk integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Brex and ShipMonk integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Brex and ShipMonk, or get started