Projectrr

Integrations

Projectrr connects to the places your work already happens. Integration credentials live on the product, so each product connects to its own repositories and boards.

GitHub

Link repositories to a product and Projectrr ties code back to issues.

What you get

  • Commits and pull requests that mention an issue key (WEB-14) are linked to that issue
  • Releases cut from linked repos are tracked, with the issues that shipped in them
  • Workflow rules can fire on push, PR opened, PR merged, PR closed and release published
  • Rules can create GitHub issues from Projectrr issues, and push status changes outward

Setting it up

  1. Open your product’s settings and link a repository (owner/repo).
  2. Install the Projectrr GitHub App on that repository so events reach us and we can write back.
  3. Optionally set the repo’s default branch and mark it as a monorepo.

From the CLI:

prr repo link starkey-digital/projectrr --product=<productId>
prr repo list --product=<productId>
prr release sync --product=<productSlug>

Trello

Two-way sync between a Trello board and a Projectrr project.

What you get

  • Cards become issues, and issues become cards
  • Trello lists map to your project’s statuses, so moving a card moves the issue and vice versa
  • New comments travel both ways between an issue and its card (edits and deletes do not sync)
  • Existing boards can be imported in one go
  • Changes arrive by webhook, with a scheduled poll as a safety net for anything a webhook missed

Setting it up

  1. Get a Trello API key and token, and save them against the product.
  2. Link a board to a project.
  3. Map each Trello list to one of the project’s statuses.
  4. Import the cards already on the board.

A project syncs with one board. Linking a second one is refused — unlink the current board first, which also removes its webhook.

From the CLI:

prr trello connect --product=<productId> --key=<key> --token=<token>
prr trello boards --product=<productId>
prr trello link --project=<projectId> --board=<boardId>
prr trello lists --id=<boardLinkId>
prr trello map-lists --id=<boardLinkId> <listId>:<statusId> ...
prr trello import --id=<boardLinkId>
prr trello unlink --id=<boardLinkId>

Loop prevention. An update that arrived from Trello is never pushed back to Trello, and a chain of rules triggering rules stops after three hops. See Workflow rules.

Claude routines

A workflow rule can hand an issue to a Claude Code routine — the agent picks up the issue’s full context, does the work, and comments back on the issue with a link to the session. Configure the routine against a product, then use the Trigger Claude routine action in a rule.

For interactive work, connect your assistant directly over the MCP server instead.

AI assistants and scripts

  • MCP server — Claude, Cursor and anything else that speaks MCP
  • CLI — prr, for terminals, scripts and CI

On the roadmap

Sentry and Linear triggers are selectable in the rule dialog, but nothing sends those events yet and there is no connection to configure — a rule built on one will never fire. Error tracking for Projectrr itself runs on Sentry today; the customer-facing integration is still to come.