06-25-2025 01:12 PM - edited 06-26-2025 06:58 AM
To help new Workflow users get started we'll be posting some example workflows here until the Workflows Exchange is ready. Please feel free to ask any questions about these workflows here. We are also creating video walkthroughs of each example workflow and will update the posts with the links as soon as they are ready.
If you've already submitted a request for Early Access to the new Workflows environment but haven't received notification yet, please be patient. We had an overwhelming response for Early Access at Cisco Live and we're working through the backlog. We will get you activated as soon as we can over the next few weeks.
If you haven't already requested Early Access, you can do so here: http://cs.co/WorkflowsEarlyAccess
06-25-2025 01:16 PM - edited 06-26-2025 11:19 AM
This is a custom Workflow created by enovak that requires a Meraki device Serial Number as input and will blink the device LEDs. This workflow uses a Generic Meraki API Request Action to the Create Device Live Tools Leds Blink API to enqueue a job to blink LEDs on a device.
To import this example, you will need to change the file extension from .txt to .json
06-25-2025 01:20 PM - edited 06-26-2025 11:19 AM
This workflow requires a Meraki Network Name and either a Meraki Organization ID or Meraki Organization Name as input. The workflow returns JSON objects for the current and available firmware versions for Appliance, Switch and Wireless devices on the Network.
To import this example, you will need to change the file extension from .txt to .json
06-25-2025 05:36 PM - edited 06-26-2025 11:19 AM
06-26-2025 11:18 AM
06-26-2025 11:50 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide