A bucket is a group of people defined by rules rather than by a list. People fall into it and out of it as their circumstances change, without anybody maintaining it.

Why they matter

• Entering a bucket can start a workflow.
• Leaving a bucket can start one — or end one.
• A workflow can check whether somebody is in a bucket before deciding what to do next.
• They are the shared definition of "our lapsed customers" that every automation can use.

Naming them

Name a bucket after who is in it, in plain words — "Customers, bought in last 12 months", "Enquiries with no response". You will read these names inside workflow steps months later, and "Bucket 3" will mean nothing.

Check the size before you use one

Product buckets

Product buckets group things you sell rather than people, so a workflow can trigger on "bought anything in this group" instead of naming every product. They are what makes a "you bought a machine, here is the servicing" automation possible without rebuilding it per product.