# Actions
## What is an action?
*Actions* are the operations available for creating and automating, which live inside of a [workflow](/documentation/automations/workflows.md). You grab these actions from the left side menu of the workflow builder, and drag them onto the workflow canvas. When you run a workflow, Rewst is completing a series of actions specified within that workflow. Once an action has been dragged onto the canvas, we refer to that dragged action as a *task*, to differentiate between a dragged and undragged action.
Once you've set up an [integration](https://docs.rewst.help/documentation/integrations), Rewst offers you a number of actions related to that integration to build your workflows. They're accessible from the accordion menus in the left side menu of the workflow builder, and sorted based on their respective sources, including integrations by brand, Core, Rewst, Transform, and Workflow. Expand any accordion to see the related actions it contains.
The actions menu of the workflow builder
Each action serves a unique purpose and comes with a brief description to aid in understanding its functionality. Click on any action to begin dragging and dropping it onto your Workflow Builder Canvas. For more on our workflow builder and how workflows are essential to Rewst, see our workflow documentation [here](https://docs.rewst.help/documentation/workflows).
{% hint style="success" %}
Click through to any of the related action type pages to learn more.
{% endhint %}
Each task has a set of configuration options within it, editable in its right side menu of the Workflow Builder once dragged onto the canvas. Learn more about settings for tasks [here](/documentation/automations/workflows/workflow-builder-how-to-set-up-a-workflow.md#configure-tasks) in our workflow documentation.
### Core actions
These are the essential platform components like webhooks, email dispatching, and [noops](https://docs.rewst.help/documentation/workflows/actions-in-rewst/core-actions#no-operation-noop).
{% content-ref url="/pages/ItLAL7BSFZkafcQPS6S6" %}
[Core actions](/documentation/automations/actions-in-rewst/core-actions.md)
{% endcontent-ref %}
### Integrations actions
When you set up an integration in Rewst, it comes with a predefined set of actions, which will appear in your workflow builder action menu. These actions allow you to work with various parts of the integrated product as per its API. Rewst's integrations pull in the most useful and most commonly used actions, but not all available actions. See our [individual integration setup pages](/documentation/integrations.md) for more information on available actions.
{% content-ref url="/pages/OSnkx0SEHcbueeC19adV" %}
[Integrations](/documentation/integrations.md)
{% endcontent-ref %}
### Rewst actions
These actions are for interacting with your Rewst environment. You can perform tasks such as creating organizations and users, associating with multi-tenanted objects, and setting organization variables.
{% content-ref url="/pages/5tKhys9AyA11Caej1cal" %}
[Rewst actions](/documentation/automations/actions-in-rewst/rewst-actions.md)
{% endcontent-ref %}
### Transform actions
These actions help you shape and modify your data for efficient workflow execution, replacing the need for complex Jinja statements.
{% content-ref url="/pages/wzApPvhqXx0qV57qBEbb" %}
[Transform actions](/documentation/automations/actions-in-rewst/transform-actions.md)
{% endcontent-ref %}
### Workflows actions
These actions allow you to call other workflows within your environment. They enable you to feed information from the parent workflow as inputs and return the results upon completion.
{% content-ref url="/pages/vIgZWGeoD6JWH1YqyITR" %}
[Workflows actions](/documentation/automations/actions-in-rewst/workflows-actions.md)
{% endcontent-ref %}
### Generic actions
For each integration, Rewst provides a single action that isn't predefined like the other integration-related actions, but which can be used to define a URL path. Using that path for the endpoint you wish to reach in the partner's API allows you to specify data, cookies, headers, etc., for custom targeting beyond what Rewst's other predefined actions allow.
Generic actions rely heavily on your reading the integration's API documentation and researching the endpoints yourself. Most frequently, we suggest this as a feature for more advanced users, though customers with specific goals might be required to use it early on in their onboarding process.
Generic actions are typically named after the integration in the format of `[integration] API Request`. For example, for HaloPSA the action is called `HaloPSA API Request` .
The HaloPSA generic action
{% hint style="warning" %}
Note that the paginate request option in any generic action modifies how the request is formed. This can cause issues on the API's side, causing them to behave unexpectedly and return error messages.
If your integration is missing a generic action and you'd like to see us develop one, add that feedback to our [Canny feedback collector.](https://rewst.canny.io/integrations)
{% endhint %}
## Action version updates
{% hint style="info" %}
Note that this action version functionality won't appear for any actions related to your custom integrations.
{% endhint %}
From time to time, Rewst will make updates to existing actions. These updates may require customers who are using those actions in their workflows to make modifications or adjustments. View the changelog of an action's version history in the left side action list of the [Workflow Builder.](/documentation/automations/workflows/workflow-builder-how-to-set-up-a-workflow.md) If the action in the action list has logged changes, an icon will appear to the right of its name in the list. Click on that icon to expand the version history log.
### Action version log status and alert meanings
| Label | Color | Meaning |
| ---------------- | ------ | -------------------------------------------------------------------------------- |
| Action Required | Red | One or more actions have breaking changes |
| Attention Needed | Yellow | Actions need review, but aren't breaking |
| Updated | Blue | Actions have been updated - no action is required and the alert is informational |
Click links in the action changelog to view additional documentation or guides.
You'll see a red pulsing dot to the right of the **Workflows** section of your left side menu when there are unread breaking changes. \
When workflows in your current organization are affected by version changes, a toolbar will appear in your workflows list page with up to three buttons, each containing the total count of actions in the organization that fall into each alert category. A red pulsing dot will be present next to the Attention Needed category when unread breaking changes exist. Click on any of the categories in the toolbar to filter your workflows list to just that group of workflows. These statuses also apply to the **Attributes** column's filtering capabilities.
## Known actions issues and errors
This collection of issues related to actions have been reported to Rewst by our customers. If you experience an issue with actions that is not in this list, contact us in your dedicated Discord support channel.
{% hint style="success" %}
Click on any of the issues below to expand and see its solution or information.
{% endhint %}
Brave browser
Brave browsers will block the click event on Rewst actions. This is due to the way that Brave handles the click event. To fix this, you can either [disable the Brave shield for the page](https://support.brave.com/hc/en-us/articles/360023646212-How-do-I-configure-global-and-site-specific-Shields-settings), or use a different browser.
ThreatLocker
We have received reports that ThreatLocker may block certain Rewst actions. Threatlocker has a built-in application for Rewst IP addresses that can be added to your Ringfence policy.
To set this up in ThreatLocker:
1. Navigate to **Modules > Application Control**.
2. Click **Policies**.
3. Select **PowerShell Ringfencing Policy**.
4. In the **Actions** section, click **Tags**.
5. Add **Rewst**.
This process may not be necessary if you have already [whitelisted our outgoing IP addresses](https://docs.rewst.help/security/security-policy), but it's something to consider if you run into any issues. Additional steps for whitelisting in ThreatLocker are outlined in this linked document.
UnreachableJoinError: The join task|route "XXXXXXX" is partially satisfied but unreachable.
This error is related to having multiple transitions going to a single action.
1. Click the **Advanced** tab within the action that has multiple transitions going to it.
2. Under the field **Task Transition Criteria***,* you'll likely have a 0. This means that all actions previously have to be complete before that action will run.
3. Change this to the relevant number. For example, change to a 1 so that only one of the previous actions must complete before that action runs.\
\
{% hint style="info" %}
In the image above, the workflow chooses the RMM of the client. Then, depending on the result, it runs a script on that system. The client likely isn't going to have multiple RMMs, so only one of the script tasks is going to run.
However, they all merge into the final **compile\_results** task at the bottom. By default, this workflow will fail, as it is expecting each script task to complete before hitting that final task.
This is where you would change the **Task Transition Criteria Sensitivity** to a `1`. This states that only one of the tasks that come into it must have been completed.
If there was a workflow where you wanted to run on two instances then you would enter `2`, for 2 tasks to be completed.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.rewst.help/documentation/automations/actions-in-rewst.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.