Running on Trello?

Trello Power-Up broken or Butler looping? We unstick it.

Trello is simple, which is why a board grown to five thousand cards, a Power-Up that will not authenticate after an OAuth rotation, or a Butler rule firing a hundred times an hour feels disproportionately painful. We split the boards, rewire the Power-Up, and bring the API integrations back to a sane rate.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

trello-butler.log

still firing

What it is

Trello at a glance

Trello is a visual kanban tool launched in 2011 by Fog Creek Software and spun out as its own company in 2014. Atlassian acquired it in 2017, and it now sits alongside Jira and Confluence in the Atlassian product line. The core idea is simple: boards hold lists, lists hold cards, and cards hold checklists, comments, members and attachments.

The platform covers boards, lists, cards, labels, members, custom fields, workspaces, templates, Butler automation (if-this-then-that rules with daily, calendar and due-date triggers), Power-Ups (plug-ins that extend boards and cards with external integrations), a REST API with OAuth 1.0a, and webhooks on nearly every object. It supports Atlassian Access for SAML SSO at the organisation level and integrates with Jira, Slack, Google Drive, Microsoft Teams and many other tools. Most of the pain we see comes from Butler rules that cannot find the list or label they reference after a rename, Power-Ups that break on manifest or OAuth changes, and webhook consumers that stop signing requests the way Trello now requires.

Type
Visual kanban project management tool
First released
2011
License
Proprietary SaaS, per-user pricing with Free, Standard, Premium and Enterprise tiers
Maintained by
Atlassian (via Trello)
Typically used for
Personal task tracking, team kanban, simple project management, editorial workflows

The honest version

Trello pros and cons

No technology is all upside. This is where Trello earns its place and where it tends to cause trouble.

Where Trello is strong

  • The kanban model is immediately understandableLists as columns, cards as work. A new team member is productive on the board inside an hour without a training session.
  • Butler covers routine automationRules, card buttons, board buttons, due-date commands and calendar triggers handle the common automation needs without pulling in Zapier or a developer.
  • Power-Ups extend without a rebuildCustom fields, calendar, voting, GitHub, Jira, Slack and Confluence integrations drop into a board through Power-Ups, so boards grow capabilities without changing the core model.
  • A solid REST API with OAuthEvery object in the data model is reachable through the API, webhooks fire on most state changes, and the OAuth flow works with external user accounts for third-party apps.
  • Low friction price at the entry tierThe Free tier is genuinely useful, Standard is cheap enough to drop onto a small team without a procurement discussion, and the upgrade path is linear.
  • Part of the Atlassian familyAtlassian Access covers SAML SSO at the org level, and the Jira and Confluence connections are native rather than third-party, which matters for teams already on the suite.

Where Trello bites

  • Scales badly past a few thousand cardsBoards with many thousands of cards become slow in the browser, especially with several Power-Ups enabled, and the archive is not a performance solution so much as a graveyard.
  • Reporting is thinThe built-in dashboards do basic counts; anything cross-cutting (cycle time, throughput, WIP by label) needs a Power-Up, a separate BI tool, or a custom integration against the API.
  • Butler is powerful and fragile at the same timeRules reference lists and labels by name, so a rename quietly breaks them. There is no inventory view that shows which rules are broken, and nothing enforces review.
  • OAuth 1.0a is datedThe API still uses OAuth 1.0a for user authorisation, which is rare in modern integrations, and libraries for it are not as current as the OAuth 2.0 equivalents. Writing a new Power-Up has more boilerplate than it should.
  • Permissions are coarseBoard-level access, member roles and workspace settings do not reach into per-list or per-field control, so a board that contains both public and sensitive cards usually has to be split.
  • Power-Ups are an extra line itemThe Free and Standard tiers cap the number of Power-Ups per board, and heavy Power-Up users end up on Premium or Enterprise for the limit rather than the features.

Sound familiar?

Common Trello problems we fix

The Trello problems that bring people to us, and what you have once each one is fixed.

Butler command skipped: list missing

Butler rules break after a list rename

A list renamed from 'Done' to 'Shipped' leaves every rule that references it skipping silently. Automation stops moving cards and nobody notices until the backlog starts to grow in the wrong column.

Butler rules bound to current lists

429 rate limit: 300 per 10s

API client throttles out

An integration listing cards and writing updates without respecting the per-token rate limit, hitting 429s partway through a sync and giving up without a resume point.

Client backs off and resumes

Power-Up manifest capabilities missing

Power-Up fails to load after a manifest update

A manifest schema change that added required capability fields, or a Power-Up built against an older iframe sandbox that no longer matches the current origin rules. The Power-Up appears in the sidebar but will not initialise.

Power-Up manifest current, loads cleanly

webhook signature verification failed

Webhook deliveries are rejected at your end

A consumer that was written before webhook signature verification was required, or a shared secret that was rotated at Trello without updating the receiver. Events succeed at Trello and fail quietly at your end.

Webhook signatures verified

5200 cards, archiving recommended

A board has grown unusable

Years of cards in one board, no archival pattern, and multiple Power-Ups enabled. Loads are slow, Butler rules are backed up, and new members cannot find what they need in search.

Boards split, archive policy agreed

Butler quota exceeded

Butler rules stop firing after hitting daily quota

A rule that fires on every card creation in a busy board, exhausting the per-day operation budget on the current tier. Automation stops silently for the rest of the day.

Butler scoped within quota

401 invalid key or token

API integrations stop working

A user token that was rotated in Trello without updating the integration, or a key issued against an account that was removed from the workspace. Writes fail with 401 across all endpoints.

Tokens rotated and stored

Atlassian SSO: user not provisioned

SSO succeeds but users land without access

Atlassian Access configured for the organisation but the Trello workspace membership not provisioned from the identity provider, so SSO authenticates the user but they see no boards.

SSO and provisioning aligned

What we do

Trello help, board to Power-Up

Call us for one dead Butler rule, or let us own the whole Trello workspace and Power-Up layer.

Rescue
A board that will not load, Butler rules firing in a loop, or a Power-Up that broke after an update. We get the board usable first and explain the root cause afterwards.
Board architecture
Breaking oversized boards into focused ones, agreeing an archive policy, and naming conventions for lists, labels and workspaces that survive team changes.
Butler automation audit
Rules inventoried against current lists and labels, quotas checked, overlapping rules consolidated, and a review process so new automation does not sprawl.
Power-Up development
Custom Power-Ups built against the current manifest and iframe sandbox, with OAuth 1.0a handled correctly and the Marketplace submission process taken off your plate.
API integrations
Custom webhooks, warehouse exports, Jira and Slack syncs that respect rate limits, verify signatures and survive token rotations.
Managed Tech
Quarterly board hygiene reviews, Butler rule audits, Power-Up compatibility checks against the current API, and an engineer on call when a Trello release reshapes the webhook signing format.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Trello alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Trello questions

Something else? Call+1 737 727 7327

Why does our Trello Butler rule stop firing?

The three common causes are a list, label or card type that was renamed or deleted so the rule can no longer resolve its reference, a quota exhausted for the day on the current tier, and a rule that depends on a user who is no longer a member of the board. The fix is to audit the rules against current board state, consolidate overlapping rules, and often to upgrade the tier if the quota is the real constraint rather than inefficient rules.

How do we deal with Trello API rate limits?

The limit is per API key plus per token, applied as 300 requests per 10 seconds. Clients that respect it batch reads, use ETag and If-Modified-Since where possible, back off on 429 responses and record a persistent cursor so a failed job resumes rather than restarts. Large exports run outside business hours and split across several tokens where the integration allows it.

Why does our Power-Up fail to load after a Trello update?

Trello periodically tightens the Power-Up iframe sandbox, adds required manifest fields and updates the OAuth flow. A Power-Up that was fine two years ago can start failing silently after a current release. We bring the manifest up to the current schema, re-verify the origins and sandbox permissions, and test on a staging board before pushing to users.

Can we migrate from Trello to Jira or ClickUp without losing history?

Mostly yes. Cards, comments, attachments, members and custom fields transfer through the REST API, with the usual caveats: history and audit trails do not come across with full fidelity, Butler rules have to be rebuilt in the target system, and Power-Up data lives per Power-Up so each needs its own export plan. We run the migration on a sandbox workspace first and keep the source read-only during switchover.

How do we handle Trello webhooks reliably?

Four rules cover most of it. Verify the HMAC-SHA1 signature on every delivery, respond with a 200 quickly and do the work asynchronously, make the handler idempotent so a retry is safe, and record every delivery so you can tell a bug in your consumer apart from a Trello outage. A consumer that follows those four survives the normal failure modes.

How much does Trello help cost?

The estimate is free. Describe the board, the tier and what is going wrong, and we return a scope and a price before any changes land in the workspace.

Free estimate

Trello giving you trouble?

Butler audits, Power-Up development, API integrations and migrations. We work on the whole workspace and the integrations around it.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.