Documentation Index
Fetch the complete documentation index at: https://docs.boltroute.ai/llms.txt
Use this file to discover all available pages before exploring further.
Use Case
Use webhooks when you want verification to trigger downstream automation without polling. This is ideal for routing results into CRMs, spreadsheets, or internal workflows.Where Verification Fits
Workflow at a glance:1. Trigger
Capture email(s) from a form or app event.
2. Create task
Submit a batch task with a
webhook_url.3. Receive
Handle per-email or task completion webhooks.
4. Route
Update your CRM, spreadsheet, or workflow.
Recommended Flow
- Capture one or more emails from a form or app event.
- Create a batch task and include a
webhook_url. - Receive per-email or task completion webhooks.
- Map verification signals to actions in your CRM or automation tool.
Minimal API Example
Decision Rules
Common webhook routing rules:- Reject or suppress when
statusisinvalid_syntaxorinvalid. - Hold for review when
statusiscatchallorunknown. - Accept or advance a lead when
statusisvalid.
Operational Notes
- Webhook URLs must be HTTPS and respond with a
2xxstatus. - Verify signatures when
WEBHOOK_SECRET_KEYis configured. - Use
X-Webhook-IDfor idempotency if you process retries.
Acknowledge webhooks quickly, then process updates asynchronously to avoid retries.
Success Metrics
- Faster lead routing and reduced manual review.
- Lower operational overhead from polling.
- Consistent verification signals across tools.