Call Mesh action
Communicate with a Mesh endpoint
Use the Call Mesh action to contact an Alloy Mesh endpoint.
Data can be sent to a Push Mesh endpoint (e.g. AWS IoT, Telensa) or received from a Pull Mesh endpoint (e.g. Street Manager, SupaTrak).
All Meshes require a corresponding module to be installed and configured on your customer project.
Details
| Icon | Action | Description | Availability | Input | Output |
|---|---|---|---|---|---|
| Call Mesh | Contact a Push or Pull Mesh endpoint | Always | Item(s) from the previous node | None (Push) The endpoint's response (Pull) |
Configuration
To configure a Call Mesh action node when building a workflow:
- Add a new action. Alternatively, select an existing action, and then select Edit in the action bar.
-
In the right panel, fill in the following fields as needed:
-
Action description - write an optional description of what this action does.
-
Mesh * - choose from the list of available Meshes.
-
Single Instance - if enabled, the action will always be performed once, no matter how many input items there are. Multiple input items will be processed in one go, rather than contacting the Mesh multiple times. This is recommended for Pull Mesh actions, as they're typically used in schedule workflows that trigger with no input items.
-
-
Select Validate to check if the action can be saved as configured. A notification will appear to indicate success or failure.
- If successful, select Save to finish.
Dynamic values
Fields marked with can accept a dynamic value:
- Constant - select or enter static values.
- Offset - set a date/time relative to when the workflow triggers.
- Link - link to the corresponding output of any preceding stage in the current branch path (one item).
- Output - reference the total output of any action in the sequence (one or more items).
If an action attribute displays as <<Computed>>, its value is determined by the output of a workflow computation. If you enter a new value and save, the computation will be overwritten!