Automated Actions

The steps available in the cloud_queue Automated Actions category are displayed on the figures below:

info

The picture may not show the full scope of workflow steps available in this menu. Some steps become available only after the corresponding integration is configured in evalink talos.

Set Status

The swap_vertSet Status step can be used to set a site status to one of its configured states.

This is an option for statuses that have their state changes triggered not by the connected equipment, but by other sources – for example, by SMS received through Virtual SMS Receiver.

warning

For statuses that listen to physical devices (such as alarm panels), setting status states via a workflow is not recommended. If a state change is triggered from a workflow, the evalink talos state of the status and its real state on the alarm panel may diverge.

For example, you can have a workflow that sets the Arm status of the connected alarm panel to Armed. After the workflow runs, the evalink talos status state switches to Armed, while the status state on the panel does not change.

An example of a configured swap_vertSet Status step in the workflow editor (see section Operations with a Workflow > Work with Workflow Steps > Workflow Editor) is shown on the figure below:

To configure the step, add it to the workflow and fill out these fields in the step details:

1. (Optional) In the Title field, specify the step title

2. In the Status field, select one of the configured site statuses from the list

   The list displays the statuses configured for the current site and the Status Roles.

   When configuring a site-level workflow, select a regular status. When configuring a higher-level workflow (a site group or a global workflow), consider selecting a Status Role. The rationales for using Status Roles are described in section Advanced Features in evalink talos > Use of Roles.

   warning

   Make sure to assign a Status Role to a status on the site level. If the role is not assigned, when the workflow runs, an execution error will occur. For details on how roles are used and configured, see section Advanced Feature in evalink talos > Use of Roles > Using Roles in Workflows: Required Setup.

3. In the State field, select the state of the status that needs to be set

Trigger Webhooks as Part of a Workflow

The Trigger Webhook automated action allows you to work with evalink talos API or third-party APIs in WYSIWYG mode and without profound API knowledge. Using this action, you can call different APIs in order to retrieve, edit, add and delete data for their endpoints.

You can use this step in manual and automated workflows.

To trigger a webhook as part of a workflow:

1. Create a workflow or open an existing one to edit

   info

   For more information about creating workflows, see section Add a Workflow.

2. When adding steps, select Trigger Webhook from Automated Actions

   

3. (Optional) Add the Webhook Trigger name in the Title field

4. In the Webhook URL field, add the URL of the webhook you want to trigger

   info

   For example, you can use this webhook URL https://api.open-meteo.com/v1/forecast?latitude=37.9792&longitude=23.7166&current_weather=true to retrieve a weather forecast for Athens.

5. In the Http Method dropdown, select one of the following:

   • GET - retrieves data from the endpoint. The response can be post-processed in the workflow
   • DELETE - deletes a resource at the endpoint
   • POST - adds data to the endpoint
   • PUT - updates data at the endpoint
   • PATCH - partially updates data at the endpoint

6. (Optional) In the Url Parameters tab, enter any required URL parameters as key-value pairs and click Add

7. (Optional) In the Headers tab, specify any required request headers as key-value pairs and click Add

   info

   If you are calling an evalink talos API endpoint, your API keys can be accessed in Company > Integrations > API Tokens

8. (Optional) In the Authentication tab, configure authentication for the endpoint:

   • In the Authentication dropdown, select one of the following:

     • None - no authentication is used. This is the default
     • Digest - enter the Username and Password required by the endpoint
     • mTLS - paste a PEM bundle that includes your client certificate and private key into the Client Certificate (PEM) field

9. (Optional) In the Response tab, configure how the response is processed:

   • In the Response JSON Path field, enter a JSONPath expression to extract a specific value from the response body. When set, only the extracted value is returned by the step and passed forward in the workflow — useful when the full response body is large and only a specific field is needed. Click the JSON path syntax link in the field for reference.

   • In the Response headers to extract area, enter header names in the Key field and click Add to capture specific response headers — for example, cookies or custom headers returned by the endpoint — and make them available for use later in the workflow.

10. Save the workflow

---

coming soon

More workflow steps will be described in future documentation releases.