Meraki Workflows for Automation

[ReginaPhalenge]

Hi everyone,

I’ve been exploring Workflows for Automation in the Meraki dashboard and would love to hear how others are using it in real-world environments.

For those who’ve deployed it, what practical use cases has it been most valuable for? Are you leveraging it for operational efficiency, change management, alert remediation, or something else entirely?

Any examples or lessons learned would be greatly appreciated. Looking to better understand where it delivers the most impact.

Thanks in advance!

[obrigg]

Hi Regina,

We have a dedicated forum for Agentic Workflows in the Cisco community. We have expert there who will be happy to help.
The entire Meraki community will be moving into the Cisco community during Spring 2026.

[Philip D'Ath]

Check out this post that I just made.

https://community.meraki.com/t5/Full-Stack-Network-Wide/Top-2-3-Meraki-Workflows/m-p/291824/highlight/true#M3203

[Noel-Edouard Chenu @ Boundless]

Late to this thread, picking up on forum messages I'd missed. A few notes from the field on what's actually landed for customers over the last couple of months:

1. PSK rotation with scheduled distribution. SSIDs with shared passphrases (retail, healthcare guest networks) on a rotation cadence, with the new key posted to Teams or Webex for staff. Takes the helpdesk out of the loop.

2. Bulk firewall rule pushes by tag. Same outbound block across 50+ MX networks (a known-bad domain, a deprecated SaaS) is much cleaner via a tag-driven workflow than the dashboard UI. Audit trail is also tidier.

3. Pre-change config snapshot. Before a meaningful change window we trigger a workflow that pulls the relevant endpoints and stores a baseline. If anything regresses, rollback is a known-good JSON, not "let's diff screenshots in the change log."

4. New-site provisioning glue. Claim devices, bind to template, set address, notify the site lead. Not magic, but removes the click-fatigue when you're rolling out 200+ networks.

Where we've kept things outside Workflows: cross-org orchestration, signed audit trails for regulated customers, and full restore-from-backup parity. Workflows is genuinely good inside a single org, but multi-tenant ops still want a layer above the dashboard.

Curious what others are running. Especially interested if anyone has wired Workflows into the new EVPN-VXLAN cloud-managed fabric yet, since that's where we're spending design cycles next.

[PacketWizard]

I was just in a meeting with Boundless regarding Safeguard.  I was sad to see that only backups are possible, with no current restoration option. I was told this is a future feature. Do you know of a way that the JSON can be taken and used for recovery? Outside of auditing, I'm not sure I understand the purpose of a backup if there is not a restoration option. 

[Noel-Edouard Chenu @ Boundless]

Hey PacketWizard,

Fair pushback, and you're not wrong: a backup without restore is just an audit trail.

Quick context that might help:

1. Restore is live in beta today. Safeguard evolved out of our backup-as-a-service offering, so the underlying restore engine isn't new for us, we're just rolling it out feature-by-feature in the product to keep quality tight. Beta users are running full restores right now.
2. General availability is next month (June). One-click restore, selective restore (by network, by config object), and point-in-time rollback all ship together.
3. In the meantime, the JSON we generate is Meraki Dashboard API compatible. Every backed-up object maps 1:1 to its API endpoint, so it can be pushed back via the API for targeted recovery, like reverting a single firewall rule or cloning a known-good config to a new network. Several customers use it that way today.

Appreciate you raising it here, this kind of feedback is exactly why we ship. Happy to set up a call with a call with you in the coming days if needed.

Ned

[PacketWizard]

This is great news! You were much needed on the call I had. #1 in particular is very important to us. We were not ready to test a new recovery product on some specific networks of ours. Safeguard was explained to us as a new product, not one that was an evolution of an existing backup-as-a-service offering. We had also asked about using the JSON to recover but were told  " I'm not sure" by the on boarding manager. Thanks for clearing this up. I am much more comfortable about the purchase now. 

[Noel-Edouard Chenu @ Boundless]

Glad to hear it Sam! And thanks for being straight with me.

I'll follow up with some slots so I can walk you through where Safeguard came from (the backup-as-a-service heritage and what carries over) and we can review the restore capabilities together.

Ned