Trello vs Monday.com under 50 Dollars a Month Why This Broke Again

I only found out my Trello board had stopped emailing card assignments (again) when someone @mentioned me two weeks late in Slack with a passive-aggressive “Is this still moving forward?”. If you’re trying to manage a cross-functional team working under tight budgets, Trello and Monday.com both look like they should just work. They don’t. Not consistently, anyway — especially not under $50/month. Here’s what happens when you set them up, walk away, and then come back later expecting things to still behave.

1. Card automation failures in Trello automations

If you’ve ever set up Trello’s built-in Automation (previously Butler), you know the sweet moment when it actually triggers — like moving a card to “Ready for Review” automatically after a checklist is completed. But under the hood? There’s no visibility into when these automations silently fail.

I had a board with a rule: when a due date is added to a card, assign it to the member who added the date. That worked for months until one day it didn’t. Logs? Nope. The only way I figured it out was because someone messaged me confused why they weren’t assigned and the card was floating in project purgatory.

Turns out the automation broke because Trello started enforcing rate limits quietly — around 25 actions per 15 minutes — and my sequence included five small automations per card update. It still saves, still lets you test-run it, but it just doesn’t always execute. The only feedback is in the Activity log… buried inside each card… and even that just says “Rule started,” not what failed mid-way.

Also, if your team is using guest accounts on a Free or Standard plan, certain assignments just skip. The automations only partially run, but the system still returns a success code. It’s wild.

The fix? I moved the logic to Integromat (uh, sorry, Make) where I now catch webhook triggers and update card members manually. Which leads to my next chaos moment…

2. Monday.com automation limits make complex flows nearly useless

Monday’s automation builder looks gorgeous — like an engineer and a designer had a baby and named it after a dropdown menu. But building logic-heavy flows on Standard or Basic plans? Ha. I hit the automations cap in about 3 days. If it’s a recurring report or board cleanup job, you’re punished twice: once for the flow complexity, then again for how often it runs.

Here’s the thing: Monday counts every individual automation event against your monthly quota, and some sequences trigger twice for no reason. I had a chain that triggered when a status changed to Complete → then moved the item to a new group → then notified the manager. Randomly once a week, the move and notification fired twice — but the status event log only showed one trigger.

Monday support just told me to “rebuild the automation in a new board.” That’s not a fix — that’s a fresh coat of paint while leaving the wall crumbling underneath :/

Also: The “item created by automations” doesn’t count for filtered views in dashboards. So if you create tasks automatically, they just… disappear from your widgets. This is not documented. I only found out because a team member panicked thinking tasks were deleted. (Nope, just born into the void.)

3. Trello Power Ups do too much or too little

Trello’s Power-Ups are like browser extensions — 10% useful, 90% chaos. On the $5/month plan, you only get access to one Power-Up per board (unless you game it via third-party APIs, but that’s another rabbit hole). I used the Calendar Power-Up once to help my assistant visualize rollout timelines — then enabled Custom Fields — and boom: I had to disable Calendar because I hit the Power-Up limit.

The dumbest part? If you disable a Power-Up, your historical data might vanish. Like, the fields vanish visually — but sometimes the values persist inside the API, and other times they don’t. It depends on the day, apparently 🙃

If you reset and re-enable the Power-Up, Field A might return with data, but Field B? Nope. I tested this by exporting raw JSON from several cards. Multiple fields returned null values even though they previously had input.

A few survival tips if you insist:

• Always export JSON backups before disabling any Power-Up
• Use Trello’s API explorer to check preserved fields, even if the UI hides them
• Create a read-only backup board via Unito or Zapier every weekend
• Set up a separate board just for Power-Up experimentation — not your real workflow
• Don’t trust that Custom Field values will map to Butler conditions unless manually tested
• Never mix third-party Power-Ups with native fields unless you want to scream

4. Monday.com permissions and visibility are a black hole

One time I created a shared board in Monday with task visibility per person — a nice way to share with freelancers without giving them access to financial info. Except as soon as I added a file column, they could download attachments from any row, even ones they couldn’t see in the main table 😐

I triple-checked with support. Their answer was, “as long as they have item access and the file column exists, it’s accessible to all shortcuts.” Which… what? Imagine letting someone view one item and they can now click “Files” from the left sidebar and get access to company logos, contracts, and timelines from other hidden items.

Permissions are tied to the column, not the row. If you want true isolation, you have to create entirely separate boards. But then your automation logic doesn’t carry over unless you’re on a Pro plan. (Not under $50/month.)

Also: Monday’s mobile app breaks permission behavior in completely different ways. I confirmed this by switching between my admin and user accounts on iOS — items hidden on web were still visible on mobile under “My Work.” That’s just… great!

5. Zapier becomes mandatory to bridge blind spots

Against my better judgment I once tried to build an automation where: new cards added in Trello by interns would automatically be categorized, notified via Slack, and logged to Airtable. In theory? Nice. In reality? I ended up with a six-step Zap that looked like spaghetti by the time it worked reliably.

Trello’s native webhook into Zapier sometimes fires twice, depending on how quickly the card is renamed (e.g. add card → rename → assign label). That results in double Slack messages unless you debounce. I wrote a 1-minute Delay followed by a Filter step checking “Card Last Updated Doesn’t Contain Seconds Value from Step 1” — which still feels like dark magic that shouldn’t be necessary.

On Monday, I tried to use their Zapier triggers (“New Item in Board”) to map form submissions to team leads. Problem is: the Zap trigger doesn’t reveal any of Monday’s new custom fields unless they’re manually used in a sample item. So you end up creating dummy entries just to expose the fields. If you forget this step, the Zap simply offers you no fields to pick from, leaving you wondering if Zapier is broken. It’s not. Monday’s API is just… stubbornly lazy.

Still, once stable, Zapier is often the only way to:

• auto-label cards based on complex keyword matching
• filter incoming items by team and forward only relevant rows
• bridge Google Sheets with either Monday or Trello without new logins
• build error logs for silent automation failures (yes, from both platforms)
• send one-time direct messages that aren’t bound to assignment logic

Zapier becomes less optional and more like duct tape holding your sanity together. Just kinda weird that we need third-party glue for things that these platforms pretend to offer natively ¯\_(ツ)_/¯