Message
A box for custom data. You type the content; the node passes it on.
Use the Message node when you want a node to output a specific block of data you write yourself, rather than data computed from an earlier step. The content must be valid JSON or XML.
When to use it
- Inject a fixed payload into the workflow (a template, a set of defaults, a constant).
- Provide sample data while you build and test the rest of the flow.
- Hand a hand-crafted request body to a downstream Connection node.
Inputs & outputs
| Input handle | One. (The incoming data is available but the node's output is the content you type.) |
| Output handle | One — the parsed content you entered. |
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Content | JSON or XML text | Yes | The data this node outputs. It is validated when you save — invalid content is rejected with the error "The provided content must be valid JSON or XML." |
Example — a JSON payload
Content you type into the node:
{
"source": "orchasync",
"status": "new",
"priority": 1
}
Anything you connect after this Message node receives exactly that object as its input.
Example — an XML payload
<order>
<source>orchasync</source>
<status>new</status>
</order>
warning
If you see "The provided content must be valid JSON or XML." when saving, your content has a syntax error — a trailing comma, an unclosed tag, or unquoted keys are the usual causes. Paste it into a JSON/XML validator to find the issue.