In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
Choose this option if all alerts go to one channel. It’s the simpler setup.View dedicated integration setup steps
View dedicated integration setup steps
- In the Flashduty console, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Choose Meraki integration, click Save to generate a card
- Open the generated integration card and copy the Push URL
Use a shared integration
Choose this option if you need to route alerts to different channels based on the alert payload.Configure Meraki
1
Add an HTTPS receiver in Meraki
Where: Meraki Dashboard › Network-wide › Configure › Alerts › Webhooks › Add an HTTPS receiver
Then click Save. The URL must be a publicly reachable HTTPS address with a certificate from a trusted CA; the Flashduty push URL meets this.

2
Send alerts to the receiver in Meraki
Where: Meraki Dashboard › Network-wide › Configure › AlertsOn the Alerts page, configure
Cellular gateway and the other alert types as needed, and select the Flashduty receiver created in the previous step as the recipient of each alert type. Only the selected alert types are pushed to Flashduty.3
Send a test and confirm
Where: Meraki Dashboard › Organization › Configure › API & Webhooks › WebhooksClick Send test on the receiver row. The message
Webhook test was successful! only shows that Meraki can reach the push URL; it does not prove the content is parsed like a real alert. Verify with a real alert: trigger one of the selected alert types, and a few seconds later the integration in Flashduty shows a Latest event time, which means the setup works.Status and severity
Any other value is treated as Info. Meraki alert events carry no recovery status, so alerts do not close on their own; turn on the auto-resolve timeout in the channel that receives this integration.