SilfenworksBack to silfenworks.com

Labeling and managing triggers

It's common to build several automations from the same trigger. For example, you might have multiple "Order created" automations, each filtered to a different segment of orders. Labels make it easy to tell them apart at a glance.

Adding a label

Where the label comes from depends on how the automation was built:

  • If you configure the trigger step through monday.com's visual workflow builder, you'll find an optional Trigger label field there. Whatever you type shows up next to the trigger name everywhere this automation appears, for example "Order created (High-value EU orders)".
  • If the automation was created another way, it doesn't go through that field, so the label is set to the board's ID instead, for example "Order created (12345678)". This isn't editable from the connector for now.

A label is just a name for this specific automation. It isn't shared across your workspace or reusable on other automations, so if you can set a custom one, do it once when you configure the trigger and your list will stay readable as it grows.

Managing your automations

The automations dashboard lists every automation built on this connector, along with its trigger (and label, if it has one), status, and creator. From there you can:

  • Filter the list by status: Active, Inactive, or Deleted
  • Open an automation to see its full detail page, including its status, trigger, label, filter, creation info, activity, and metrics
  • Turn an automation off or on (more on that below) without deleting the monday.com automation itself
  • Edit or clear its filter at any time, see Adding filters to a trigger

Turning an automation off and on

From an automation's detail page, use Turn off to stop it from processing further Shopify events. Incoming webhooks for that automation are silently ignored, and you can optionally jot down a reason, like "pausing during the holiday sale". The monday.com automation itself stays in place and can be switched back on at any time with Turn on, after which webhooks resume being processed normally.

This is the recommended way to pause an automation temporarily, for example while you adjust board columns or mappings, without losing its configuration, filter, or activity history.