Use this when another product can send HTTP events and your team wants a structured Slack notification with run history in B3OS.

Pattern

text
manual/webhook trigger -> format -> Slack message -> optional webhook response
Webhook to Slack flow
POSTtrigger bodyformatted text External event Payment, form, app callback, custom system Webhook trigger Input schema and trigger body Format alert Normalize fields and template text Slack message Connector-backed notification

Build Steps

1

Create a manual trigger

Use the manual trigger with an input schema that matches the event body you expect to receive.

2

Format the alert

Add the format action and reference trigger fields such as {{$trigger.body.customerId}}, {{$trigger.body.amount}}, and {{$trigger.body.status}}.

3

Send the Slack message

Add a Slack message action, attach the Slack connector, and use the formatted output as message text.

4

Publish and copy the webhook URL

Publish the workflow, then use the workflow run URL or public execution URL appropriate for your integration surface.

Example Nodes

json
{ "nodes": { "root": { "type": "manual", "payload": { "inputSchema": { "type": "object", "required": ["customerId", "amount"], "properties": { "customerId": { "type": "string" }, "amount": { "type": "number" }, "status": { "type": "string" } } } }, "children": ["format_alert"] }, "format_alert": { "type": "format", "payload": { "data": { "customerId": "{{$trigger.body.customerId}}", "amount": "{{$trigger.body.amount}}", "status": "{{$trigger.body.status}}" }, "template": "Customer {{@customerId}} status {{@status}} for {{@amount}}" }, "children": ["send_slack"] }, "send_slack": { "type": "slack-send-message", "connector": { "type": "slack", "id": "conn_slack" }, "payload": { "channelId": "C0123456789", "text": "{{$nodes.format_alert.result.formatted}}" }, "children": [] } }}

Production Checks

CheckRequirement
Input schema matches the senderRequired fields are explicit and optional fields have fallback behavior.
Connector is attachedThe Slack connector belongs to the same organization and has access to the target channel.
Failure path is visibleAdd an execution webhook or monitoring alert for failed deliveries.
Ask a question... ⌘I