Shapes

Start a flow

When something happens

Starts the flow on platform events, such as a flow turned on or off, a deployment, a refused sign-in or a Worker going offline.

Nodes › TriggersOpen in Neblex
Good for
Operations automation
Role
Starts a flow
Find it in
Nodes › Triggers

When to use it

  • Someone should hear when a connection's sign-in is refused and it needs reconnecting.
  • A failed transfer route should open a ticket.
  • Turning flows on or off, promotions and Git deployments should be recorded or announced.

Reach for something else when

Example

When a transfer route fails, open a ticket with the route's name and error; when a connection's sign-in is refused, message its owner.

  1. When something happens
  2. Branch
  3. ServiceNow
  4. Slack

How it works

Settings
Start when: a flow is turned on; a flow is turned off; a promotion lands here; a flow is deployed from Git; a connection's sign-in is refused; a transfer route moves its files; a transfer route fails; an On-Prem Worker goes offline. Choose at least one.
Behaviour
Events of this flow's environment start it; a Worker going offline starts it in every environment. Each event starts each watching flow once, also when the platform is busy or restarts, with one record: event, at and what it happened to (flow and flow_name; promotion, kind, lineage and from_environment; flow, flow_name, source and path for a Git deployment; connection, connection_name and error; route, route_name, run, transferred, failed and error; worker and worker_name). A refused sign-in is one whose provider refused to renew it (a revoked or expired grant, a wrong client), at most once per connection per hour however many runs hit it; a sign-in renewed on an On-Prem Worker itself is not watched. A run that cannot start yet (the monthly quota, storage) is tried again until it starts.
Example
When a transfer route fails, open a ticket with the route's name and error; when a connection's sign-in is refused, message its owner to reconnect it.
More in the guide

Add it to a flow

  1. Open the flow from Build › Workflows.
  2. Open Nodes and find When something happens under Triggers. Drag it onto the canvas as the first step.
  3. Connect it to the next step and open its settings with ✎ Edit.
  4. Save and test with Run, then set the flow Active so it starts on its own.