Connect 1C:Enterprise (OData) integrations

Verified

Business management platform for accounting, trade, and manufacturing, connected to WEXTL workflows and AI agents. Sync 1C:Enterprise (OData) invoices, payments and records with your CRM, billing and operations tools. When Watch New Catalog Items arrives, continue with Count Records or Get a Business Process.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • 1C:Enterprise (OData)
  • WEXTL
  • Zoho Books
  • Splynx
  • Splitwise
  • NetSuite
  • Invoice Ninja
  • Tridens
  • Stripe
  • Checkout
  • Whop
  • PayPal
  • Mintsoft
  • Donorbox
  • Telleroo
  • onPay
  • Shopify
  • Lemon Squeezy
  • MYOB
  • Brex
  • Ongoing WMS

Supported triggers and actions for 1C:Enterprise (OData) integration

Triggers can detect changes in 1C:Enterprise (OData) and run actions that can create, search or modify data inside 1C:Enterprise (OData) automatically[3], exactly how you set them.

  • Watch New Catalog Items Each scheduled check of a catalog starts the workflow for every item created since the previous check. Use Date Field to name the creation attribute, and Limit to size the first run, newest first.
  • Watch New Documents Checks a document type on a schedule and emits each new document, found by its document date. Use Posting Status to limit the watch to posted documents only.
  • 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.
  • 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.

How to integrate 1C:Enterprise (OData) in automation workflow?

1C:Enterprise (OData) in three steps: start with "Watch New Catalog Items", connect one credential, then add your next step.

How 1C:Enterprise (OData) connects and integrates with WEXTL

Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever 1C:Enterprise (OData) app is called in workflows. That allows your finance automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that 1C:Enterprise (OData) supports.

Full 1C:Enterprise (OData) API documentation

The following table illustrates what fields 1C:Enterprise (OData) integration require during authorization flow inside our workflow builder[4].

Connect 1C:Enterprise (OData)

  • Publication URL*Text

    ••••••••

  • Username*Text

    ••••••••

Demonstration of 1C:Enterprise (OData) connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
Publication URLRequired
text

The web address where your 1C database is published, for example https://server.example.com/accounting. You can also paste the full OData address ending in /odata/standard.odata. The server must be reachable from the internet on a standard web port. Your 1C platform must be version 8.3.8 or newer for lists and triggers to work. 1C:Fresh also works when your provider has switched OData on. You may need a user with API access.

UsernameRequired
text

A 1C user with the right to read and write the objects you want to use. Names with Cyrillic letters are fine.

PasswordRequired
password

The password of that 1C user (1C authentication, not Windows login).

Server TimezoneRequired
select

The time zone of the 1C server. 1C stores dates without a zone, so a wrong value shifts every date. If your zone is not in the list, use Make an API Call and type dates in server time. Where the clocks go back, dates stamped in the repeated hour can be missed.

Connect 1C:Enterprise (OData) to popular apps on WEXTL

Enter a name of the other app you want to sync with 1C:Enterprise (OData) below. Click on selected app to explore integration options with 1C:Enterprise (OData). If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.

Example automation with 1C:Enterprise (OData) integration

Select Watch New Documents trigger from 1C:Enterprise (OData) - this will be a starting point in your automation. Whenever event happens in 1C:Enterprise (OData), workflow will start[7] from Watch New Documents node.

Search for Cancel a Document Posting, connect it as the next step of integration sequence. You can use filters between Watch New Documents and Cancel a Document Posting, so only important data pass from Watch New Documents to the next step. WEXTL gives you full control over the process of 1C:Enterprise (OData) automation. All parts of workflow are visible on the canvas[4].

1C:Enterprise (OData) on WEXTL has 77 modules for building finance automations. Explore 1C:Enterprise (OData) documentation for more.

  • 1C:Enterprise (OData)Watch New Documents
  • Zoho BooksPerforms action

OR

  • Zoho BooksTriggers
  • 1C:Enterprise (OData)Cancel a Document Posting
Demonstration of how visual 1C:Enterprise (OData) automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating 1C:Enterprise (OData) in your workflows.

What triggers does 1C:Enterprise (OData) support?

1C:Enterprise (OData) has 2 triggers, including "Watch New Catalog Items" and "Watch New Documents". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in 1C:Enterprise (OData)?

Integration has 75 actions, including "Count Records", "Get a Business Process", and "Get a Calculation Type", and more. Refer to our 1C:Enterprise (OData) Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. The 76 1C:Enterprise (OData) modules, like "Count Records", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].

Is the integration secure?

Yes. You fill in the 1C:Enterprise (OData) credential once. WEXTL encrypts it at rest, and only your team can use it.

How does WEXTL integrate with 1C:Enterprise (OData)?

Through the official 1C:Enterprise (OData) API: 76 modules, plus "Make an API Call" for any endpoint they don't cover[3].

Can I use webhooks with 1C:Enterprise (OData)?

1C:Enterprise (OData) doesn't push events here, so "Watch New Catalog Items" and "Watch New Documents" check on the schedule you set. Anything 1C:Enterprise (OData) posts to a URL can start a Custom Webhook node.

Why use WEXTL platform for 1C:Enterprise (OData) automation?

WEXTL is an AI-first visual canvas: describe the 1C:Enterprise (OData) flow in plain words and AI wires the nodes[4].

Automate 1C:Enterprise (OData) on WEXTL®

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

Cancel anytime.

References

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

  1. 1C:Enterprise (OData) integration source code, module specs and credentials implementation.
  2. Internal 1C:Enterprise (OData) integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official 1C:Enterprise (OData) vendor API documentation, 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. WEXTL® Apps Library
  6. WEXTL® 1C:Enterprise (OData) App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain 1C:Enterprise (OData) app documentation

Explore how WEXTL® crafted 1C:Enterprise (OData) integration page documentation. Used sources, the role of AI, and how the team validates the result.