Webhooks let external systems push data into Myra in real time - a website form, a legacy database, an internal tool, or a no-code platform such as Zapier, Make or n8n.
Inbound only. Myra does not currently have an outgoing event-subscription system. There is no Settings → Webhooks tab, no event catalogue to subscribe to, and no per-endpoint signing secret. If you need Myra to notify another system when something happens, use an Automation with a Webhook step, which posts to a URL you choose at the point in the workflow you choose.
Automation trigger webhooks
The most flexible way in. An automation can start whenever a POST request arrives at its own URL.
- Create a new Automation.
- Select the Webhook trigger.
- Myra generates a unique trigger URL, shown in the builder, in the form:
https://myra-app.ai/api/public/hooks/automation-webhook/{token}
- Send a sample POST request with a JSON body. Myra parses the keys so you can use them as variables in later steps. For Typeform payloads, recent real question titles appear as selectable source fields, and you can still type a ref or question title by hand.
Keep the token private - anyone holding it can start that automation.
Rate limit: 300 requests per 60 seconds per token. Requests over the limit are rejected with
429 and a retry-after header.
Use case example
External e-commerce: when a purchase happens in your custom shop, POST to the trigger URL to create the contact, tag them "Customer", and start a post-purchase sequence.
Pipeline webhooks (inbound lead capture)
The only webhook configuration in Settings is the Pipeline Webhooks card on Settings → Pipeline. It mints inbound lead-capture URLs: post a lead payload to one and the contact is created in that pipeline. Use this when you only need "create a contact" and not a full automation.
Sending data out of Myra
Use the Webhook action inside the Automation builder. You choose the method, URL, headers and body, and tokens are rendered from the contact and trigger data. The builder's Send test button runs the exact same payload-building code as a real run and shows you the request and response.
Developer best practices
- Idempotency: an inbound request may be retried by the sender. Make sure repeated payloads do not create duplicate work on your side.
- Testing: use
webhook.siteorngrokwhile developing to inspect payloads before pointing them at production. - Rotate on exposure: if a trigger URL leaks, create a new trigger and retire the old one.
FAQs
Is there a signature header I should verify? Not for automation trigger webhooks - the secret is the token in the URL itself.
Can I subscribe to events like contact.created?
Not yet. Build an automation with the matching trigger and a Webhook step instead.
Do you publish static outgoing IP addresses? No. Requests come from our hosting provider's shared egress, so IP allow-listing is not supported.