Send Message

output.send-message Output v0.1.0

Sends a normalized message to Gmail, Slack, Telegram, Discord, or a generic webhook endpoint.

Finding it in the library

Search the builder's node library for Send Message (it lives under Output). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Library capture pending — regenerate with npm run shots:nodes.

Wired up in the builder

Send Message in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

Canvas capture pending — regenerate with npm run shots:nodes.

How it’s configured

The node’s Configure panel as it opens in the builder when you select the step — every setting laid out with real values. Click any field to edit it.

Config capture pending — regenerate with npm run shots:nodes. See the full property reference below.

Ports

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

Direction	Port	Label
Input	`input`	Input
Output	`sent`	Sent
Output	`error`	Error

How data flows through it

Send Message consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

Expressions in the config

String-typed properties accept {{ }} expressions evaluated against the incoming item at run time — e.g. {{ $json.customer.email }}. On this node that’s url, targetUrl, targetUrlConfigKey, tokenConfigKey, token, channel, recipient, subject, message. JSON- and code-typed fields never interpolate — they are passed through literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Send Message) works as well as the exact type id (output.send-message).

In the Copilot panel (or any connected AI):

add a send message node after the trigger

As a step in a create_chain_workflow call:

{"type":"Send Message","config":{}}

Raw MCP call — add this node to a workflow with add_node

curl -s -X POST http://localhost:48170/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Send Message" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what you see in the run data panel after pressing Test workflow.

On this run the node emitted on ports sent, output.

Input — what the node received

{
  "kind": "json",
  "contentType": "application/json",
  "payload": {
    "message": "hi smoke"
  },
  "body": {
    "message": "hi smoke"
  }
}

Output — what the node produced

{
  "provider": "generic",
  "statusCode": 200,
  "ok": true,
  "responseBody": "{\"ok\":true,\"echoed\":43}"
}

Property reference

Every setting, with its type and default — the same fields shown configured in the panel above.

Property	Type	Default	Description
Provider `provider`	`select`	`"slack"`	Messaging provider to send through. `discordgenericgmailslacktelegram`
URL `url`	`string`	`—`	Static webhook/API URL (or use the config key below).
Target URL `targetUrl`	`string`	`—`	Resolved target URL.
URL config key `targetUrlConfigKey`	`string`	`"messageWebhookUrl"`	Config/secret key the webhook URL is read from.
Token config key `tokenConfigKey`	`string`	`—`	Config/secret key the auth token is read from.
Token `token`	`string`	`—`	Inline auth token (prefer the config key in production).
Channel `channel`	`string`	`—`	Target channel/conversation, where the provider uses one.
Recipient `recipient`	`string`	`—`	Target recipient, where the provider uses one.
Subject `subject`	`string`	`—`	Message subject, where the provider uses one.
Message `message`	`string`	`—`	Static message text (or read it from the path below).
Message path `messagePath`	`field`	`"message"`	Dotted path to the message text in the input.
Headers `headers`	`json`	`—`	Additional request headers as a JSON object.
Expect 2xx `expectOk`	`boolean`	`true`	Fail the node on non-2xx responses.

Related nodes

The rest of the Output group — the same folder you’d scan in the editor’s library.

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples.