Concepts

Action Execution

How actions get executed

Overview

Actions are the work horses of Stubber.
Actions are defined on the flow.

Anytime anything happens in Stubber, an action is being executed. Having an understanding of how actions are executed is key to understanding how Stubber works.

Actions can get triggered by various mechanisms.
A full list of trigger methods can be found here.

Once an action is triggered it starts execution.

Finding the Action

When you need something to happen in Stubber the first thing you need to do is find the action that will be triggered.
It might be that a message is being received on a stub, then you need to look for the feedback action that is triggered when a message is received.
If you want something to happen when a stub is created you will likewise look for a lifecycle action like the _create action.
Sometimes the action is just a standard stub action and you can implement the action directly on the flow.

Execution Phases

Actions do 4 things:

1. collect data
2. run tasks
3. send notifications
4. record metrics

Actions do these things in 3 execution phases:

1. intent - the user or AI is evaluting the action for required data
2. execution - the action is being executed
3. effect - the action is sending notifications and recording metrics