E-commerce team triggers AI on new orders
Every new order fires a webhook to the AI employee, which confirms inventory, sends the customer a personalized update, and flags exceptions.
Get notified when tasks complete, approvals are needed, or schedules fire so your systems react in real time.
Webhooks push events from your AI workforce to your systems in real time. When an employee completes a task, your project management tool gets notified. When an approval is needed, your Slack channel gets a message. When a scheduled execution finishes, your data pipeline picks up the output. Events flow out automatically, no polling required.
Configure which events trigger webhooks and where they go. Route task completions to one endpoint, approval requests to another, and error notifications to a third. Each webhook includes a full payload with context: what happened, which employee did it, what the output was, and relevant metadata.
Webhooks are especially valuable for building custom automation pipelines. Chain an AI employee's output into a downstream system: employee researches leads, webhook notifies your CRM to update records, CRM triggers an email sequence, email sequence results webhook back to the employee for follow-up analysis. Closed-loop automation with your AI employee at the center.
Webhooks let Sistava push events to any HTTP endpoint you control as they happen. Task completed, approval requested, employee hired, credit threshold crossed, error detected. No polling, no scheduled fetches, no stale data. Your external systems know about events the moment they occur.
This is the standard pattern for production integrations between SaaS platforms and your internal infrastructure. When an AI employee finishes a research task, your project management tool gets updated. When an approval is needed, your ticketing system creates a ticket. When credits run low, your finance system gets an alert. All automatically, in real time.
Not every system needs every event. Webhook subscriptions are configurable per event type and per delivery endpoint. You can send task completion events to one URL and approval requests to a different URL, or fan out all events to a central event bus for routing downstream.
Event payloads are structured JSON with consistent schema per event type. Each payload includes event type, timestamp, relevant entity IDs, and enough context to act on the event without a follow-up API call in most cases. Full payload schemas are documented in the API reference.
Webhook deliveries include retry logic for failed deliveries (non-2xx responses or timeouts) with exponential backoff. Delivery history is visible in the developer dashboard so you can inspect successful and failed deliveries, view the exact payload sent, and manually replay a delivery for debugging.
Combining webhooks with the REST API creates a fully event-driven automation loop. An AI employee completes a task, the webhook fires, your system processes the result and uses the API to start the next phase, which may involve spinning up another AI employee or sending results to a human reviewer. This pattern is how sophisticated organizations build multi-step automated workflows on top of Sistava.
For developers building products on top of the platform, webhooks are the mechanism for giving end users real-time updates without building polling infrastructure. Your product subscribes to relevant events, routes them to your database and notification systems, and delivers a responsive user experience backed by Sistava's agent workforce.
Every new order fires a webhook to the AI employee, which confirms inventory, sends the customer a personalized update, and flags exceptions.
A new support ticket fires a webhook. The AI agent classifies it, drafts a response, and routes it to the right team in seconds.
A failed build fires a webhook to the AI employee, which investigates the error, checks recent commits, and posts a summary to Slack.
A lead form fires a webhook. The AI agent enriches the lead, scores it, and queues a personalized follow-up, all before the rep refreshes their screen.
| Before | After |
|---|---|
| External events require a human to notice and respond. | Webhooks trigger the AI agent instantly, with no human in the loop. |
| Connecting external tools to the AI workforce requires custom code. | Any tool that sends webhooks can activate an AI employee immediately. |
| Event-driven workflows require a middleware layer to build. | The AI agent listens for webhooks natively, no glue code needed. |
| Response time to critical events depends on who is online. | The AI employee reacts to every event the moment it fires. |
Every webhook delivery includes an HMAC signature in the X-Sista-Signature header, computed using a secret you set when creating the endpoint. Verify this signature in your handler before processing the payload to confirm authenticity.
Sistava retries failed deliveries with exponential backoff over 24 hours. If delivery ultimately fails, the event is marked as failed in the delivery log and you can manually replay it once your endpoint is restored.
You can configure multiple endpoints per workspace, each with independent event subscriptions. There is no fixed limit on the number of endpoints, though very high fan-out configurations may be subject to rate limits on delivery volume.
Yes. Webhook subscriptions can be scoped to specific employees or teams in addition to event types. This lets you set up targeted integrations, like routing events from your sales AI team to your CRM and events from your research team to your knowledge base.
Yes, each AI employee can accept inbound webhooks, so any external service can push data or trigger work in real time. You configure the endpoint once and the agent acts on incoming payloads automatically.
We hooked our e-commerce platform directly to our AI agent. Every order above a threshold triggers the agent automatically and it handles the review without us touching it.