Connect Stack9 to Everything — Push Data Out, Plug Agents In
Webhooks push form submissions to your systems the moment they happen, with queue-based delivery and retries. Instance MCP lets AI agents call your data and automations directly. Two ways in, both built on the permissions you already trust.
Two Ways to Connect Stack9 to the Rest of Your Stack
Real-time form webhooks
The moment a visitor submits a form, Stack9 POSTs the submission to every webhook registered for that form — no polling the submissions API required.
Queue-based delivery with retries
Deliveries run through a queue with automatic retries, so a receiver's brief outage doesn't cost you a lead.
Secure with custom headers
Attach the HTTP headers your receiver needs — API keys, bearer tokens — to authenticate every delivery. Secret header values are encrypted at rest and never echoed back in the API.
Test before you trust it
Send a real test payload to your endpoint straight from Stack9 and see the status code, response body, and round-trip time before a single real submission depends on it.
AI agents as a first-class integration
Beyond outbound webhooks, expose your query-library queries and webhook automations as MCP tools so agents like Claude can read your data and trigger actions directly — see Instance MCP.
Form submissions today, built to grow
form.submission is the first event Stack9 delivers over webhooks, registered per form. It's the foundation we're building broader event coverage on top of.
From Form Submission to Your System
Register a webhook
Choose the form to listen to, set a target URL, and add any custom headers your receiver needs to authenticate the call.
Test it
Fire a stored test payload at your endpoint and confirm you get back the status code and response you expect.
Go live
Every submission to that form is queued and delivered to your URL, with automatic retries if the first attempt fails.
Or skip the receiving endpoint entirely
Use Instance MCP to let an AI agent query submissions or trigger automations directly — no webhook receiver required on your side at all.
See the Integration Surfaces
Outbound webhooks for your systems, MCP tools for your AI agents.
Register a webhook against one form, with custom headers for auth.
Validate your receiver before a real submission ever depends on it.
The same submission data, callable by an AI agent through MCP.
Get Data Out — to Systems or to Agents
Register a webhook in minutes, or hand your query library and automations to an AI agent through Instance MCP. Either way, Stack9 enforces the same rules it already does for your REST API.