Billdu and Brex Integration

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

Keep Billdu and Brex matched by integrating their events and actions. When finance events happen in Billdu, update the Brex automatically - without any line of code in visual workflow builder.

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

Learn about Billdu and Brex

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

  • Billdu

    • Finance
    • 3 triggers
    • 8 searches
    • 10 actions

    Invoice creation, billing, and payment management for small businesses.[5]

  • Brex

    • Finance
    • 4 triggers
    • 59 searches
    • 56 actions

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

How to connect Billdu to Brex

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

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

WEXTL exposes actions and triggers for Billdu and Brex 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.

Billdu triggersBrex actions

Billdu modules

  • Add a Payment Records a payment received for an existing document. Use Payment Date to set when it was received and Variable Symbol to attach a reference to it.
  • Create a Client Creates a client from a Company name. Add Email or Phone for contact details, or Shipping Street and Shipping City for a separate delivery address. The result includes the ID of the client.
  • Create a Document Creates an invoice, order or estimate for a Client and lists what is billed under Items. Set Maturity (Days) for the payment term and Currency or Discount for pricing. Output includes the Status of the new document.
  • Create a Product Adds a product under a Label with a Price. Set Stock Number, Count and Unit to describe stock, and Tax (%) for the rate. Output includes the ID and Created date.
  • Delete a Client Deletes one client from your Billdu account.
  • Delete a Document Removes an existing document from Billdu, whatever its type.
  • Delete a Product Removes a stored product entry from Billdu.
  • Download a Document Downloads a document as a file. Output is one item holding Data.
  • Get a Client Shows a single client, including Company, Name, Surname, Salutation and Country.
  • Get a Document Retrieves one document along with its Custom ID, Status and Payment.
  • Get a Product Finds a single product and gives its Label, Price, Count and Unit.
  • Get an Image Fetches an image as Data. Billdu cannot list images, so take the number for Image ID from an image link in a product or document response.
  • List Clients Returns the clients in your account, each with Company, Name, Surname and Country. Use Limit to cap the number returned.
  • List Documents Fetches documents with their Currency and Vs values. Add Document Type to narrow the results to one kind, and Limit for a maximum count.
  • List Products Gives every product along with its Label, Price and Unit. Set Limit when you want only the first few.
  • Make an API Call Calls the Billdu REST API directly with a free-form request under your saved credential.
  • Send a Document Emails a document to the addresses added under Recipients. Use Subject and Message to write what the email says.
  • Update a Document Changes the Paid On date, Payment Method, Note, Header, Currency, Discount or Locale of a document. Use Document Color to set its color.
  • Watch Clients Polls Billdu on a schedule and emits each newly created client with its Company, Name and Surname. Use Limit to set how many results are worked with in one cycle.
  • Watch Documents Checks Billdu regularly for newly created documents and returns each with its Custom ID, Currency and Status. Raise or lower Limit to change the batch size per check.
  • Watch Products Reports newly added products on a schedule, including the Label, Price and Unit. Cap the work done per run with Limit.

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.

Explore alternative integrations

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

Automate Billdu and Brex on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Billdu and Brex.

How do I connect Billdu and Brex?

Connect your Billdu and Brex 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 Billdu and Brex?

Example: when the "Watch Clients" trigger in Billdu fires, WEXTL can "Archive a Budget" in Brex. Billdu has 3 triggers (including Watch Clients, Watch Documents, and Watch Products). Brex has 115 actions (including Archive a Budget, Archive a Spend Limit, and Archive a Spend Limit (v1)). Add filters and transforms between steps when you need them.[1]

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

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 Billdu and Brex?

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

Does Billdu integrate with Brex in real time?

Yes. Trigger-based automations start the moment Billdu (or Brex) 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 Billdu + Brex 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 Billdu with Brex?

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

References

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

  1. Billdu and Brex integration source code, module specs and credentials implementation.
  2. Our Billdu and Brex integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Billdu and Brex, 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. Billdu integration information
  6. Brex integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore Billdu and Brex, or get started