Skip to content
Sarudo

Webhook Events

Receiving events from Stripe, GitHub, Typeform, Calendly, and other services. Viewing event history.

webhookseventsstripegithubtypeformcalendlyincoming

What Are Webhooks?

Webhooks are real-time notifications sent by external services when specific events occur. When a customer pays an invoice in Stripe, a form is submitted in Typeform, a PR is merged in GitHub, or a meeting is booked in Calendly, the service sends event data to a URL on your server. Your AI employee receives these events and can take action — notifying you, updating CRM records, triggering workflows, or any other configured response.

Supported Services

Sarudo can receive webhooks from virtually any service that supports them. Commonly configured integrations include Stripe (payment and invoice events), GitHub (pull requests, issues, deployments), Typeform (form submissions), Calendly (meeting bookings and cancellations), Shopify (orders and inventory), and custom applications. Any service that can send HTTP POST requests to a URL can integrate with your AI employee through webhooks.

Receiving a Stripe webhook

Automatic notification on payment.

You say:
[Stripe webhook event received]
Sarudo responds:
Payment received! ClientCo just paid Invoice #INV-0042 for $1,850 via Stripe. Payment method: Visa ending 4242. I've updated the invoice status to "paid" and logged the payment activity in the CRM under ClientCo. The associated deal "ClientCo Consulting" has been updated. Would you like to send a thank-you email?

Configuring Webhooks

To receive webhooks from a service, your AI employee provides a unique webhook URL that you register in the external service's settings. Each service has its own webhook configuration interface — your setup team can help with the initial configuration. Once configured, events flow automatically. The AI validates incoming webhooks using signature verification to ensure they are authentic and not spoofed.

Always use webhook signature verification when available. This ensures that incoming events are genuinely from the expected service and not from a malicious source.

Viewing Event History

All received webhook events are logged and can be reviewed at any time. Ask your AI employee to show recent webhook events — you will see the event type, source service, timestamp, and a summary of the data. This event history is useful for troubleshooting integrations, verifying that events are being received, and reviewing past activity. Events are stored for at least 30 days.