Webhooks · Cost workflow
Send cost events into your own workflows
Deliver supported StackSpend events to an endpoint you control, with the cost context your automation needs. Validate the payload and delivery behavior before connecting a production runbook.
Built for Platform engineers building event-driven workflows.
14-day trial · No credit card required · Business from $199/month
Illustrative connection workflow. No account is connected by viewing this page.
The problem
What brings Webhooks teams here?
Your team may need cost events in an internal workflow that has no native integration. A documented payload and clear delivery contract are necessary before those events can drive operational work.
The solution and buyer value
How StackSpend helps with Webhooks
- 01
Connect a custom destination
Send supported StackSpend events to an HTTPS endpoint you control.
- 02
Build around an explicit event contract
Use documented event types and fields so downstream automation handles the actual payload rather than assumed dashboard data.
- 03
Validate delivery and failure handling
Test signature verification and the supported retry behavior before relying on the endpoint for a critical workflow.
Before you connect
Check Webhooks coverage and access
- Workflow and prerequisite
- The anomaly.created event and webhook.test delivery, signed with HMAC-SHA256 and retried up to six attempts.
- Required access
- Your endpoint and the documented event-delivery configuration.
- Data and delivery
- Event timing follows source reporting, sync and event creation; this is not a cost-history import.
Limits to check
- Budget events are not in the current event catalog.
- Your receiver must verify signatures and handle duplicate deliveries.
- StackSpend does not supply automatic remediation for your endpoint.
Evaluate the connection
From setup to a useful Webhooks review
Supported test event received, verified and deduplicated safely; no production remediation in evaluation.
Read the webhook contract- Your endpoint and the documented event-delivery configuration.
- Open the Webhooks setup guide and configure the supported destination or endpoint.
- Supported test event received, verified and deduplicated safely; no production remediation in evaluation.
Webhooks questions before you connect
Which webhook events can I subscribe to?
The current catalog supports anomaly.created and webhook.test. Delivery uses HMAC-SHA256 signatures and up to six attempts. Verify the signature, store a stable deduplication key and test your receiver before enabling an operational workflow.
Does a webhook automatically fix the cost problem?
No. Your receiver decides what to do with the event. Validate, authenticate and deduplicate it, and apply your own safeguards before any consequential remediation.
Should we build a webhook receiver for PagerDuty or incident.io?
Review the supported native integrations first. A native destination may meet the routing need without a custom receiver; use webhooks when you need a distinct internal workflow.