Scenarios

Universal integrations let you define a common logic that works across many external applications and customers.

We recommend organizing universal integrations in Scenarios that contain all the building blocks in one place.
Scenarios help you conveniently manage multiple pieces of integration logic across multiple applications.

To start building a universal integration, go to the Scenarios page and create a new one.

Scenario Templates

For common use cases, we provide pre-built and well-tested scenario templates. You can use them as a starting point for your integration and then customize.

After selecting a scenario and integrations to apply it to, you can proceed to adding it to your app or customize it using the section below.

Custom Scenarios

The main building blocks of a scenario are Actions and Flows.

To choose whether to use Action or Flow, use this comparison table:

If an Action works for you, you should use it. If you need to make it more complex later, you can re-use it in a flow.

After you've picked the main building block, see corresponding documentation for more details:

Dynamic Scenarios (Advanced)

When you do not know the exact logic of your integration ahead of time, you will need to use integration metadata to create it dynamically.

Typical use cases when this approach is needed:

• AI agent that picks actions dynamically based on the context.
• Complex integration logic that you want to keep on your application's side.

Integration Engine provides rich metadata about integrations, resources available through it, and any middleware you've created.
You can explore the available entities using Data Collections.