What are Replicate webhooks?
Replicate webhooks send an HTTP request when an event occurs in your Replicate account. Teams use them to react to prediction completion, failure, and model events without repeatedly polling an API. Hookflo gives each delivery a searchable record and can notify the right team when an event arrives or signature verification fails.
Events to monitor
Choose the event types that matter in your Replicate configuration. Common examples include:
- starting
- processing
- succeeded
- failed
Connect Replicate to Slack or email
- Create a webhook in Hookflo and select Replicate.
- Copy the unique Hookflo webhook URL.
- In Replicate API request → webhook configuration, add the Hookflo URL and choose the event types to send.
- Use the webhook signing secret from your Replicate configuration. It is separate from your Replicate API token.
- Save the endpoint, send a test event, and choose Slack or email for notifications.
Verify signatures and debug delivery issues
Confirm the signing secret is present in the webhook setup and that the Hookflo URL is the callback URL used for the prediction.
When a delivery fails, check the selected event, destination URL, and provider-specific signing secret first. Hookflo keeps the event payload and verification result together so the issue is easier to diagnose.
Read Replicate webhook documentationHow do I get alerts when a Replicate prediction fails?
Configure the prediction webhook URL to point to Hookflo, save Replicate’s webhook signing secret, and route failed prediction events to Slack or email.