1C:Enterprise (OData) and Lyra Integration

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

Keep 1C:Enterprise (OData) and Lyra matched by integrating their events and actions. When finance events happen in 1C:Enterprise (OData), update the Lyra 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 1C:Enterprise (OData) and Lyra

Detailed info you need to know about 1C:Enterprise (OData) and Lyra 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]

  • Lyra

    • Finance
    • 2 triggers
    • 5 searches
    • 8 actions

    Payment gateway for charges, refunds, and hosted checkout across cards, wallets, and net banking.[6]

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

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

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

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

Lyra modules

  • Create a Charge Creates a charge for an order, from its Order ID, Currency, Amount and Customer. Set Webhook URL to have Lyra send payment status updates to your own address.
  • Create a Charge (PG) Sets up a charge through the PG endpoint, from an Order ID, Currency, Amount and Customer. Use Webhook to get status updates and Order Information to describe the order.
  • Create a Refund Requests a refund of a charge for a Refund Amount in a Currency. Use Refund Reference to tag the request, and keep it unique to avoid duplicate refunds.
  • Drop a Charge Cancels a charge and records the Drop Reason. The result includes a Drop reason.
  • Get a Charge by UUID Retrieves the details and payment status of one charge. Output also has the Link to the charge and the Attempts count.
  • Get a Charge Status Retrieves the payment status of a charge. The result shows the Status, how much is Paid or Due, and the number of Attempts.
  • Get a Refund Status Checks how one refund request is progressing, using the UUIDs of the charge and of the refund. The result includes the Status and any Error.
  • Initiate a Net Banking Payment Begins a net banking payment on a charge, paid through the chosen Bank. Returns a Method, URL and Params.
  • List Charges Searches for the charges created with an Order ID. Use Limit to cap how many are returned. Each result has its UUID, Date, Status, Currency and Amount.
  • List Refund Requests Searches the refund requests made against a charge. Use Refund Reference to find the ones created with that merchant reference, and Limit to cap the results.
  • Make an API Call Makes an authorized free-form request to the Lyra REST API with your saved credential.
  • Submit a Card Payment Starts a card payment attempt on a charge, from the Card Number, Expiration Month, Expiration Year, CVV and Card Holder Name. The result has Method, URL and Params fields.
  • Submit a Wallet Payment Pays a charge from a wallet the customer selects. Output gives the Method, URL and Params.
  • Watch Charges Runs on a schedule and reads the charges that share an Order ID, to follow their status. Use Limit to set how many charges each run reads.
  • Watch Refund Requests Polls the refund requests of one charge on your schedule. Narrow it with Refund Reference, and use Limit to control how many each execution returns.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with 1C:Enterprise (OData) and Lyra integrations. Pick any from the list below if the current combination isn't the one you need.

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

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

Cancel anytime.

Frequently asked questions

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

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

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

Example: when the "Watch New Catalog Items" trigger in 1C:Enterprise (OData) fires, WEXTL can "Create a Charge" in Lyra. 1C:Enterprise (OData) has 2 triggers (including Watch New Catalog Items and Watch New Documents). Lyra has 13 actions (including Create a Charge, Create a Charge (PG), and Create a Refund). Add filters and transforms between steps when you need them.[1]

Can 1C:Enterprise (OData) trigger actions in Lyra, and Lyra 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 Lyra?

No. 1C:Enterprise (OData)-to-Lyra 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 Lyra in real time?

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

You can build your 1C:Enterprise (OData) + Lyra 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 Lyra integration.

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

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