Project management

Trello stays simple by refusing to be your database, which is exactly the problem once it has to be one

Trello's whole appeal is that a board, a list and a card are all anyone needs to explain. No setup, no admin screen, no field types to configure — you drag a card from "To do" to "Done" and everyone understands what happened.

That same simplicity is the ceiling. The moment a business wants to know how many cards came from the website this month, or wants a card to also become something in another tool, Trello has nothing built in to answer that — a Power-Up gets bolted on, or somebody starts counting cards by hand.

  • REST API and webhooks per board
  • No native custom fields on the free tier
  • From €1,700 plus service fees
The tool

What Trello is, and where its simplicity runs out

Trello is a board built from three ideas: lists, cards and moving a card between lists. A card can carry a description, a due date, members, labels and checklists, and Power-Ups add narrow extra features — a calendar view, a custom field, a link to another tool. It has a documented REST API and webhooks per board, plenty for reading and writing cards; the API itself is not where Trello integrations get complicated.

Where they get complicated is that Trello deliberately keeps structure light. Custom fields exist only as a Power-Up, with real limits on the free plan, so what looks like a status field on one board might be a label on another and a word in the card title on a third. A connection has to be built against how a specific team actually uses their board, because there is no Trello standard to build against.

What goes wrong

Three things that go wrong around a Trello board

Trello's lack of structure is a feature for a small team and a liability the moment the board has to answer to something outside it.

A support request becomes a card, eventually

A ticket comes in by email or a website form, and someone has to open Trello, pick the board, and write out a card with the customer's name and issue by hand. Between the email arriving and the card existing, the customer has already sent a follow-up asking whether anyone saw the first one.

What you see instead

A form submission becomes a card the moment it arrives, in the right list, with the customer's details in the description and the right label already attached.

A card moves to "Done", and nobody outside Trello finds out

Dragging a card to the last list is the entire signal Trello gives that something finished. If a customer is waiting on that completion — a design approved, an order packed — somebody still has to notice the move and tell them separately, usually by opening the same three tabs they open for everything else.

What you see instead

The move itself sends the message: an email to the customer, a note in a shared channel, or a status update in a portal, the moment the card lands in the list that means done.

Everyone invents their own version of a field Trello does not have

Without a real custom field, a priority or a client reference ends up as a colour label, a word in the title, or a line in the description that only makes sense to whoever wrote it. Three team members invent three conventions, and a report across the board means reading every card by eye.

What you see instead

We agree one convention per field before building anything, and read it consistently through the API — so a report is a query, not an afternoon of scrolling.

The bill for doing it by hand

What a Trello board that nobody wires up costs

The honest starting point with Trello is usually low volume: a support board, a small content calendar, a handful of onboarding checklists. Creating a card by hand from an email takes two to three minutes; at ten a day that is half an hour, not a number that justifies a project on its own.

What tips the balance is not volume, it is a customer waiting on the other end of a card move. A design approval that sits done in Trello for two days before the client hears about it is a two-day delay on every job, and that adds up in a way retyping ten cards a day does not.

What we build

We build the thing on the other end too

With Trello the honest first question is whether the board should stay a Trello board at all, or whether the team has outgrown it and a small custom tool would serve them better — we say which before quoting either.

A connection needs two ends. Plenty of agencies will build you the API call and hand you a JSON payload; that is the easy half. The harder half is what the data lands in — a website, a webshop, a portal your customers log into, an internal tool that replaces a spreadsheet. JKC builds both ends, which is why the connections we build tend to keep working: nothing about the receiving side is a black box to us.

API integrations

The connection itself: authentication, field mapping, rate limits, retries and a queue that survives the other system being down for an hour. Built against the documented API where there is one, and against whatever the vendor really offers where there is not.

Websites

WordPress sites that read from your systems instead of repeating them by hand: a careers page fed by your HR system, a team page that follows your payroll, prices and availability that are the real ones.

Webshops

WooCommerce shops where the order is the last time anyone types it: it becomes an invoice in your accounting package, a label at your carrier, a stock mutation in your warehouse, and a line in your CRM, on its own.

Web applications

When the process does not fit any standard product: a customer portal, a quoting tool, a planning board, a dashboard that reads three systems at once. Built on your data, with your systems as the source instead of a copy of them.

What can be connected

What can be connected between Trello and the rest of your stack

Because Trello has so little built-in structure, the first step on every project is agreeing what a label, a due date or a checklist item actually means on your board — the connection is built on that agreement, not on a Trello standard.

  • Forms and emails as new cards

    A website form or a support inbox becomes a card in the right list, sender's details in the description and a label attached automatically, instead of somebody creating it by hand.

  • A card reaching a list triggers a message or an update

    A card landing in a chosen list — Done, Approved, Shipped — sends a Slack message, an email to the customer, or updates a status elsewhere, instead of relying on someone noticing.

  • Cards kept level with a task list in another tool

    Cards mirrored into ClickUp, Asana or a CRM's task list for teams who want Trello's simplicity on one side and more structure on the other, matched on a shared card ID.

  • Checklist completion reported without opening the board

    The percentage of a card's checklist that is done, read on a schedule and shown on a dashboard or sent as a weekly summary, no need to open Trello at all.

How it works

How a connection gets built at JKC

The same four steps every time, whichever tool it is. Nothing here is a workshop you pay for: step one exists because scoping a connection wrong is the single most expensive thing that can happen to it.

  1. 1. We look at what is actually being retyped

    Not "which fields exist" but "which fields does somebody currently move by hand, how often, and what breaks when they get it wrong". Most projects turn out to need two or three flows, not a full two-way sync of everything. That conversation is what keeps the quote where it is.

  2. 2. We pick the route, and say why

    A maintained connector from the vendor, a platform like Make or Zapier, or a custom integration against the API. Cheapest first, not custom first: if a supported plugin does exactly what you need, that is the answer and we will tell you so. Custom is for the cases where the off-the-shelf option would need so much configuring that it becomes the fragile option.

  3. 3. We build it to survive the other system

    Every connection ships with retries, a queue and an idempotency key, so an order that arrives while the other side is down is delivered later rather than lost, and a retry does not create a second invoice. On a test environment first where the vendor offers one, so the first thing your real administration sees is a working connection.

  4. 4. We hand it over with the failure modes written down

    Which alerts you will get, what each one means, what to do about it, and who to call. Plus the credentials in your own name, in your own vault — not in ours. A connection nobody but us can maintain is a connection you do not own.

More about system integrations at JKC

After it goes live

A connection that fails silently is worse than no connection

This is the part most quotes leave out. A connection that stops working without telling anyone is worse than manual work, because with manual work at least somebody notices when it does not get done. Every connection JKC builds is monitored, and the monitoring is not an upsell — it is in the service fee.

An alert per failed message, not a monthly report

A message that does not get through raises an alert the same hour, with the record it was about. Not a dashboard you have to remember to look at.

Replay, not re-enter

Anything that failed sits in a queue and can be sent again once the cause is fixed, in order. Nobody goes back through yesterday to find the four orders that did not land.

We watch the vendor's changes, so you do not have to

APIs get versioned, deprecated and rate-limited. When a vendor announces a change that affects your connection, adjusting to it is part of the service fee, not a new project.

What it costs

From €1,700, and the biggest variable is who built the other end

For Trello specifically: because there is no standard structure to build against, the quote depends more on how consistently your team already uses labels, due dates and checklists than on the platform itself — a tidy board is a cheaper connection than a messy one.

A connection starts from €1,700 plus a monthly service fee, which covers the monitoring, the queue and keeping up with the vendor's API changes. Work outside a fixed scope is €95 per hour.

What moves the number is not the tool — it is how well the system on the other end is known. If JKC built your website, your webshop or your web application, we already know its data model, its edge cases and where its stock numbers really come from, and a connection into it is mostly configuration and testing. If it is a system we have never opened, we start with a short technical check of both sides and quote after that, so you are not paying hourly for us to work out the basics.

Two more things that move it, in our experience more than anything else: whether the tool has a real API or only a CSV export, and whether the sync has to go both ways. One-way is roughly half the work of two-way, because two-way means deciding, per field, which system wins when they disagree — and that decision is the expensive part, not the code.

Questions

Frequently asked questions about connecting Trello

Yes for reading and writing cards, lists and checklists — that is the core API and it works the same on every plan. What the free plan removes is Trello's own custom fields and its cap of one Power-Up per board, which rarely blocks a connection because we usually read information from labels, due dates or the description anyway, precisely because custom fields are not reliably available across plans.

Often next to this one

Tools that often sit next to this one

Almost nobody connects one tool. These are the ones that come up in the same conversation, either because they sit in the same part of the business or because people ask for the two together.

See all integrations

Free, 10 minutes

Not sure where the manual hours actually go?

That is what the Growth Scan is for. Ten minutes, no sales call attached: you get back where the double work sits, which connection would pay for itself first, and which one honestly would not.

Do the free Growth Scan