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

​
Configure the request

Create a Zap with your source trigger, then add a Webhooks by Zapier request action that accepts a JSON body. Use the shared POST URL, headers, and body below. Store the API credential in the platform’s supported secure configuration; restrict access to the Zap. 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 the trigger’s message field into data.message. Use a source-event ID as the operation key; if the same record can trigger distinct notifications, include the event version or transition. Confirm your plan includes the required Webhooks action. 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