Turn Trello cards into Keepr tasks and report time on the card
What the integration does
One integration connects one Trello board to one Keepr project. Inbound, Trello tells Keepr about the board’s cards: a new card, or one moved onto the board, becomes a task in the Keepr project. Archiving a card archives its task and restoring the card restores it; if you name a done list, moving a card into that list archives the task too, and moving it out restores it.
Outbound, Keepr reports tracked time back. Trello has no time-tracking field, so each time entry on a task linked to a card becomes one comment on it, edited when the entry changes and deleted when the entry is deleted. Only time from the integration’s Keepr project is sent, to the second, never rounded.
Before you start
In Keepr you need to be an owner or admin of the organization, or a manager of the workspace that holds the project. Every plan includes integrations: Free runs one at a time, Team three, and Ultimate — trial included — as many as you need.
In Trello you need an API key, its secret, and a token issued for that key by a member who can see the board and comment on its cards. Keepr registers the board’s webhook itself: there is nothing to set up on the board.
1. Create the integration in Keepr
Open Organization settings → Integrations and press “New integration”. Choose Trello, the board — its address, such as , or just its short link — the Keepr project its cards go into, and the name it acts under: Keepr shows its actions as, for example, “Archived by Trello · Website”.
Optionally name a done list, such as Done. Without one, only archiving a card archives its task.
2. Get a key, its secret and a token
Trello shows every comment as written by the token’s member, and the same token registers the webhook. Use a dedicated member of the board rather than yourself. Under Trello’s Power-Up admin page, create a Power-Up (or open an existing one) for your workspace and generate an API key; the same page shows the key’s secret.
Next to the key, follow the “Token” link and authorize it as that member, with read and write access. Trello shows the token once; copy it.
3. Give Keepr the key, the token and the secret
On the integration’s page, open Credentials and press “Set…” next to the Trello credential. Paste the API key, the token and the API secret, and save. There is no address to enter.
Keepr then registers the webhook on the board and shows its state under Inbound webhooks: “Registering…”, then “Registered by Keepr”. Trello signs every delivery with the API secret, so until it is set Keepr refuses them. All three are stored encrypted and afterwards only their first characters are shown.
The webhook Keepr registers
It belongs to the token, watches the board, and sends to . Leave it to Keepr: changing the board on the integration’s page replaces it, and removing the credential or revoking the integration deletes it. If it is gone, “Register again” on the integration’s page creates it anew.
What Keepr sends
An entry is sent once it is finished — a running timer sends nothing until it stops — and only when its task is in the integration’s project and links to a Trello card. Tasks the integration created link that way, and so do tasks started from the browser extension on a card.
Each entry gets one comment naming the member, the duration and the day. An edit rewrites that comment instead of adding another, deleting the entry deletes it, and moving the entry to another card moves the comment. A comment deleted by hand is written again the next time the entry changes.
Imported time is history and is never sent. The integration’s “Recently sent” list shows the latest entries, each with its card, the member, the time Trello holds for it, and whether the last send worked; a failed row says why and what to do.
Pause or revoke
The switch on the integration’s page turns it off without losing anything. While it is off, deliveries are recorded but not acted on, and no time is sent: an entry saved during the pause is sent the next time it changes. Switching it back on takes a slot under your plan’s limit again.
“Remove” next to the Trello credential stops time reporting and deletes the webhook. Revoke is final: Keepr deletes the webhook, destroys the stored key, token and secret, and acts on nothing more. Revoke the token in Trello as well.
If something goes wrong
Every delivery appears under the integration’s recent deliveries with what it did. Nothing arriving usually means the webhook is not registered: check its state under Inbound webhooks. Deliveries refused with 401 mean the API secret in Keepr is not the key’s. “Task already there” means a task for the card existed — for example, one started from the browser extension — and nothing was duplicated.
In “Recently sent”, “Credential rejected” means the token was revoked or expired, and “Issue not found” that the card was deleted or the token’s member cannot see it. “Tool unreachable, retrying” clears on its own once Trello answers. A send that failed for good is tried again the next time the entry changes.