Connect TrelloContents

How to connect Trello to Layerdock

Once Trello is connected, every new pin becomes a card on the list you choose, with the screenshot attached and the page, element, viewport and reporter in the description.

Before you start

A Trello account with access to the board you want cards on. Nothing to install.

Connect it

1. Authorise

In Layerdock, go to IntegrationsTrello Connect a dock, choose the dock, then Continue to Trello. Trello asks you to grant Layerdock read and write access, which does not expire. Click Allow.

2. Pick a board and list

Click Choose a liston the dock's row. Lists are grouped by board, because names like “To Do” repeat across every board you own.

Trello connects switched off until you do this.There is no sensible default list, and guessing one would drop your client's feedback somewhere nobody is looking.

3. Test

Click Test. A card should appear on the list within a few seconds.

Good to know

Archived lists are hidden from the picker.Trello keeps them addressable by id, so a card created into one succeeds and is then invisible wherever you are actually looking — a failure that looks exactly like nothing happening.

The authorisation never expires. Unlike Jira, there is no token to refresh; the connection lasts until someone revokes it in Trello under AccountApplications.

Trello is outbound only for now.Moving or archiving a card will not resolve the pin. Trello's webhooks are created per board and per token through its API rather than registered once, so two-way sync needs a developer to set up. Linear, GitHub and Jira all sync both ways today.

Only new pins create cards. Replies and status changes do not edit an existing card.

If it stops working

Reconnect needed means the token was revoked in Trello, or the board was closed. Click Reconnecton that dock's row.

If cards stop appearing with no warning, check the list has not been archived and the board has not been closed.

For developers

The webhook endpoint exists and is ready: /api/webhooks/trello. It answers HTTP HEAD with 200, because Trello sends a HEAD to the callback URL when a webhook is registered and refuses to create it otherwise. Signatures are HMAC-SHA1 over the raw body concatenated with the callback URL.

Prefer issues to cards? Connect Linear or GitHub, which both sync statuses back. See all documentation.