Skip to main content
This is a generic HTTP integration. It does not require or announce a native LithoBlocks Retool connector. Review environment availability.

​
Configure the request

Create a REST API resource using your environment’s API base URL and a server-side Bearer credential. Add a POST query for /v1/templates/send with the shared JSON body. Restrict who can edit or run the query. Use the full settings and JSON body in Send from an HTTP automation. Start with a template that accepts data.message, an API key with messages:create, and a test channel.

​
Map and verify

Map validated form or query values into data.message. Keep the destination configured in the resource/workflow. Persist one operation ID per approved user action so a repeated click or retry does not silently become a second send. Run one synthetic event, confirm success and the returned message coordinates, and inspect Slack. Route non-success responses to a visible failure branch. Do not rotate the operation ID after a timeout to force another send.

​
Receive interactions

Create a webhook receiver in your automation platform, authenticate incoming requests, and use its URL in a LithoBlocks webhook destination. Use payload variables to send the original record ID, Slack actor ID, and submission receipt where applicable. Logs · API keys