Before looking at specific use cases, it’s essential to note that you will need to update your existing customers or invoices when creating/updating a rule, to ensure they’re aligned with it. You can refer to our main article for more insights on what smart rules are and how they work.Documentation Index
Fetch the complete documentation index at: https://docs.upflow.io/llms.txt
Use this file to discover all available pages before exploring further.
Manually bulk update customers/invoices
If you created or updated a rule in Upflow, you must take into account that it’ll apply only when the rule’s trigger (and conditions) are met. For existing customers (or invoices), you must ensure the following option is ticked:
Rule update or manual application update
If you just edited an existing and active rule, and wish to apply this new behavior to existing objects (customers or invoices), we recommend you deactivate the rule, and reactivate it while ticking the option “Apply to all existing objects matching the rule’s conditions” (screenshot above). Wait for the sync to happen (delay depends on the volume to update). Then go to your Customers or invoices list view, refresh and check the data.Simple rule to assign a workflow

Rule to assign a workflow based on a filter

Rules based on the customer threshold
If you decide to use the following trigger in your rules, “When a customer outstanding amount threshold ‘exceeds/falls below’ amount ”, you need to take into account that if:- Existing customers already match this amount range, they will not be impacted by the rule.
- If they are updated (field value, balance), but are still within the same amount range, it will not trigger the rule.

Solutions
First, if you just created the rule, don’t forget to mass assign the same behavior manually to existing customers, as detailed higher in the article. You can create additional rules to take care of special cases as the example above. It can be based on the due or overdue amount (if you need both, you’ll need a rule for each):

Threshold rules - double management
If you use a rule based on the outstanding threshold, don’t forget to create an additional one to support the reversed behavior. If your rule is to unassign the workflow when the customer threshold falls below a certain amount, you’ll want another rule to reassign a specific workflow when it exceeds a certain amount. Feel free to share your needs and context with our Support team if you’re not sure how to set this up.Assign users based on custom fields
User email address

- The custom field must absolutely be a TEXT type and contain the user’s email address.
- If you need to assign more than one person, use one field per user.
- Ensure the users are created in your Settings > Users, even if not invited.
One of the fields is empty
If you decide to automatically assign users to your customers, based on custom fields, but one of the fields is empty, rest assured, the users present in the other one(s) will still be assigned. Let’s say you need to assign three users to (some of your) customers:- AE email
- CSM email
- Sponsor email
Rule to assign users based on a custom field

Rule to assign users based on filters
