Actions are the third stage of a task. They can take the job results and eg. distribute them. Some actions may require a specific type of data to be added to the list of actions.
Actions are executed one after the other without a guaranteed order. If an Action fails, it does not stop the task execution but it will continue with the next Action.
Each Action is executed only once, even if there is a list of results from one or more jobs. If an Action should be executed once for each result, a series should be used instead.
Actions will usually be provided with each job's result and can then decide what it is going to do with it. Some actions require a specific type of data as input, e.g. the FTP action needs a file. They will not be executed if there is no job result having the required type. Other actions do not need any specific input (email, IRC).
There are two indicators to find out which kind of input is going to be processed:
Note: Actions that are greyed out can be added and configured but will not be executed. The reason for this is that the action requires a specific input that is not fulfilled by any job.
The Execution Qualification selection becomes available when one or more jobs have been configured with a condition. Conditions will evaluate to valid or invalid state which is being sent to the action along with every job result.
Note: Jobs without a condition will always produce a valid result.
One of the following options can be selected to determine how the results will be processed:
A job can return metadata which is available via placeholders and can be used in fields that allow placeholders, e.g. text and file fields. Placeholders that can not be found in the metadata of a result will not be replaced.