Description
An ‘action’ in workflows is a specific task or operation that the workflow performs after the trigger occurs. These actions will only apply to users who match the workflows audience filters.
This guide details information about all of the actions available in workflows with RESPOND.
Workflow actions A-Z
Action | Description | Example use case | Requirements |
Wait for trigger | Pause the workflow until chosen trigger event occurs. | Resume the workflow after the user has completed all of their training modules. |
|
Add delay | Pause the workflow for a specific amount of time. | Resume the workflow after 7 days. |
|
Slack automation | Send a web request to a URL from Slack, allowing you to perform specific actions within Slack. | Add the user from a specific Slack group if they have not completed their training modules. | |
Send webhook | Send a web request to a URL from a third-party app or service, allowing you to perform actions outside of CybSafe. | Perform specific tasks within a third-party app or service after a high-risk event occurs. |
|
Send notification to user | Send a nudge or alert to the user via your chosen delivery channel(s). | Send users a positive reinforcement message after they successfully report a phishing simulation. | Email service |
Send message to Microsoft Teams channel | Send a message to a specific Microsoft Teams channel. | Send an alert to a private Microsoft Teams channel when a user enters data into a phishing simulations landing page. | |
Send message to Slack channel | Send a message to a specific Slack channel | Send a message to a private Slack channel when a user posts confidential information publicly. | |
Send message to Google Chat space | Send a message to a specific Google Chat space. | Send a message to a private Google Chat space when a user uses unapproved software. | |
Send email message | Send an email to any number of specific email addresses. | Send an email to the security team when a user’s email has been compromised in a data breach. |
|
Add user to group | Add the user to a specific group | Add the user to a ‘high-risk’ group when they enter data into a phishing simulation's landing page. |
|
Remove user from group | Remove the user from a specific group | Remove the user from a ‘high-risk’ group when they successfully report a phishing simulation. |
|
Filter users | Split your workflow into two paths based on an additional audience rule. | Send users down different workflow paths depending on their inclusion in specific groups. |
|
Enrol in training module | Assign a specific training module to the user | Assign a training module to users who enter data into a phishing simulation's landing page. | |
Enrol in phishing campaign | Enrol the user in a specific phishing campaign | Enrol a user into a more challenging phishing campaign after they successfully report a phishing simulation from a different campaign. | |
JIRA automation | Send a web request to a URL from JIRA, allowing you to perform specific actions with JIRA. | Create a JIRA ticket when a high-risk event occurs. |
Additional resources
Still have questions?
If you still have questions, you can contact the CybSafe team via [email protected]. We’re on hand to help resolve any further questions you may have!
