Publishing Flows & Events
Quick links in this article:
There are several ways you can change the conditions under which your Workflows will trigger. They each have different use cases, so let’s run through the functions now.
Events
Events can be enabled or disabled whenever you select an event by clicking or . We use this to stop an event from triggering any of it’s associated flows. You may want to do this because:
You have a problem with the event and need to turn it off to make changes
You want to make a process change to an event, or a flow
Enabling or disabling will happen immediately.
Make sure you’re certain before you disable something - it may change the way other events work if the flows contained trigger other events in turn. Check Logs to look for errors and behavioural changes before and after changing an event status.
Flows
Flows have two options to make changes to their ‘firing’ status. It’s important to remember a flow can be used on more than one event, and this is why we have two different ways of changing the status of a flow!
It can be useful to think of it like this; enable/disable lets you control your flow across all of your events, while publish/draft is used to build new flows you might want to try out later.
Disabling/Enabling
You can disable/enable from the Flows table by using the quick action menu under
Enabling and disabling a flow will make it stop/start working on every event it is attached to. This is the best and quickest way to stop/start a flow from working everywhere, all at once.
Publishing/Drafting
If you’ve made some changes to a flow and used ‘Save’ in the builder, you’ll have saved a draft version of the flow. When you’re ready overwrite the published version, you can move it from draft to published using ‘Publish’ in the builder or the quick action menu in the Flows table.
A published workflow is one that is ready to be used; when you attach it to an event, or publish something in draft that is already attached to an event, it will begin executing.