Who can perform these steps: Members of AnyCross
Intro
AnyCross is a robust, accessible solution designed to help organizations seamlessly integrate various applications onto a single unified platform. Featuring a visualized interface, organizations can easily, flexibly, and quickly integrate apps and systems with Lark, build automated processes, and much more.
Features and benefits of different plans are shown in the table below. If you need more flows or other help, contact Support or the Customer Success Manager.
Capabilities
AnyCross links a multitude of business systems, with low- or no-code. By enabling app-to-app connections and business automation, information travels more efficiently within the organization, all while boosting data quality and accessibility.
- Visualized orchestration of system integrations: Business systems are abstracted into standard connectors, enabling users to connect different systems together using a visual toolkit.
- Diverse connectors: A wide range of connectors are readily available.
- Out-of-box core and helper components: Encapsulate common business logic and data processing capabilities into core and helper components that can be used straight out of the box. When corresponding capabilities need to be added to a business flow, you can add core or helper components to the corresponding nodes and configure them.
- Full-lifecycle integration management: Organizations are empowered to manage integrations throughout their full lifecycle, with the ability to configure, test, and publish integrations, check logs, monitor operations, and more—all in one place.
- Solutions for common scenarios: Ready-to-use solution templates that suit diverse needs, such as syncing of personnel data and customer data.
Advantages
- Widely applicable: A multitude of connectors are usable to integrate common business systems easily and quickly.
- More efficient: Core and helper components transforms data and logic processing of integration into low-code or no-code work
- Lower costs: Connectors, templates and solutions from AnyCross cut the amount of time needed to implement a function from multiple days to within 24 hours.
- More secure: Full-lifecycle management and real-time monitoring of integrations offer full interoperability while guaranteeing data security and auditability.
Scenarios
Key Concepts
Workflow
Workflow refers to defining how data is sent from one app to another app using the Flow Editor, including when it's sent, the conditions for sending data, the data format, and how the application expects to receive data.
You can arrange the workflow by dragging and dropping connectors in the Flow Editor. These connectors can obtain data from a Lark app (such as Approval) or third-party services (such as Weaver) and perform actions. Users can use core and helper components to arrange the flow logic and process data, as well as send data to a node in the workflow.
250px|700px|reset
Triggers
Triggers hold the conditions for automatically executing each flow. The workflow must be activated by an event acting as a trigger, which can be based on event services. Using the "Leave request" in Approval as an example, when a request is approved, the sequence of actions in the flow will begin. If the desired trigger service isn't available, you can choose to use webhook trigger instead.
Connectors
Connectors are the main part of a workflow and highly encapsulate specific business systems, including authentication and function interfaces. When designing a flow, you can use common business systems (such as Lark Contacts and Weaver). Using these preset connectors, you can use the interface capabilities of business services directly in a flow and connect to a business system at zero cost.
You can select the API for a business system and configure it in the Visual Actions interface. When designing a workflow, the output of every connector can be used by other connectors. If the business system you want to use doesn't provide any connectors, you can use the "HttpClient" component that we offer.
Core and helper components
Core and helper components are the encapsulation of common coding logic and the abstraction of data processing capabilities in the flow. They are integral for arranging a workflow. AnyCross encapsulates common business logic and data processing capabilities into core and helper components that can be used straight out of the box. When corresponding capabilities need to be added to a business flow, you can add core or helper components to the corresponding nodes and configure them.
Authentications
When a connector accesses a third-party system, it must use an "authentication" to declare how AnyCross will establish an access relationship with the third-party system. An authentication contains a network channel, credentials, and service endpoint information. You must create and select an authentication in order to use connectors.
- By default, the network channel doesn't need to be selected. When you need to connect to a system on the Intranet, you must select a proxy service.
- Credentials, such as username, password, and App ID/App Secret, are required to access the third-party system
- The service endpoint refers to the entry to the third-party system, which is usually the endpoint of the HTTP interface.