Skip to main content
Use your platform’s HTTP capability to send template data to LithoBlocks. These workflows do not require a native LithoBlocks connector. Check availability before choosing a production or preview environment.

​
Shared request

Create a template whose Section contains {{message}}. Configure an API key with messages:create, a connected test Slack workspace, and a fixed template/channel ID.
Map data.message from the trigger while keeping the template and channel configured. Send data as an object, not a JSON string nested inside another string. Use your platform’s JSON/body editor to escape quotes and newlines.

​
Verify and handle failure

Run once with a synthetic event. Save channel, message_ts, and the request ID, then confirm Slack. Branch on unsuccessful responses and inspect bulk results individually. Set a request timeout where supported. Do not enable automatic write retries unless the workflow preserves the original body and idempotency key. A timeout may follow a successful delivery; inspect logs before starting another operation.

​
Platform choices

For the full input discovery and destination contract, see Send with the API. To receive events back, configure button webhooks against your platform’s receiver URL.