Operations & Automations Limits

Yomna Yasser

 

 

Hello,

I’ve heard that adding paid members to our workspace can increase the automation limit by an additional 10,000 operations, up to a total of 200,000 or 250,000 operations.

Can anyone clarify whether adding paid members affects our main automation quota, or if it creates a separate quota for the new users?

We often reach our 150,000 operations limit early in the last week of the month, and I’m looking for ways to reduce the number of operations.

Additionally, I’m curious about the cost implications of adding paid members and whether this could help us extend our automation limits effectively.

Thanks in advance for your help!

DiMaggio Tucci

According to this support article , automation runs are counted on the workspace, not the user. The user adds 10,000 but, as you mentioned, only up to 250,000 for the entire workspace. That puts the limit to 25 users before adding users does not help with the quota.

If you are not at that cap yet, the pricing for a new user is at least $10 a month per user (when billed annually). This would come to around $250 per month to maximize your automation quota. If you get Trello enterprise, it could be lower than $10 per user (as they negotiate those prices on a case-to-case basis), but, according to their estimating tool, it usually ends up more expensive per user until you hit around 2255 users. And you only need 25 to hit the automation limit. So I doubt Trello Enterprise would keep your prices down.

 

  If it works for you, you could split your boards into multiple workspaces (that would each need to be paid for).

If you are hitting your limits, you might want to consider if what you are trying to accomplish with Trello is reasonable considering it's intended use case as a project/task management and note taking tool.

Are you trying to use Trello as a sort of generic database, like you would create for a web application? If so, Atlassian directly states that Trello is not designed for this. Here, it states:

Note: Don't use lookup actions as a generic database-style functionality in Trello. Creating lookup tables with thousands of cards will result in poor performance.

I'm not saying you're doing this, but, if you were, then just be aware that Trello is not the right tool for it.