Set up automations

How to get there: Click Settings in the sidebar → Automations (under Content & workflow).

An automation is a small rule you write once: when this happens, do that. It saves someone on your team from checking the board and doing the same thing by hand every day.

Automations are part of the Business plan, and they are included in your trial so you can try them out.

What a rule looks like

Every rule has three parts:

  • When something happens (a new post, someone voting on a post, a post reaching a number of votes, a post moving to a different status).
  • If it matches what you describe (it is in the Bugs category, the person who posted it is a paying customer, the person who voted is a paying customer, and so on).
  • Then ProductLift does something (assign it to a teammate, change the status, add a tag, email selected team members).

A finished rule reads like a sentence: When a new post is created, Category is Bug, assign to Sanne.

Create your first automation

  1. Open Settings → Automations.
  2. On the Rules tab, click New automation in the card header.
  3. Choose Use a template for a starting rule, or give it a name you will recognise later, like "Route new bugs".
  4. Under When this happens, choose what starts the rule.
  5. Under Only if, add the things that have to be true. Leave this empty if the rule should apply whenever the selected event happens.
  6. Under Then do this, choose what should happen and select its target. For example, choose Assign to and a Team member, or Email team members and the recipients. You can add more than one action.
  7. Leave Turn on this automation switched on and click Save automation.

That is it. From now on the rule runs on new activity.

Useful rules to start with

  • Bugs go to the right person. When a new post is created, Category is Bug and Assignment is No one assigned, assign to your developer.
  • Hear about your best customers. When a new post is created, Author segment is Paying customers, email yourself.
  • Spot the popular ideas. When a post reaches 10 votes, add the Popular tag and email a team member.
  • Hand over the planned work. When a post status changes, Current status is Planned and Assignment is No one assigned, assign it to whoever builds it.
  • Know when a big customer wants something. When a post receives a vote, Voter segment is Paying customers, email yourself.

Things worth knowing

"Receives a vote" and "reaches 10 votes" are different things. The first runs on every single vote, so you can react to who voted. The second uses the total shown on the post, including anonymous votes and manual bonus votes. It runs once when the total crosses the number you set. Removing votes and crossing the same number again will not repeat that rule. If you change its trigger, conditions or actions, the updated rule can run on a later crossing. Renaming or pausing it does not reset this limit. The individual vote trigger applies to votes from a user account, including votes cast on their behalf. Anonymous votes and bonus changes only activate the total-vote trigger.

Author segment and Voter segment are different too. Author segment is about the person who wrote the post. Voter segment is about the person who just voted, so it is only available on the vote trigger.

All the "If" lines have to be true. If you add two, a post has to match both. There is no "either/or".

Protect an existing owner. Add Assignment is No one assigned when a rule should only assign posts that have no teammate assigned. Without this condition, Assign to replaces the post's current assignees with the teammate you choose. ProductLift checks this condition again just before a waiting automation starts. If someone has assigned the post meanwhile, no actions run and the history says the assignment changed. The condition checks people assigned to the post; a team selection alone does not count as a person.

Templates need your choices. Select the teammate or email recipients before saving. If a suggested category, customer segment or status does not exist, choose one or create it in settings first. A missing choice never turns the template into a rule for every post.

Rules only apply going forward. Creating a rule never goes back and changes posts you already have.

Changing a status this way does not email voters. The post moves to the new status without a status-change email to its followers. To notify your team separately, add Email team members to the rule.

An automatic status change does not start another status-change rule. This prevents rules from repeatedly triggering each other.

More than one rule can match. Matching rules can run independently. Their position in the list does not give them priority, so avoid rules that set the same field to different values. Within one rule, actions run in the order shown under Then do this.

Check what changed

  1. Open Settings → Automations and select Activity.
  2. Leave the Automation filter on All automations for the full list, or choose one rule.
  3. Read What happened to see the saved changes. For example, Status: Under review → Planned or Assignees: No one → Sanne.
  4. Click the post title to open the post and check its current state.

You can also click a rule's run count, or choose ··· → View runs. Both open the same Activity view with that rule selected.

Completed means the actions finished. An action may say unchanged or already present when the post already had the requested value. In progress means the actions have not finished yet. Failed, partly completed or skipped runs show an explanation.

An Email queued for… entry means the email was queued, not that it has been delivered. Older runs may say their change details are unavailable. ProductLift does not fill in missing history from the rule's current settings.

The saved names and values describe the change at the time it happened. Later changes to a rule or a team member's name do not rewrite those details. The post itself may have changed again since then.

Click Refresh to check for new executions. Use Load more to see older ones. Posts that did not match a rule's conditions do not appear as executions.

When a rule says "Needs attention"

If you delete a category, a tag, a status, or remove a team member from your portal, any rule pointing at it can no longer do its job. Those rules get an amber Needs attention label.

The rule stays where it is and nothing else about it changes. Open it, pick something that still exists, and save.

Pausing and deleting

Switch a rule off with the toggle to pause it. It keeps everything you set up and simply stops running until you switch it back on.

If your plan changes and Automations are no longer included, your rules are paused in the same way. Nothing is deleted, and they start working again as soon as your plan covers them.

To remove a rule for good, use ··· → Delete. This also deletes its execution history. Changes the rule already made to posts stay in place. Deleting or pausing a rule does not undo them.