Log Message
Write a message to the workflow run log. Supports variables like {{node.result.field}}. Helpful for debugging and tracking execution.
Built-in action Built In
Write a message to the workflow run log. Supports variables like {{node.result.field}}. Helpful for debugging and tracking execution.
At a Glance
| Field | Value |
|---|---|
| Action ID | log |
| Category | Built In |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | logging, debugging, output, utility |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Message to log. Supports template variables like {{node.result.field}}, {{$item}}, {{$index}} |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | The formatted log message with resolved template variables |
loggedAt | string | Yes | ISO 8601 timestamp when the log was created |
Examples
json{ "type": "log", "payload": { "message": "Processing item {{$item}} at index {{$index}}" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/log/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "message": "Processing item {{$item}} at index {{$index}}" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.