Workflows

Automate many of the manual data tasks you do every day.

Updated over a week ago

Note: Workflows are available as an additional element on the Standard, Premium, and Ultimate plans. They can be added in Settings > Billing.


If you're like many other organisations, you probably have a lot of manual tasks you need to do every day/week/month.

Manual tasks usually end up getting in the way of making a difference, so we built a workflows products specifically to automate many of the manual data tasks you do every day.


How workflows work

Workflows are made up of triggers, filters, and actions. I.e. If something happens (trigger) and it meets this criteria (filters), then complete this task (actions).


Triggers

Triggers are what cause a workflow to run. For example, a trigger could be every time a particular donation form is submitted.

The following triggers are supported:

Filters

Filters let you only run your workflow when certain criteria are met. Using the form submission example above, you could add a filter to only run the workflow if the donation amount is more than £100.

Note: The filters you can add depend on the trigger you're using, see the individual trigger articles to see more information.

Actions

On to the fun stuff. Actions are the things that actually happen when a workflow is triggered, once the filters have passed. This is where the automation kicks in - you can execute one or more actions to do something you would usually have done manually.

Note: The actions you can add depend on the trigger you're using, see the individual trigger articles to see more information.

Action: Trigger a Zap from a workflow

See details over on our Zapier guide article


Frequently asked questions

Workflows sound great! But I need a trigger that isn't yet supported.

We'd love to hear from you! Please let us know at [email protected] - we're going to be improving this feature directly based on feedback and real-world use-cases.

Can a single Beacon workflow trigger multiple Zaps?

Yes! While there can be only one action on a workflow that ‘Triggers a Zap’, there is no limit on the number of Zaps that can be registered on them.

Did this answer your question?