List of Workflow Nodes

Below is a list of all workflow nodes available in WEGnology’s cloud platform, in the Gateway Edge Agent, and in the Embedded Edge Agent. Nodes are broken down by category and can be filtered by their availabity for a given workflow class.

To learn more about a node, click its name to view detailed documentation and examples.

Triggers

• Amazon SQS Trigger

  The Amazon SQS Trigger fires a workflow whenever a WEGnology integration receives an Amazon Simple Queue Service (SQS) message.

• Application: Sync Trigger

  The Application: Sync Trigger fires a workflow whenever the Gateway Edge Agent receives updated peripherals, global values, or changes to its Edge Compute device configuration.

• Azure Event Hubs Trigger

  The Azure Event Hubs Trigger fires a workflow whenever a WEGnology integration receives an Azure Event Hubs message.

• Beckhoff Trigger

  The Beckhoff Trigger fires a workflow whenever monitored symbols on a Beckhoff TwinCAT PLC receive new values.

• Data Table Trigger

  The Data Table Trigger fires a workflow whenever a row is added, updated, or removed from a WEGnology Data Table.

• Device: Command Trigger

  The Device: Command Trigger fires a workflow whenever its Edge Compute or Embedded Device receives a command over the MQTT broker.

• Device: Connect Trigger

  The Device: Connect Trigger fires a workflow whenever one or more devices connect to the WEGnology Platform.

• Device: Create Trigger

  The Device: Create Trigger fires a workflow whenever a device is created within your application.

• Device: Disconnect Trigger

  The Device: Disconnect Trigger fires a workflow whenever one or more devices disconnect from the WEGnology Platform.

• Device: Inactive Trigger

  The Device: Inactive Trigger fires a workflow whenever one or more devices do not report state for the configured period of time.

• Device: Startup Trigger

  The Device: Startup Trigger fires a workflow whenever the Gateway Edge Agent starts or restarts.

• Device: State Trigger

  The Device: State Trigger fires a workflow whenever a device reports state to the WEGnology cloud platform.

• Direct Trigger

  The Direct Trigger fires an Embedded Workflow whenever the "eea_direct_trigger" method is invoked within the Embedded Edge Agent.

• EEA: Init Trigger

  The EEA: Init Trigger fires a workflow whenever the "eea_init" function is called within the Embedded Edge Agent.

• Email Trigger

  The Email Trigger fires a workflow whenever your application receives an email at its address or a subaddress.

• Endpoint Trigger

  The Endpoint Trigger fires a workflow when the selected Experience Endpoint receives an HTTP request.

• Event Trigger

  The Event Trigger fires a workflow whenever an event matching the criteria defined in the trigger's configuration is created or changes state.

• File Tail Trigger

  The File Tail Trigger allows you to monitor and analyze logs and other files on the Gateway Edge Agent's container or host file system.

• File Trigger

  The File Trigger allows you to fire a workflow when a file is created, modified, or deleted from a directory in your Application Files.

• File Watch Trigger

  The File Watch Trigger fires a workflow whenever the file or directory changes are observed on the Gateway Edge Agent.

• GCP Pub/Sub Trigger

  The GCP Pub/Sub Trigger fires a workflow whenever a message is sent to a WEGnology GCP Pub/Sub integration.

• GCP Pub/Sub Trigger Node

  The GCP Pub/Sub Trigger fires a workflow whenever a message is sent to a WEGnology GCP Pub/Sub integration.

• HTTP Request Trigger

  The HTTP Request Trigger fires a workflow whenever the Gateway Edge Agent receives a request on its local web server.

• Job: Complete Trigger

  The Job: Complete Trigger fires a workflow whenever a Resource Job completes all iterations or is canceled during execution.

• Job: Iteration Trigger

  The Job: Iteration Trigger fires a workflow whenever an iteration of a Resource Job begins.

• Job: Timeout Trigger

  The Job: Iteration Timeout Trigger fires a workflow whenever an iteration of a Resource Job is not acknowledged before the Resource Job’s configured timeout.

• MQTT Trigger

  The MQTT Trigger fires a workflow whenever a message is published to a topic on the WEGnology MQTT Broker, the Gateway Edge Agent Local Broker, an external broker, or an MQTT integration.

• Notebook Trigger

  The Notebook Trigger fires a workflow whenever the selected WEGnology Notebook has completed an execution, either successfully or with errors.

• OPC UA Trigger

  The OPC UA Trigger fires a workflow whenever an Edge Compute Device receives a change message on the configured OPC UA monitored node.

• OPC UA Trigger Node

  The OPC UA Trigger fires a workflow whenever an Edge Compute Device receives a change message on the configured OPC UA monitored node.

• Particle Trigger

  The Particle Trigger fires a workflow whenever an event is received on the WEGnology Particle integration.

• Redis Trigger

  The Redis Trigger fires a workflow whenever the Edge Compute Device receives a message on the configured Redis Pub/Sub channel.

• Serial Trigger

  The Serial Trigger fires a workflow whenever the Edge Compute Device receives data over a Serial connection.

• SNMP: Trap Trigger

  The SNMP: Trap Trigger fires a workflow whenever the Edge Compute Device receives an SNMP trap message or an SNMP inform request.

• Timer Trigger

  The Timer Trigger fires a workflow on a scheduled interval.

• UDP Message Trigger

  The UDP Message Trigger fires a workflow whenever the Edge Compute Device receives a UDP datagram on the configured port.

• Virtual Button Trigger

  The Virtual Button Trigger fires a workflow when the "virtual button" is pressed.

• Webhook Trigger

  The Webhook Trigger fires a workflow whenever a WEGnology webhook receives an HTTP request or WebSocket message.

• WebSocket Trigger

  The WebSocket Trigger fires a workflow whenever a WEGnology WebSocket integration receives a message.

• Workflow Error Trigger

  The Workflow Error Trigger fires a workflow whenever a halting error occurs in a separate workflow execution.

Debug Nodes

• Debug Node

  The Debug Node prints out the current payload and execution timing info at the point of invocation within a workflow run.

• Throw Error Node

  The Throw Error Node halts a workflow execution, logs the provided error message, and fires any associated Workflow Error Triggers.

Experience Nodes

• Authenticate Experience User Node

  The Authenticate Experience User Node authenticates an email and password against Experience Users in a WEGnology application.

• Device: Verify Node

  The Device: Verify Node checks whether a given device is associated with an Experience Group or Experience User in a WEGnology application.

• Generate Experience User Token Node

  The Generate Experience User Token Node creates a token for an Experience User to make authorized requests against Experience Endpoints.

• Group: Create Node

  The Group: Create Node adds a new Experience Group to a WEGnology application.

• Group: Get Node

  The Group: Get Node retrieves one or more Experience Groups from a WEGnology application.

• Group: Summary Node

  The Group: Summary Node retrieves Experience Groups in a hierarchical tree format.

• Group: Update Node

  The Group: Update Node updates an existing Experience Group within a WEGnology application.

• Group: Verify Node

  The Group: Verify Node checks whether a given Experience User is a member of an Experience Group or any of the group's children.

• SAML: Login URL Node

  The SAML: Login URL Node creates a login URL for a Security Assertion Markup Language 2.0 (SAML) single sign-on (SSO) identity provider.

• SAML: Verify Node

  The SAML: Verify Node verifies and extracts response data from a Security Assertion Markup Language 2.0 (SAML) single sign-on (SSO) identity provider.

• User: Create Node

  The User: Create Node adds a new Experience User to a WEGnology application.

• User: Delete Node

  The User: Delete Node removes an Experience User from a WEGnology application.

• User: Get Node

  The User: Get Node retrieves one or more Experience Users from a WEGnology application.

• User: Update Node

  The User: Update Node updates an existing Experience User within a WEGnology application.

Logic Nodes

• Array Node

  The Array Node performs operations against an array-type value on the payload.

• Base64: Decode Node

  The Base64: Decode Node takes a Base64-encoded string and decodes it as a binary array.

• Base64: Encode Node

  The Base64: Encode Node takes a string or binary array and encodes it to a Base64 string.

• CBOR: Decode Node

  The CBOR: Decode Node takes a CBOR-encoded value on the payload and converts it into a JSON object.

• CBOR: Encode Node

  The CBOR: Encode Node converts a JSON object into Concise Binary Object Representation format.

• Conditional Node

  The Conditional Node branches a workflow based on the result of an expression.

• CSV: Decode Node

  The CSV: Decode takes a CSV string and decodes it into an object array.

• CSV: Encode Node

  The CSV: Encode Node takes an object array and encodes it into a CSV string.

• Date/Time Node

  The Date/Time Node allows for parsing and manipulating dates and timestamps.

• Delay Node

  The Delay Node pauses a workflow execution for a short period of time.

• Fast Fourier Transform Node

  The Fast Fourier Transform Node takes an array of data points from one domain and converts it into a frequency representation using a fast Fourier transform algorithm.

• Function Node

  The Function Node allows execution of arbitrary, user-defined JavaScript.

• Generate ID Node

  The Generate ID Node creates IDs in UUID, Object ID, or Nano ID format.

• Geofence Node

  The Geofence Node branches a workflow based on whether a given geographic point is within a defined area.

• Hash Node

  The Hash Node creates a cryptographic hash through a variety of algorithms.

• HTML/XML Parser Node

  The HTML/XML Parser Node takes an HTML or XML document string and parses it into a traversable tree.

• JSON: Decode Node

  The JSON: Decode Node takes a JSON string and parses it into an object.

• JSON: Encode Node

  The JSON: Encode Node takes an object and converts it into a JSON string.

• JWT: Create Node

  The JWT: Create Node generates a JSON Web Token from a JSON payload, optional headers, and a secret.

• JWT: Decode Node

  The JWT: Decode Node takes a JSON Web Token and decodes it to an object.

• JWT: Verify Node

  The JWT: Verify Node branches a workflow based on whether a provided JSON Web Token is valid.

• Latch Node

  The Latch Node allows for easy "one-time" branching of a workflow, with the ability to reset the branch condition.

• Loop Node

  The Loop Node allows for iterating over values on your payload, or for performing a certain operation a set number of times.

• Math Node

  The Math Node performs expression-based mathematical calculations.

• Mutate Node

  The Mutate Node modifies, moves, copies, or removes values from a workflow payload.

• Object Node

  The Object Node performs operations against objects or arrays on the payload.

• On Change Node

  The On Change Node branches a workflow based on whether a value has changed since previous executions of the workflow.

• Random Number Node

  The Random Number Node generates a random integer within a range of your choosing.

• Root Mean Square Node

  The Root Mean Square Node calculates the root mean square (RMS) of an array of numbers.

• Rust Function Node

  The Rust Function Node allows for execution of user-defined Rust code.

• String Node

  The String Node allows for manipulating string values.

• Switch Node

  The Switch Node branches across many different paths based on matching a switch statement against various case values.

• Throttle Node

  The Throttle Node branches a workflow based on the amount of time that has passed since the last execution of the node.

• Time Range Node

  The Time Range Node branches based on whether a given timestamp is within a provided time range.

• Validate Payload Node

  The Validate Payload Node branches a workflow based on whether a given value validates against a provided JSON schema.

Data Nodes

• Access Key: Create Node

  The Access Key: Create Node generates a new Access Key for authenticating against the WEGnology MQTT Broker.

• Agent Config: Get Node

  The Agent Config: Get Node retrieves configuration settings for an instance of the Gateway Edge Agent.

• Agent Config: Set Node

  The Agent Config: Set Node changes configuration settings for an instance of the Gateway Edge Agent.

• Allen-Bradley: Read Node

  The Allen-Bradley: Read Node reads multiple tags from an Allen-Bradley CompactLogix or ControlLogix programmable logic controller (PLC).

• Allen-Bradley: Write Node

  The Allen-Bradley: Write Node writes to multiple tags on an Allen-Bradley CompactLogix or ControlLogix programmable logic controller (PLC).

• Athena Request: Post Node

  The Athena Request: Post Node is a connector to AWS Athena where you can perform serverless interactive queries that allow users to analyze data directly in Amazon S3 using standard SQL.

• AWS Lambda Node

  The AWS: Lambda Node executes an AWS Lambda function and optionally returns the result.

• AWS S3: Get Node

  The AWS S3: Get Node retrieves a file and its metadata from an Amazon S3 bucket.

• AWS S3: Put Node

  The AWS S3: Put Node uploads a file into an Amazon S3 bucket.

• AWS Signature

  The AWS Signature that Returns the Signature Version 4

• Azure Blob: Get Node

  The Azure Blob: Get Node retrieves a file and its metadata from an Azure Blob Storage container.

• Azure Blob: Put Node

  The Azure Blob: Put Node uploads a file to an Azure Blob Storage container.

• Azure: Function Node

  The Azure: Function Node executes an Azure Function and optionally returns the result.

• Azure: Table Storage Node

  The Azure: Table Storage Node allows you to perform entity operations on an Azure Data Table.

• BACnet: Read Node

  The BACnet: Read Node reads multiple properties across multiple objects from a BACnet device.

• BACnet: Who-Is Node

  The BACnet: Who-Is Node broadcasts a Who-Is message and awaits I-Am replies from BACnet-compatible devices on a network.

• BACnet: Write Node

  The BACnet: Write Node writes multiple properties in multiple objects on a BACnet device.

• Beckhoff: Read Node

  The Beckhoff: Read Node reads multiple symbol values from a Beckhoff TwinCAT PLC.

• Beckhoff: Write Node

  The Beckhoff: Write Node allows for writing values to one or more symbols on a Beckhoff TwinCAT PLC.

• Data: Gauge Query Node

  The Data: Gauge Query Node retrieves aggregate state data for one or more attributes across one or more devices.

• Data: Time Series Node

  The Data: Time Series Node retrieves state data across a time period for one or more attributes across one or more devices.

• Device: Create Node

  The Device: Create Node adds a new device to a WEGnology application.

• Device: Delete Node

  The Device: Delete Node removes one or more devices from a WEGnology application.

• Device: Get Node

  The Device: Get Node retrieves one or more devices from a WEGnology application.

• Device: Update Node

  The Device: Update Node updates an existing device within a WEGnology application.

• Event: Create Node

  The Event: Create Node generates a new event within a WEGnology application.

• Event: Delete Node

  The Event: Delete Node removes one or more events from a WEGnology application.

• Event: Get Node

  The Event: Get Node retrieves one or more events from a WEGnology application.

• Event: Update Node

  The Event: Update Node updates one or more existing events within a WEGnology application.

• File: Create Node

  The File: Create Node creates a file within a WEGnology application's files.

• File: Read Node

  The File: Read Node retrieves a file from disk on an Edge Compute Device.

• File: Write Node

  The File: Write Node writes a file to disk on an Edge Compute Device.

• FTP: Get Node

  The FTP: Get Node retrieves a file from an FTP or SFTP server.

• FTP: Put Node

  The FTP: Put Node uploads a file to an FTP or SFTP server.

• GCP Storage: Get Node

  The GCP Storage: Get Node retrieves a file and its metadata from a Google Cloud Storage bucket.

• GCP Storage: Put Node

  The GCP Storage: Put Node uploads a file to a Google Cloud Storage bucket.

• GCP: BigQuery Node

  The GCP: BigQuery Node makes requests to a Google BigQuery table.

• GCP: Function Node

  The GCP: Function Node executes a Google Cloud Function and optionally returns a result.

• GCP: ML Node

  The GCP: ML Node sends data to Google ML and retrieves predictions based on models in that service.

• HTTP Node

  The HTTP Node makes arbitrary HTTP requests to third-party services.

• Loggly: Write Node

  The Loggly: Write Node sends one or more messages to SolarWinds Loggly

• Modbus: Read Node

  The Modbus: Read Node reads multiple registers from Modbus-enabled PLCs.

• Modbus: Write Node

  The Modbus: Write Node writes to multiple registers on Modbus-enabled PLCs.

• MongoDB Node

  The MongoDB Node runs queries against a MongoDB database.

• OPC UA: Browse Node

  The OPC UA: Browse Node allows for browsing node folders on an OPC UA Server.

• OPC UA: Call Node

  The OPC UA: Call Node calls a method on an object within an OPC UA Server and connected programmable logic controller (PLC).

• OPC UA: Read Node

  The OPC UA: Read Node retrieves multiple node values from an OPC UA Server and connected programmable logic controller (PLC).

• OPC UA: Write Node

  The OPC UA: Write Node writes multiple node values to an OPC UA Server and connected programmable logic controller (PLC).

• Peripheral: Get Node

  The Peripheral: Get Node retrieves one or more of an Edge Compute Device's associated Peripheral Devices.

• Redis Node

  The Redis Node queries or updates values in a Redis database.

• Registered Function Node

  The Registered Function Node invokes a registered function defined on an Embedded Device.

• Run Executable Node

  The Run Executable Node runs a script or process locally on an Edge Compute Device.

• Salesforce Cases Node

  The Salesforce Cases Node accesses the Salesforce Service Cloud to create, read, update, or delete cases in their CRM platform.

• Serial: Write Node

  The Serial: Write Node writes values to a specified serial port.

• ServiceNow Node

  The ServiceNow Node create, updates, and retrieves records from tables in the ServiceNow platform.

• Siemens S7: Read Node

  The Siemens S7: Read Node allows you to read one or more values from a PLC that supports the Siemens S7 protocol.

• Siemens S7: Write Node

  The Siemens S7: Write Node allows you to write one or more values to a PLC that supports the Siemens S7 protocol.

• SNMP: Get Subtree Node

  The SNMP: Get Subtree Node reads values beneath a root OID on an SNMP device.

• SNMP: Read Node

  The SNMP: Read Node reads values from multiple OIDs on an SNMP device.

• SNMP: Write Node

  The SNMP: Write Node writes values to one or more OIDs on an SNMP device.

• SQL Node

  The SQL Node queries or updates values in an SQL database.

• Storage: Get Value Node

  The Storage: Get Value Node retrieves a value set by a Storage: Set Value Node in a previous workflow execution.

• Storage: Set Value Node

  The Storage: Set Value Node stores a value for use in a subsequent workflow execution.

• Table: Delete Rows Node

  The Table: Delete Rows Node deletes one or more rows from a WEGnology Data Table.

• Table: Get Rows Node

  The Data Table: Get Rows Node retrieves one or more rows from a WEGnology Data Table.

• Table: Insert Rows Node

  The Data Table: Insert Row Node adds one or more new rows to a WEGnology Data Table.

• Table: Update Row Node

  The Table: Update Row Node updates an existing row in a WEGnology Data Table.

• TensorFlow: Predict Node

  The TensorFlow: Predict Node makes predictions against a pretrained TensorFlow model that has been loaded onto an Edge Compute Device.

• WEGnology API Node

  Learn more about the WEGnology API Node.

Output Nodes

• Amazon SQS Node

  The Amazon SQS Node publishes a message to an Amazon SQS queue.

• Azure Event Hubs Node

  The Azure Event Hubs Node publishes a message to an Azure Event Hub.

• Debug Node

  The Debug Node prints out the current payload and execution timing info at the point of invocation within a workflow run.

• Device: Command Node

  The Device: Command Node sends a command to one or more devices connected to the WEGnology MQTT Broker.

• Device: State Node

  The Device: State Node records telemetry data as attributes for a device.

• Email Node

  The Email Node sends an email to one or more users through WEGnology's provided email delivery.

• Endpoint: Reply Node

  The Endpoint Reply Node sends a response to an Experience Endpoint HTTP request.

• GCP Pub/Sub Node

  The GCP (Google Cloud Platform) Pub/Sub Node publishes a message to a Google Pub/Sub topic.

• HTTP Node

  The HTTP Node makes arbitrary HTTP requests to third-party services.

• HTTP Response Node

  The HTTP Response Node sends a response to an HTTP request received by an Edge Compute Device's local web server.

• Job: Acknowledge Node

  The Job: Acknowledge Node marks an iteration of a Resource Job as a success or failure.

• Job: Execute Node

  The Job: Execute Node requests an execution of one of your application’s Resource Jobs.

• Mailgun Node

  The Mailgun Node sends emails through a given Mailgun account.

• MQTT Node

  The MQTT Node publishes a message to the WEGnology MQTT Broker, the Gateway Edge Agent Local Broker, an external broker, or an MQTT integration.

• Notebook: Execute Node

  The Notebook: Execute Node initiates an execution of a WEGnology Notebook.

• Particle Call Node

  The Particle Call Node invokes a remote function on a device within Particle.

• SendGrid Node

  The SendGrid Node sends emails through a given SendGrid account.

• Slack Node

  The Slack Node sends messages to a given channel within a Slack workspace.

• SMS Node

  The SMS Node sends an SMS message through WEGnology's provided SMS delivery service.

• Telegram Node

  The Telegram Node sends a message to a specific Telegram chat.

• Twilio Node

  The Twilio Node sends SMS messages using the configured Twilio account.

• UDP Send Node

  The UDP Send Node sends a UDP datagram to a given address and port.

• Webhook: Reply Node

  The Webhook: Reply Node sends a response to an HTTP request received by a WEGnology Webhook.

• WebSocket Message Node

  The WebSocket Message Node publishes a message to a WebSocket integration.

• WhatsApp Node

  The WhatsApp Node allows you to send messages using your WhatsApp Business account.

• Workflow Trigger Node

  The Workflow Trigger Node invokes another workflow execution with a custom payload.