...
Overview
| Excerpt | ||
|---|---|---|
| ||
Actions allow you to automate common tasks |
Actions are
...
macros which can be put in Event Triggers. When the event is detected, the trigger performs the actions.
They are extremely useful because they enable the workflow to automate common tasks - from adding labels, to sending emails and even synchronising content with another server.
Example
In this example, the {trigger} listens listens for the pagecreated event (only available in Space Mode) and then performs the {set-message} action action.
| Code Block | ||||
|---|---|---|---|---|
| ||||
{workflow:name=Action macros}
{state:Test}
{state}
{trigger:pagecreated}
{set-message}This is a new page created by @creator@{set-message}
{trigger}
{workflow} |
...
Most actions support Value References, such as @creator@ in the example above.
These are named placeholders for information stored somewhere else, and they allow your actions to respond dynamically to current workflow and content state.
...
Action macros must be placed inside the macro body of a {trigger} macrotrigger macro.
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Events
Certain actions will generate additional events. For more details, see the macro documentation above.
...
Certain macros will be affected by application settings. For more details, see the macro documentation above.
Examples
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|