FlowLife
|
Automations

Work moves on its own – once you have approved it

Every automation starts as a dry run. You see what it would send, approve the content and switch it on. If the content changes, it returns to the dry run.

  • so nothing goes out wrong in your name
  • so the next step starts without anyone remembering it
  • so people only do what a person is needed for
Automations
Sample data
When a run is complete
Send a Slack message
OffDry runApprovedLive
  • Message to channelSent
  • Message to channelDry run
  • Text messageRefused

Dry run first

Nothing goes out for real until you have seen it.

Approval of the content

A changed message returns to a dry run until it is approved again.

Chaining

One workflow starts the next.

Variables

Run name, runner, link and date right in the message.

Email on task completion

The message goes out when the task is checked.

Log

Every send, dry run and refusal is listed with its reason.

Slack

To a channel or as yourself.

Text message

To fixed numbers or a number from the form.

Email

From your own domain or your own mailbox.

Calendar

A follow-up, review or kick-off days ahead.

Task boards

A card per run, with links.

Contracts

Send a contract from a template, and the signature moves the workflow on.

Webhook

Any automation platform or your own service.

Schedule Operator

Our sister app with the same sign-in.

Browser extension

Record steps from any website.

Phone browser

Its own bottom menu, with your tasks along.

Which costs more: the machine or another year of the same?

In the strategy call we go through your numbers, show the machine with your process and give you the price. 45 minutes, no slide deck.

Calculate first