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

​
Configure the request

Create an Automation with a record trigger and a Run a script step, if available on your plan. Map record fields into script inputs. Have the script issue the shared JSON request with fetch; check the HTTP status and record the returned message coordinates. 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

Store the key using the platform’s supported secret facility, never in a shared record field. If secure server-side secret storage is unavailable for your workflow, send the event to an external automation service instead. Derive the operation ID from the record plus its intended notification event, not the record ID alone. 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