Create and Manage Webhooks
Learn how to create, configure, manage, and monitor ingestion webhooks in Sprinto, including authentication, attached plans, recent events, webhook testing, and lifecycle actions.
Webhooks allow external systems to send data directly into Sprinto.
Each webhook generates a unique endpoint URL that can receive incoming requests from external services.
Webhooks are commonly used when:
Data must be pushed into Sprinto automatically
Events occur outside scheduled ingestion plans
External systems support webhook delivery
Near real-time processing is required
Within Sprinto, webhooks can be configured with:
Authentication rules
Rate limiting
Attached ingestion plans
Event filtering
Runtime parameters
Event visibility
Before You Begin
Ensure that:
You have access to the Ingestion module
A webhook use case has been identified
Any required ingestion plans already exist
Authentication requirements are known
Access the Webhooks Page
To manage webhooks:
Log in to the Sprinto dashboard.
Go to Ingestion.
Select the Webhooks tab.
The Webhooks page displays all configured webhooks.
Understand the Webhooks Dashboard
The Webhooks dashboard lists all available webhooks.
Each row typically includes:
Name
Webhook name
Description
Optional explanation
Status
Current webhook state
Created At
Creation timestamp
Actions
Opens webhook details
Use the dashboard to monitor existing webhook configurations.
Create a Webhook
Create a webhook when you need Sprinto to receive data from an external source.
Add a Webhook
Open the Webhooks tab.
Click New Webhook.
Configure webhook settings.
The webhook becomes available immediately.
Configure Webhook Details
Webhook creation includes multiple configuration sections.
Basic Information
Configure:
Webhook name
Description
Use descriptive naming to identify the source system.
Examples include:
Incident Events
Device Sync Webhook
Security Alert Feed
Authentication
Authentication validates incoming requests.
Authentication ensures that only trusted systems can send data.
Authentication configuration may include:
Secret keys
Signature validation
Header mapping
Token validation
The authentication method depends on the external system.
Advanced Configuration
Advanced settings define how Sprinto processes webhook requests.
Advanced configuration may include:
Payload handling
Event identification
Challenge validation
Custom parsing rules
These settings help align the webhook with external payload formats.
Rate Limiting
Rate limiting controls how many requests Sprinto accepts.
Rate limiting helps:
Prevent abuse
Avoid overload
Improve webhook stability
Rate limits can be configured during webhook creation or editing.
Save a Webhook
After configuring all sections:
Review the configuration.
Click Save.
Sprinto creates the webhook and generates a webhook URL.
View Webhook Details
Webhook details provide access to configuration and event activity.
Open Webhook Details
Locate a webhook.
Click View.
Sprinto opens the webhook details page.
Webhook Details Overview
The details page includes:
Configuration summary
Webhook URL
Attached plans
Recent events
Testing utilities
Lifecycle actions
View the Webhook URL
Each webhook includes a generated endpoint URL.
External systems must send requests to this endpoint.
The URL is visible from the webhook details page.
Test a Webhook
Webhook testing helps validate connectivity.
Sprinto provides a cURL testing section to help verify requests.
Test a Webhook
Open webhook details.
Review the test request example.
Send a request to the webhook endpoint.
Confirm event visibility.
Testing helps confirm that payloads reach Sprinto successfully.
Attach a Plan to a Webhook
Attached plans determine how webhook payloads are processed.
Without a plan, webhook requests may be received but not processed into ingestion workflows.
Attach a Plan
Open webhook details.
Go to Attached Plans.
Click Attach Plan.
Select a plan.
Configure optional settings.
Click Attach.
The plan becomes associated with the webhook.
Configure Attached Plan Settings
When attaching a plan, you can configure additional behaviour.
Filter Expression
Filter expressions control whether incoming events should trigger processing.
Use filters to:
Restrict processing
Ignore unnecessary payloads
Match specific event types
Runtime Parameters
Runtime parameters pass values from the payload into the plan.
This allows dynamic execution based on incoming data.
View Recent Events
Recent events display webhook activity.
This helps confirm whether requests are reaching Sprinto.
Recent Event Information
Each event may include:
Timestamp
When the request was received
Status
Processing result
Event ID
Unique event identifier
Payload
Incoming request preview
Recent events are useful for troubleshooting.
Edit a Webhook
Webhook configurations can be updated after creation.
Edit a Webhook
Open webhook details.
Click Edit.
Update the required configuration.
Click Save to save the changes.
Updates apply immediately.
Rotate Webhook ID
Rotating a webhook ID generates a new endpoint URL.
Use rotation when:
Credentials are compromised
Endpoint URLs must be refreshed
Security policies require regeneration
Rotate a Webhook ID
Open webhook details.
Click Rotate ID.
Confirm the action.
Sprinto generates a new webhook URL.
Important
After rotation:
Old URLs stop working
External systems must update the endpoint
Requests sent to the previous URL fail
Delete a Webhook
Delete a webhook when it is no longer required.
Delete a Webhook
Open webhook details.
Click Delete.
Confirm the action.
The webhook is permanently removed.
Webhook Workflow
A typical webhook lifecycle follows this sequence:
Create a webhook.
Configure authentication.
Define advanced settings.
Save the webhook.
Share the endpoint URL.
Attach a plan.
Receive incoming requests.
Monitor recent events.
Update or rotate configuration when needed.
Best Practices
Use the following recommendations when managing webhooks:
Use descriptive webhook names
Configure authentication whenever possible
Attach plans immediately after creation
Test webhook delivery before production use
Use filters to reduce unnecessary processing
Review recent events regularly
Rotate webhook IDs if exposure occurs
Delete unused webhooks
Related Information
Last updated