Input Protocol + IoT Connector Nodes
      Back to home
      1. Home
      2. 5: Automation & Workflows
      3. Input Protocol + IoT Connector Nodes

      Trigger Node Configuration Guide

      The Trigger Node initiates workflow execution by generating and emitting payloads at defined time intervals, either globally or per UID. It acts as a scheduled input mechanism, supporting use cases such as periodic polling, timed rule evaluation, or

      What It Does

      This node automatically emits a payload into the workflow at regular intervals. Each execution can optionally include a payload template, be formatted as JSON, and be repeated across selected UIDs with delay spacing between them.

      Step-by-Step: How to Configure the Trigger Node

      1. Add the node

        • Drag the Trigger Node from the Inputs section onto the canvas.

      2. Open the configuration panel

        • Double-click the node to set up the interval, payload format, and filters.

      3. Define output payload (optional)

        • You can leave the output blank or define a fixed structure.

      4. Connect downstream logic

        • Any connected nodes will receive the trigger's output as their input.

      Configuration Fields

      General Settings

      Field Requirement Description
      Node Name* Required Logical name of the node in the workflow.
      Trigger Interval* Required Time value that determines how often the trigger fires (e.g., 10).
      Interval Units* Required Select time units: Seconds, Minutes, Hours, Days, etc.
      Output Payload Format* Required Format of the output: currently JSON.
      Output Payload Optional The body of the payload to emit. This can be an empty object {} or any JSON key-value structure.
      Interval Between Each UID (ms)* Optional Adds a delay between payloads emitted per UID. Useful to avoid congestion. Default: 1000 ms.
       

      Activation Filters

      Field Description
      Logical Operand AND / OR for combining multiple filters.
      Select Data Source Filter Apply the trigger only to selected UIDs or device label groups. This causes the trigger to emit one payload per matching UID.
       

      Output Example

      Config:

      • Output Payload:

        json
        CopyEdit
        { "event": "poll", "status": "pending" }

      • UIDs: device-01, device-02

      • Interval: every 10 minutes

      • Interval between UIDs: 1000 ms

      Resulting Output:

       
      { "uid": "device-01", "event": "poll", "status": "pending" }

      (1 second delay)

       
      { "uid": "device-02", "event": "poll", "status": "pending" }

      Best Practices

      • Keep the payload size minimal unless sending fixed metadata.

      • Use the UID filter for per-device periodic processing (e.g., polling sensors or APIs).

      • Increase the inter-UID interval if your downstream system has rate limits.

      • Combine with a Rule Builder or External API node for periodic decision logic.

      Use Cases

      • Schedule regular API calls or workflow evaluations

      • Send synthetic payloads for testing or simulation

      • Trigger alerts, checks, or conditional updates every hour/day

      • Emit keep-alive messages or data snapshots at fixed times

      FAQ

      Q: Does this node require an input?

      A: No. The Trigger Node is an input node — it emits data on its own based on schedule.

      Q: Can I include dynamic values in the payload?

      A: No — this node emits static payloads. For dynamic content, combine it with logic or scripting nodes downstream.

      Q: Does it support cron expressions?

      A: Not currently. Time is configured in terms of fixed units and intervals only.