webhook_format to
slack when creating or updating the scout. Slack payloads use Block Kit formatting.
Example Request
Below is an example of the HTTP request that a Scout sends to your webhook endpoint.Slack Incoming Webhook Payload (Example)
Field Descriptions
| Field | Description |
|---|---|
event_type | Always "scout_update" |
scout.id | Unique identifier for the Scout |
scout.display_name | Human-readable name |
scout.query | Original query/task description |
update.id | Unique identifier for this update |
update.timestamp | ISO 8601 timestamp when update was generated |
update.status | Typically "completed" |
update.has_changes | Boolean indicating if new content was found |
update.summary | Brief description of what was found |
update.details_url | URL to view full results |
update.report_content | Raw content of the update |
delivery.id | Unique identifier for this delivery attempt |
delivery.attempt | Delivery attempt number (starts at 1) |
delivery.timestamp | Timestamp when webhook was sent |
Webhook Delivery Details
Headers
All webhook requests include the following headers:Content-Type: application/jsonUser-Agent: Scout-Webhook/1.0X-Scout-Event: scout.update
Response Expectations
Your webhook endpoint should:- Respond with HTTP status 200-299 for successful receipt
- Process the webhook asynchronously if needed
- Respond within 10 seconds (default timeout)
Error Handling
Scout will consider delivery failed if:- HTTP response status is not 2xx
- Request times out (default 10 seconds)
- Network error occurs
Security Considerations
- Use HTTPS URLs for production webhooks
- HTTP URLs are only allowed for
localhost/127.0.0.1(testing) - Validate webhook payload structure in your endpoint
- Consider implementing webhook signature verification for additional security