Is it possible to use two triggers in a single flow?

The short answer is no, but there is a workaround using platform resources. Follow the steps below to learn how:

Context

In some scenarios, you may need to trigger the same flow in different ways. Imagine you have a trigger that needs to run automatically every day at a set time, but there are also situations where the flow must be triggered immediately, such as when an important sale is registered and needs to be processed as quickly as possible.

Instead of duplicating the flow and creating two independent triggers (e.g., one temporal and another via Webhook), which would result in higher maintenance efforts, you can encapsulate the flow logic in a flow call. This way, the same process is executed in different contexts, allowing you to trigger the flow both automatically and on demand.

Step-by-step

Here, we’ll explain the details of how to set up this solution to trigger the same process at different times.

Our step-by-step guide is divided into three parts: primary flow, secondary flow, and tertiary flow.

Primary flow

The primary flow was created as follows:

Secondary flow

The secondary flow was created as follows:

With the trigger set to run every day at 1:00 AM, as shown in the image below:

Tertiary flow

The tertiary flow was created as follows:

Conclusion

The primary flow is triggered by either the secondary or tertiary flow, with the main difference between them being the triggers configured in each. The Time Trigger initiates the flow based on a time interval, while the Webhook Trigger is activated via an HTTP call.

Summary

We use the primary flow as a block that can be called within another flow, while the others, in this scenario, are merely ways to initiate/trigger the primary flow that contains the Flow Call.

Therefore, there are several ways to trigger this flow, which can be customized to meet the specific needs of each user's scenario.