Skip to main content

Input Nodes

Input nodes trigger flows and bring data into your automations. They are the starting points for most workflows.

Input Nodes

Input nodes are the entry points for your flows. They trigger workflows manually, on schedules, or in response to external events like HTTP requests, MQTT messages, or real-time connections.

12 Nodes
4 Protocols
Possibilities

inject

Popular

Triggers a flow manually or at regular intervals. Use for testing and scheduled tasks.

Trigger Manual or automatic
Interval 1s to 24 hours
Repeat Once, interval, or cron
Payload String, number, JSON, timestamp

Configuration

{cfg.key} any Value to inject
{cfg.key} string "str" | "num" | "json" | "date"
{cfg.key} number Interval in seconds
{cfg.key} string Cron expression

Output Example

{node.details.output}
Click the button on the left side of the node to trigger manually.

schedule

Advanced cron-based scheduling with timezone support for complex timing requirements.

Cron 5-field or 6-field format
Timezone Full IANA support
Schedules Up to 10 per node
Date Range Optional start/end

Configuration

{cfg.key} string "0 9 * * 1-5" (weekdays 9am)
{cfg.key} string "America/New_York"
{cfg.key} string ISO date (optional)
{cfg.key} any Custom payload

Output Example

{node.details.output}
Supports sunrise/sunset triggers with location configuration.

mqtt-in

Popular

Subscribe to MQTT topics and receive messages from IoT brokers.

Protocol MQTT 3.1.1 and 5.0
QoS 0, 1, or 2
Wildcards + (single), # (multi)
Security TLS/SSL, certificates

Configuration

{cfg.key} string mqtt://host:1883
{cfg.key} string sensors/+/temp
{cfg.key} number 0, 1, or 2
{cfg.key} string Auth username

Output Example

{node.details.output}
Use QoS 1 for important messages that must be delivered.

http-in

Popular

Create HTTP endpoints to receive webhooks and API requests.

Methods GET, POST, PUT, DELETE
Content JSON, form-data, binary
Routing Path params /users/:id
CORS Configurable

Configuration

{cfg.key} string "GET" | "POST" | "PUT"
{cfg.key} string "/api/webhook"
{cfg.key} boolean Enable file uploads
{cfg.key} string "none" | "basic" | "bearer"

Output Example

{node.details.output}
Pair with http-response node to send replies back to clients.

websocket-in

Receive real-time messages over WebSocket connections.

Mode Server or Client
Protocol WS and WSS (secure)
Reconnect Auto-retry logic
Heartbeat Ping/pong keep-alive

Configuration

{cfg.key} string "server" | "client"
{cfg.key} string "/ws" (server mode)
{cfg.key} string "wss://example.com/socket"
{cfg.key} number Retry interval (ms)

Output Example

{node.details.output}
Session ID tracks individual connections for targeted responses.

tcp-in

Listen for incoming TCP connections and receive data streams.

Mode Server or Client
Delimiter Newline, null, custom
Encoding UTF-8, ASCII, binary
Keep-alive TCP keep-alive support

Configuration

{cfg.key} string "server" | "client"
{cfg.key} string IP address to bind
{cfg.key} number TCP port number
{cfg.key} string "\n" | "\0" | length

Output Example

{node.details.output}
Use delimiter to split incoming streams into separate messages.

udp-in

Receive UDP datagrams for high-speed, connectionless data transfer.

Mode Unicast or Multicast
Max Size 65,507 bytes
Multicast Join group address
Protocol Stateless (no connection)

Configuration

{cfg.key} number UDP port to listen
{cfg.key} string Multicast group (optional)
{cfg.key} string Network interface
{cfg.key} string "buffer" | "string"

Output Example

{node.details.output}
Lower latency than TCP, but no delivery guarantee.

Common Use Cases

Testing & Debugging

Use inject to manually trigger flows and test your logic with different payloads.

IoT Data Collection

Use mqtt-in to subscribe to sensor topics and collect real-time device data.

Webhook Endpoints

Use http-in to receive webhooks from external services like GitHub or Stripe.

Scheduled Automation

Use schedule for cron-based tasks like daily reports or periodic data sync.