Trello automations

At sustained high activity — common on large team boards during sprint transitions or bulk imports — Trello's 300-requests-per-10-second API key limit is exhausted fast, especially when each card event triggers multi-step automations that fetch additional data (checklist items, member details, due dates) as separate API calls. Once 200 rate-limit errors accumulate in a single 10-second window, Trello locks out all requests for that API key for the rest of that window, meaning unrelated automations sharing the same API key also go dark. The /1/members/ endpoint carries an even stricter cap of 100 requests per 900 seconds, so any workflow that resolves member details at scale will hit this ceiling long before the primary rate limit becomes an issue.

If your automation in Zapier, Make, n8n, Power Automate, or Pipedream references a Trello workspace by its slug rather than its numeric ID, a workspace rename by any admin silently breaks every automation that touches it — no error is thrown at configuration time, and the failure only surfaces when the workflow runs and can't resolve the resource. This is a silent data-loss scenario in workflows that create or update cards, because the action silently fails or targets the wrong workspace. Always verify your integration configurations use numeric board and workspace IDs, not human-readable slugs.

Trello enforces a hard limit of 5,000 open cards per board and begins surfacing warnings at 4,500. Automations that create cards on a shared board — such as form-to-card workflows or CRM sync integrations running across Zapier, Make, n8n, Power Automate, or Pipedream — can silently fail or return API errors once this threshold is hit, often without a clear error message propagated back to the automation platform. Additionally, fetching all cards with their associated actions in a single API call triggers the API_TOO_MANY_CARDS_REQUESTED error well before the hard cap; automations must paginate or fetch card actions in separate follow-up requests to avoid this failure mode at scale.