Sources
A Source is a named, reusable trigger endpoint: a platform preset plus its connection config and a placement. Sources are the opposite end of the pipeline from Sinks: sources create events, sinks execute the tasks those events trigger.
Creating a Source
Section titled “Creating a Source”Create a source in the flow builder (“New source…”) or on the Sources screen:
- Pick a preset from the catalog.
- Fill the connection config — the fields the preset declares (broker address, credentials, cron).
SECRETfields resolve from the Secrets store at runtime; the value never leaves the platform unencrypted. - Place it — on a specific source node, or on the platform. Sources are inherently location-bound: a folder watcher watches that folder, a webhook listens on that address.
- Name it — flows reuse the source by name.
Per-flow trigger settings (watch paths, topics, trigger rows) are configured on the flow’s WHEN line, per source block; the cron itself lives on the schedule source’s connection config — editing the source updates every flow using it.
Built-In Presets
Section titled “Built-In Presets”| Preset | Where it runs | How it triggers |
|---|---|---|
| Webhook | Platform or a source node | An HTTP POST to a unique URL creates an event. Each webhook source gets its own endpoint |
| Every day at… | Platform or a source node | A cron expression fires the flow on a repeating schedule. The cron lives on the source — editing the source updates every flow using it. There is no separate Schedules screen |
| Azure EventGrid | Platform | Messages from an Azure Event Grid topic subscription become events |
| MCP | A source node | AI agents using the Model Context Protocol create events directly. See the MCP Server guide for setup |
| Folder watch | Platform or a source node | A file appearing or changing in watched paths (local folder or SMB share) creates an event. Paths are per flow, on the WHEN line. The platform’s own .lock and .track artifacts never fire the trigger, and a fully-tracked file (track position at the file’s size) is not re-fired when the watcher restarts with no memory — only appended bytes fire again, as a change event |
| MQTT | Platform or a source node | A message arriving on a subscribed MQTT topic creates an event. Broker connection lives on the source; topics are per flow |
Full details: preset catalog.
Self-Hosted Sources: One Node Service
Section titled “Self-Hosted Sources: One Node Service”All self-hosted sources — folder watch, MQTT, and webhook — run through a single node service installed on your machine, separate from anything platform-hosted. The webhook preset is unified: the same source type serves platform-hosted webhooks and webhooks pinned to your own node, with the same token/signature security:
- Install once — that one service serves every self-hosted flow whose source is placed on that node. Each flow runs as its own supervised worker inside the service, so one failing flow never takes down another.
- New presets arrive by updating the node — the platform releases new engines in batched packs; your node updates itself through the normal node update flow. No new installers or services, ever.
- Keep the service updated — when a flow needs an engine your node version doesn’t have yet, it won’t produce events until you update.
Installation guides: Source Node overview, Windows, Linux.
Triggering a Webhook
Section titled “Triggering a Webhook”Every flow using a Webhook source can be triggered over HTTP. The flow’s UUID is its webhook address — the flow editor shows the complete address once the flow is saved.
The request
Section titled “The request”POST <webhook-node-host>/<tenant-uuid>/<flow-uuid>
Content-Type: application/json
{ "type": "anything-you-like", "data": { "field": "value", ... }}<tenant-uuid>— your tenant’s UUID (shown in the flow editor’s webhook hint)<flow-uuid>— the flow’s webhook address<webhook-node-host>— the platform’s webhook endpoint host. When the platform hosts the webhook node, the flow editor shows the complete URL directly; otherwise ask your platform administrator for the public host
A 201 Created response means the event was registered and queued. Follow it on the Runs screen.
Required fields
Section titled “Required fields”Every DATA parameter on the flow’s entry action must be present in data — those are the fields the action reads from the payload at runtime. A payload missing one of them is rejected with 422 (“Missing required fields for this event type”). STATIC and SECRET parameters are supplied by the platform, never by the payload.
Authentication
Section titled “Authentication”The Webhook preset ships with security-first defaults — POSTs must carry both a valid token and a valid signature (see the defaults table below). The two mechanisms:
- Token: request one with
GET <webhook-node-host>/<tenant-uuid>/<flow-uuid>/token?type=<anything-you-like>, then append?token=<token>to the POST. The token is computed from the flow UUID and thetypevalue, so keep thetypestable. - Signature (svix/standard-webhooks): POSTs must carry the standard
webhook-id,webhook-timestamp, andwebhook-signatureheaders, verified against the source’sWH_SIGNATURE_SECRET.
Securing your webhook source
Section titled “Securing your webhook source”The platform’s Webhook preset ships with security-first defaults, so webhook sources require both a token and a signature by default:
| Param | Default | Meaning |
|---|---|---|
ALLOW_UNSIGNED_REQUESTS | false | Reject POSTs without a valid signature header set |
ALLOW_UNAUTHENTICATED_REQUESTS | false | Reject POSTs without a valid token or signature |
WH_SIGNATURE_SECRET | secret://nx-secret/webhook-signing-secret | The secret used to verify signatures |
To point the signature param at your own secret: add one on the Secrets screen (the value is write-only), then set the param’s value to its secret://nx-secret/<key> URI. A request missing either check is rejected with 403.