Actions Registry
Learn how to use and modify pre-built integrations in your workflows.
Goals
By the end of this tutorial, you will learn:
- How to create new actions from Action Templates in the Actions Registry
- How to use Action Templates to create more powerful integrations
- How to update an existing Action Template across all workflows directly in the UI
Prerequisites
- Completed the Quickstart tutorial
- Completed the Control Flow tutorial
Tutorial
Check out the Actions Registry
Go to the Actions Registry by clicking on the Registry tab back in the workflows view.
Actions are registered at the organization level and can be used across all workflows and workspaces.
Clone existing Action Template
Let’s create a new action called Is URL malicious
.
First, find and clone the existing Search URL with VirusTotal
action template by selecting New from template in Action Registry.
Edit the new action
Edit the action to get the VirusTotal report, check if the URL is malicious, and return a single boolean value. Copy the following configuration into the YAML editor:
Replace actions in workflow
Go back to Enrich URL with VirusTotal
workflow and replace the Search URL with VirusTotal
and Extract VirusTotal report
actions with the new Is URL malicious
action.
Remove the if-condition and update action result references
Remove the previously created if-condition from List VirusTotal comments on URL
action Control Flow tab.
Update the List VirusTotal comments on URL
action Input to use the trigger URL:
Modify output data
Click on the canvas to view workflow settings, then go to the Schema tab. Modify the Output Schema to following:
Run the workflow
Click on the Run button to execute the workflow. Use the same sample payload:
The results will be similar to the previous tutorial.
Why use Action Templates?
Action templates allow you to:
- Define explicit input and output schemas for your integrations
- Combine actions into reusable pieces of tradecraft that aren’t just API calls
- Build integrations that are easier to edit across workflows
- Declutter your workflows with fewer filler actions
Best Practices
- Action templates should contain logic for only one integration.
- Action templates should be simple and contain at most three actions.
- Action templates should be used to normalize input and output data between actions.
- Action templates are not mini-workflows.