Signed payload
Each payload can be verified by the receiver with an HMAC SHA-256 signature.
Discover Midna
Webhooks
Trigger automations as soon as a lead is created
Midna sends a `lead.created` event so you can connect internal workflows, Make, Zapier or custom tools.
lead.createdHMAC signatureRetries
Qualified journey
P201
Answers
02
Rules
03
Profiles
Create an HTTPS endpoint.
Product proof
One clear event for every new lead
The `lead.created` event can include the lead, answers, segment, consent, attribution and linked quiz.
Good to know
Webhooks are advanced features available depending on plan. They do not cover every product event.
SEO intents
quiz webhooks
Make Zapier quiz01
quiz lead automation02
lead.created webhook03
Available capabilities
Readable, verifiable webhooks
This feature is built for ops, data and technical teams connecting Midna to their workflow.
Delivery history
Track status, HTTP code, duration, error and attempt count.
Retry and replay
Failures can be retried automatically or replayed manually.
Webhooks
Not every automation needs a native integration.
Before
Waiting for a specific integration blocks custom workflows.
With Midna
With Midna, a webhook can send the created lead to your stack depending on plan.
Use cases
Use cases
01
Make
02
Zapier
03
Internal tool
04
Sales follow-up
05
Simple data pipeline
Related pages
Related pages
Webhooks complement native integrations, the leads API and capture workflows.
FAQ
FAQ
Is it secure?
Payloads are signed with HMAC SHA-256 so the receiver can verify them.
Which event is sent?
The feature covers the main `lead.created` event.
Can I replay a failed webhook?
Yes. Failed deliveries can be replayed manually.
Are webhooks available on every plan?
No. This is an advanced feature depending on API access.
Midna
How it works
How to use webhooks
answer → signal → segment → action
Create an HTTPS endpoint.
Receive the `lead.created` event.
Verify the HMAC SHA-256 signature.
Review delivery history.
Replay or let retries handle failures.