Call Functions and Generic Events

Generic events can be triggered from other workflows or within the same workflow. Additionally, generic events can be used like functions and can also trigger events in other workflows.

Call functions or generic events to reuse specific executions in multiple places across different workflows.

Or simply use function calls to create better separation within workflows.

Different between functions and events

First of all, we need to understand the difference between calling an event and calling a function.

In both cases, our base is the generic event.

However, the different types of calls make a significant difference.

Call a generic event

Events will be handled in a global queue, which processes them one by one.

In both examples, the “Generic Event“ will be executed after the 'Event' has completed its own execution chain.

Call event or function can also parse variables. Learn more about this here.

Call a function

Calling a generic event with the “Call Function“ action inserts it into the execution chain.

Look carefully at the execution triggers.

In these two examples, it’s clearly visible how the call functions are placed within the execution chain.


Call a generic event within the same workflow

To call a generic event, an action is required, and of course, at least one generic event must exist within the workflow.

Add Call Generic Event action

To add the "Call Generic Event" action, perform a secondary click on an empty space within the workflow.

To link the generic event with this action, define the target within the inspector.


Call a function

To call a generic event like a function, you need an action and at least one generic event in the workflow.

Add Call Function action

To add the "Call Function" action, do a secondary click on an empty space within the workflow.

To link the generic event with this action, define the target within the inspector.

Add Function return

Connect the function return

Last updated