1C:Enterprise (OData) and Brex Integration

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

Build finance workflows between 1C:Enterprise (OData) and Brex 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 1C:Enterprise (OData) and Brex

Detailed info you need to know about 1C:Enterprise (OData) and Brex integrations in WEXTL. Explore which modules apps support and how you connect them.

  • 1C:Enterprise (OData)

    • Finance
    • 2 triggers
    • 37 searches
    • 38 actions

    Business management platform for accounting, trade, and manufacturing.[5]

  • Brex

    • Finance
    • 4 triggers
    • 59 searches
    • 56 actions

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

How to connect 1C:Enterprise (OData) to Brex

Set up your 1C:Enterprise (OData) and Brex integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between 1C:Enterprise (OData) and Brex work in WEXTL?

WEXTL exposes actions and triggers for 1C:Enterprise (OData) 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.

1C:Enterprise (OData) triggersBrex actions

1C:Enterprise (OData) modules

  • Call an HTTP Service Reaches an HTTP service defined in your 1C configuration. Use Body Type with Body to send data in the format your service expects. Output includes Headers and Body.
  • Cancel a Document Posting Reverses posting for a document in 1C. Use Operational Mode to cancel in operational mode, or leave it blank for your configuration default.
  • Complete a Task Marks a task as completed in 1C and returns Completed with its Record Key.
  • Confirm Exchange Plan Changes Tells 1C that an exchange plan message arrived at a node, using the Message Number you received from Get Exchange Plan Changes. Output includes Confirmed.
  • Count Records Counts the records in an object list in 1C and returns the Count. Use Filter with an OData expression to count only matching records.
  • Create a Business Process Creates a business process record in 1C. Output includes the Number and Date. Use Additional Fields for values that are not listed.
  • Create a Calculation Type Registers a calculation type in a chart of calculation types, returning its Code and Description. Use Exchange Load Mode to skip the write-time handlers in 1C.
  • Create a Catalog Item Saves an item into a catalog in 1C. Use Data Load Mode to save it the way a data exchange does, skipping the usual save checks, and Additional Fields for unlisted fields.
  • Create a Characteristic Type Defines a characteristic type in a chart of characteristic types. Output includes its Code, Description and Is Group value.
  • Create a Document Creates a document in unposted state. Output includes its Number and Date, plus the Posted flag. Use Post a Document afterwards to post it.
  • Create a Task Creates a task in 1C. Output includes its Number and Date, plus its Completed flag.
  • Create an Account Records an account in a chart of accounts in 1C. Turn on Exchange Load Mode to write the way an exchange does, skipping write-time handlers, and use Additional Fields for unlisted fields.
  • Create an Exchange Plan Node Inserts a node into an exchange plan, returning its Code, Description, This Node flag and Sent Message Number.
  • Create an Information Register Record Writes a record into an information register in 1C and returns its Period. Use Data Load Mode to write it the way an exchange load does, skipping write-time handlers.
  • Delete a Business Process Removes a business process record. Set Expected Data Version to stop the removal if the process was modified after you read it. No rollback exists.
  • Delete a Calculation Type Deletes a calculation type from its chart in 1C and returns Deleted along with the Record Key. There is no going back.
  • Delete a Catalog Item Deletes a catalog item in 1C. Use Expected Data Version to have 1C refuse the delete when the item changed after you read it. No going back.
  • Delete a Characteristic Type Removes a characteristic type from its chart in 1C and reports the Record Key of the removed entry. Nothing is recoverable afterwards.
  • Delete a Document Removes a document. Use Expected Data Version to have 1C refuse it if the document changed since you read it. Recovery is not possible.
  • Delete a Task Removes a task record and returns Deleted with the Record Key. Nothing can be recovered.
  • Delete an Account Deletes an account, with Expected Data Version available to make 1C refuse the delete when the account changed since you read it. No rollback is available.
  • Delete an Exchange Plan Node Deletes an exchange plan node in 1C and returns Deleted with its Record Key. No recovery is possible.
  • Delete an Information Register Record Removes an information register record in 1C. Nothing restores it afterwards.
  • Get a Business Process Looks up one business process and shows its Number and Date.
  • Get a Calculation Type Fetches one calculation type from its chart, with Code, Description and Predefined Name values.
  • Get a Catalog Item Retrieves one catalog item. Use Fields to list the fields to return, such as Ref_Key and Description.
  • Get a Characteristic Type Loads one characteristic type, with its Is Group flag, Code and Description.
  • Get a Constant Reads the Value of a constant in 1C, such as Company Name.
  • Get a Document Fetches one document with its Number, Date and Posted value. Add field names to Fields to limit the result.
  • Get a Register Record Set Reads every record a given document wrote to a register, with Recorder, Recorder Type and Records.
  • Get a Register Slice Takes the latest or earliest slice of an information register. Use Slice to choose between them, and Period for the date to take it at.
  • Get a Task Retrieves one task with its Number, Date and Name.
  • Get Account Turnovers Reads debit and credit turnovers of an accounting register between Start Period and End Period. Use Group By Dimensions to break them down, and Debit Account Condition to focus on one debit account.
  • Get an Account Reads one account from a chart of accounts, with its Code, Description and Account Type.
  • Get an Exchange Plan Node Pulls one node of an exchange plan, with its Code, Description and Sent Message Number.
  • Get an Information Register Record Reads a single record of an information register, addressed by every dimension plus the Period. Output includes Period.
  • Get Exchange Plan Changes Forms an exchange message for a node and sends the changes recorded since the last confirmed message. Output includes the Changes Feed. Use Confirm Exchange Plan Changes with the same Message Number afterwards.
  • Get Extra Dimension Types Shows the extra dimension types defined on an accounting register. Use Limit to restrict the rows.
  • Get Recalculations Reads recalculation records of a calculation register, filtered by Condition on the register fields and trimmed by Limit.
  • Get Records with Extra Dimensions Queries accounting register records together with their extra dimensions. Bound it with Start Period and End Period, and ask 1C for only the first N records with First Records.
  • Get Register Balance and Turnovers Queries balance and turnover figures for a register, bounded by Start Period and End Period. Use Group By Dimensions to split the rows.
  • Get Register Turnovers Queries turnovers over the span from Start Period to End Period for accumulation or accounting registers. Use Group By Dimensions to break the totals down.
  • Get Scheduled Data Pulls scheduled data for a calculation register. Use Condition to filter by the register fields and Limit to trim the rows.
  • Get the Actual Action Period Gets actual action period data for a calculation register. Use Condition to filter by the register fields and Limit to cap the rows.
  • Get the Calculation Base Reads base data behind calculation register entries, shaped by View Points and by the main and base register dimensions.
  • Get the Register Balance Takes register balances at one date. Use Period for that date, or leave it blank for the current date, and Group By Dimensions to split the balances.
  • List Accounts Lists accounts in a chart. Use Filter to keep only matching accounts, and Limit to cap the count, with at most 10,000 read in one run.
  • List Business Processes Finds business processes of one type. Use Order By to sort them by a field, and Expand to load reference fields in full instead of just their key.
  • List Calculation Types Shows the entries of a chart of calculation types. Turn on Only Records You May Read to skip the ones hidden by access rules, which otherwise make 1C refuse the whole request.
  • List Catalog Items Reads catalog items. Use Fields to name the ones to return, and Filter with DeletionMark eq false to hide items marked for deletion.

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 1C:Enterprise (OData) and Brex integrations. Pick any from the list below if the current combination isn't the one you need.

Automate 1C:Enterprise (OData) and Brex on WEXTL®

Claim your 3-day trial to build 1C:Enterprise (OData) with Brex integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting 1C:Enterprise (OData) and Brex.

How do I connect 1C:Enterprise (OData) and Brex?

Connect your 1C:Enterprise (OData) 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 1C:Enterprise (OData) and Brex?

Example: when the "Watch New Catalog Items" trigger in 1C:Enterprise (OData) fires, WEXTL can "Archive a Budget" in Brex. 1C:Enterprise (OData) has 2 triggers (including Watch New Catalog Items and Watch New Documents). 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 1C:Enterprise (OData) trigger actions in Brex, and Brex in 1C:Enterprise (OData)?

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 1C:Enterprise (OData) and Brex?

No. 1C:Enterprise (OData)-to-Brex automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does 1C:Enterprise (OData) integrate with Brex in real time?

Yes. Trigger-based automations start the moment 1C:Enterprise (OData) (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 1C:Enterprise (OData) + 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 1C:Enterprise (OData) with Brex?

You can build your 1C:Enterprise (OData) + Brex automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the 1C:Enterprise (OData) and Brex integration.

  1. 1C:Enterprise (OData) and Brex integration source code, module specs and credentials implementation.
  2. Our 1C:Enterprise (OData) and Brex integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for 1C:Enterprise (OData) 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. 1C:Enterprise (OData) 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 1C:Enterprise (OData) and Brex integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore 1C:Enterprise (OData) and Brex, or get started