Common Workflows – weavix® Help Center

Workflows let you automate the right response when something happens on your site. Instead of relying on someone to notice an event and take action, a workflow does it for you. In this article, we'll cover how workflows work and walk through some of our most commonly used workflows.

SOS Workflow

Every walt has an SOS button that adds a layer of safety for your team. When someone presses it, an alarm sounds on their walt so people nearby know they need help. But then what? An SOS workflow makes sure the right teams are notified right away and can take action.

How to Create SOS Workflow

Set up the trigger

In console, go to the Workflows tab on the left and click Add Workflow button at the top of the screen.
On the General page, name your workflow, make sure Enabled is checked, and select one site.
On the Workflow tab, click Add under Add Trigger.
Open the Trigger dropdown and select SOS Triggered.
Optionally, add a conditional filter. This limits the workflow to a specific group of people. If you leave it blank, anyone at the site can trigger it.
Save the trigger.

Add the action

Click Then to add an action. If you'd like to add triggers that prevent the workflow from running, click Unless.
Fill in the Action banner. Here's the example we use:
- Action: Send a message to an Admin Defined Channel
- Message: {{person.firstName}} {{person.lastName}} has triggered the SOS man down button!
- Channels: ERT (Select the Admin Defined Channel you would like the message to go to)
Click Save.

You can insert variables like first name and last name into your message using the dropdown.

Pro Tip! If you have geofences built out, add a geofence variable to your message. It sends the user's last known location, which gives your team a better idea of where the incident occurred.

National Weather Service (NWS)

Weather is one of the first things many teams think of for mass alerts, but manually watching for severe weather and sending an alert every time is a lot to ask of an admin. The NWS Weather Alert trigger takes that off your plate. When the National Weather Service issues a qualifying alert for your site's location, weavix automatically runs your workflow. For example, it can send an alert to everyone on site and read it aloud on their walts.

How to Create NWS Workflow

A few things to know before you start:

Weather Alerts are available for US sites only.
The feature is included with the Protect package (legacy) and the Workforce Safety package. If you're not sure whether it's enabled for your account, reach out to your weavix Customer Success Manager.
Since your site's location is used for weather alerts, make sure your site's address or coordinates are accurate.

Set up the trigger

Go to Workflows and click Add Workflow.
On the General page, name your workflow, make sure Enabled is checked, and select one site. Weather Alert workflows are created per site, so if you have multiple sites, you'll create a workflow for each.
Click Save, then move to the Workflow tab.
Click Add under Add Trigger and select NWS Weather Alert from the dropdown.
Under Trigger Conditions, select one or more NWS event types. You must select at least one.

Supported alert types

Warnings	Watches
Tornado Warning	Tornado Watch
Severe Thunderstorm Warning	Severe Thunderstorm Watch
Flash Flood Warning	Flash Flood Watch
Hurricane Warning
Extreme Wind Warning
Winter Storm Warning
Blizzard Warning

Add the action

Click Then to add your action.
Choose how you'd like to notify your team. Weather Alert workflows use the same Alert Types, recipient targeting, and Read Aloud options as your other workflows.
Write your message. You can include NWS variables to pass along the details of the alert (see the table below).
Click Save.

Pro Tip! The headline variable will give you a one-line summary of the alert and when it's expected to start and expire. EX: Tornado Warning issued June 12 at 3:47PM CDT until 4:15PM CDT by NWS Wichita KS

Message variables

Use these variables to include the actual NWS alert details in your message:

Variable	What it contains	Example
{{event}}	Alert type name	Tornado Warning
{{headline}}	One-line summary	Tornado Warning issued June 12 at 3:47PM CDT until 4:15PM CDT by NWS Wichita KS
{{severity}}	Severity level	Extreme, Severe, Moderate, or Minor
{{urgency}}	How soon action is needed	Immediate, Expected, or Future
{{certainty}}	How likely the event is	Observed, Likely, or Possible
{{onset}}	When the event starts	3:47 PM CDT
{{expires}}	When the alert expires	4:15 PM CDT
{{areaDesc}}	Affected counties or zones	Sedgwick; Butler; Harvey
{{description}}	Full alert body	At 3:47 PM CDT, a confirmed tornado was located near…
{{instruction}}	Actions recommended by the NWS	TAKE COVER NOW! Move to a basement or an interior room…

Because you can create as many Weather Alert workflows as you need for a site, you can match your response to the level of risk. Here's an example setup:

	Workflow 1: Tornado Watch FYI	Workflow 2: Tornado Warning site alert
Trigger	Tornado Watch	Tornado Warning
Recipients	Safety channel only	Everyone on site
Action	Informational message so the safety team knows conditions could develop	High-priority alert, read aloud on walts, telling workers to take shelter
Example message	FYI: {{event}} in effect until {{expires}}. Monitor conditions.	{{event}} for our area until {{expires}}. {{instruction}}

Pro Tip! This same pattern works for Severe Thunderstorm and Flash Flood Watches and Warnings. You can also send winter weather alerts to supervisors only.

Automatic All Clear

When the NWS alert expires, your team is automatically told the threat has passed. If your workflow sends a channel message, the all clear goes to that same channel. If it sends a mass alert, an informational alert goes out to the same recipients.

What to expect

Only real alerts trigger workflows. NWS sends test, exercise, and system messages through its live feed. weavix filters these out, so your team won't be alarmed during an NWS system test.
No duplicates. The same NWS alert will never trigger the same workflow twice.
Expired alerts are ignored.

Walt Leaves Site

The Walt Leaves the Site workflow helps with device management by alerting the right people as soon as a walt leaves your site. The user can be reminded to bring it back, and supervisors or other team members can step in to help keep walts onsite and from getting lost.

How to Create Walt Leaves Site Workflow

Set up the trigger

Go to Workflows and click Add Workflow.
Name your workflow, make sure Enabled is checked, and select the site(s) you want to monitor. Click Save, then move to the Workflow tab.
Click Add under Add Trigger and select walt leaves site from the dropdown.
Optionally, add a condition to limit the workflow to a specific group, such as a certain company, craft, or tag. If you leave it blank, the workflow applies to everyone at the site.

Add the Actions

Click Then to add your action.
One common action is to send a message to a leadership channel letting them know that someone has left the site with a walt.
Select the person first name and person last name variables. You can also insert the walt ID that will list the walts Serial Number.

Add a second action to let the person who left know they still have their walt and need to bring it back.
Click Then to add another action and select Send alert.
Select the site
Enter your message
Select the alert type. You will need to create a specific alert type under the Alert Types tab in console.
Set the target to Self, and make sure the box that sends the alert to the radio that left the site is checked.
Click Save.

When you're done, your workflow will have two actions that both run when the one trigger occurs.

Wrapping Up

After a workflow has been triggered, you can review its history on the History tab under that workflow. It shows the date the workflow was triggered, the person who triggered it, and the site it was triggered on.

If you have an alert set up as an action for one of your workflows, you can go to the Mass Alerts tab and review the details of that alert. This allows you to see who all received that alert and who acknowledged it.

Pro Tip! The History tab and Mass Alerts tab are great for audits. You can review every time an SOS button was triggered.

Workflows take the guesswork out of responding quickly. With an SOS workflow, the right people know right away when a team member needs help. With a Weather Alerts workflow, your team gets timely, specific information when severe weather is headed your way, without anyone having to watch the forecast. Customize your triggers, messages, and recipients to match your organization's safety protocols.