GitHub + Trello
Connect GitHub and Trello to Keep Code and Projects in Sync
Automate the handoff between your dev workflow and project management so your team always knows what's shipping and when.
Why integrate GitHub and Trello?
GitHub and Trello are two of the most popular tools in any engineering team's stack — one tracks the code, the other tracks the work. But when they live in silos, teams waste time manually updating cards, chasing pull request statuses, and reconciling sprint boards with actual code progress. Connecting GitHub to Trello through tray.ai closes that gap with an automated link between commits, pull requests, and issues on one side, and Trello cards, lists, and boards on the other.
Automate & integrate GitHub & Trello
Use case
Automatically Create Trello Cards from GitHub Issues
When a new issue is opened in a GitHub repository, tray.ai can instantly create a corresponding Trello card in the right list or board. The card gets pre-populated with the issue title, description, labels, and a direct link back to GitHub, giving project managers full context without leaving Trello.
Use case
Move Trello Cards When Pull Requests Are Merged
As soon as a pull request is merged into the main branch on GitHub, tray.ai automatically moves the related Trello card from 'In Review' or 'In Progress' to 'Done' or 'Ready for QA.' Sprint boards stay honest, and there's no lag between code completion and project status updates.
Use case
Sync GitHub Pull Request Reviews to Trello Card Comments
When a reviewer leaves feedback or requests changes on a GitHub pull request, tray.ai can post a summary comment on the linked Trello card. Non-technical stakeholders stay in the loop on review cycles without needing access to GitHub.
Use case
Create GitHub Issues from Trello Cards
When a card is moved into a specific Trello list — such as 'Engineering Backlog' or 'Ready to Build' — tray.ai can automatically generate a corresponding GitHub issue in the right repository. Product and design teams drive work intake from Trello while developers always have a GitHub issue to reference.
Use case
Label Trello Cards Based on GitHub CI/CD Build Status
When a GitHub Actions workflow or CI pipeline fails for a branch linked to a Trello card, tray.ai can automatically add a 'Build Failed' label or move the card to a 'Blocked' list. Teams can triage broken builds directly from their Trello board without digging through GitHub logs.
Use case
Archive Trello Cards When GitHub Issues Are Closed
When a GitHub issue is closed — resolved, duplicate, or won't-fix — tray.ai can automatically archive or move the corresponding Trello card to a 'Closed' list. Boards stay clean and stale cards stop cluttering active sprint views.
Use case
Notify Trello Cards of New GitHub Releases
When a new release or tag is published in GitHub, tray.ai can post a comment on all related Trello cards that shipped in that release, notifying stakeholders that their feature or fix has been deployed. It closes the loop between code delivery and project visibility.
Get started with GitHub & Trello integration today
GitHub & Trello Challenges
What challenges are there when working with GitHub & Trello and how will using Tray.ai help?
Challenge
Matching GitHub Issues to the Right Trello Cards
Without a shared identifier between platforms, reliably mapping a GitHub issue or pull request to its corresponding Trello card is hard — especially at scale across multiple repositories and boards.
How Tray.ai Can Help:
tray.ai supports flexible matching logic using custom fields, naming conventions, or issue numbers embedded in card descriptions or PR titles. You configure the matching rule that fits your team's workflow, no custom code required.
Challenge
Handling Multiple Repositories and Multiple Boards
Enterprise teams often manage many GitHub repositories and many Trello boards at once, which makes routing events to the right destination complex without building separate automations for each combination.
How Tray.ai Can Help:
tray.ai's workflow logic supports dynamic routing based on repository name, label, or team. A single integration can direct GitHub events to the correct Trello board and list without duplicating workflows for every repo.
Challenge
Avoiding Duplicate Cards and Infinite Sync Loops
Bidirectional sync between GitHub and Trello risks creating duplicate cards or recursive update loops when changes in one platform fire events back into the other.
How Tray.ai Can Help:
tray.ai includes conditional logic and deduplication steps that check for an existing card or issue before creating a new one, along with guard conditions that prevent updates from re-triggering the same automation.
Challenge
Keeping Rich Context Intact Across Both Platforms
GitHub issues often carry structured data — labels, milestones, assignees, linked pull requests — that doesn't map cleanly to Trello's card model. That mismatch leads to lost context when syncing between the two.
How Tray.ai Can Help:
tray.ai's data transformation tools let you map, reshape, and format any GitHub field into the right Trello card property, including custom fields, labels, checklists, and card descriptions. Nothing gets lost in translation.
Challenge
Authenticating and Maintaining Connections Across Both APIs
GitHub and Trello each require separate authentication credentials and API token management. Teams that rotate tokens or change repository permissions frequently can break their integrations without warning.
How Tray.ai Can Help:
tray.ai centralizes credential management for both GitHub and Trello, so updating a token in one place applies it across all your workflows. Built-in connection health monitoring flags expiring tokens before they take anything down.
Start using our pre-built GitHub & Trello templates today
Start from scratch or use one of our pre-built GitHub & Trello templates to quickly solve your most common use cases.
GitHub & Trello Templates
Find pre-built GitHub & Trello solutions for common use cases
Template
New GitHub Issue → Create Trello Card
Automatically creates a new Trello card in a designated list whenever a GitHub issue is opened, mapping the issue title, body, labels, and URL to the card's fields and description.
Steps:
- Trigger: A new issue is opened in a specified GitHub repository
- Transform: Extract issue title, description, labels, and URL from the GitHub payload
- Action: Create a new Trello card in the configured list with mapped fields and a link to the GitHub issue
Connectors Used: GitHub, Trello
Template
GitHub Pull Request Merged → Move Trello Card to Done
When a pull request is merged into the main branch, this template finds the linked Trello card by matching the issue or branch reference and moves it to the 'Done' or 'Deployed' list automatically.
Steps:
- Trigger: A pull request is merged into the main branch in GitHub
- Transform: Parse the PR title or body to extract the linked Trello card ID or issue number
- Action: Move the matching Trello card to the configured destination list
Connectors Used: GitHub, Trello
Template
Trello Card Moved to Dev List → Create GitHub Issue
When a Trello card is moved into the 'Ready for Development' list, this template automatically creates a corresponding GitHub issue in the correct repository, pre-filled with the card's title, description, and a back-link to Trello.
Steps:
- Trigger: A Trello card is moved into the 'Ready for Development' list
- Transform: Extract card name, description, and labels from the Trello event payload
- Action: Create a new GitHub issue in the target repository with the extracted card details and a Trello URL reference
Connectors Used: Trello, GitHub
Template
GitHub PR Review Requested → Add Comment to Trello Card
When a review is requested on a GitHub pull request, this template posts a Trello card comment with the reviewer's name, the PR title, and a direct link, keeping all stakeholders informed from within Trello.
Steps:
- Trigger: A review is requested on a GitHub pull request
- Transform: Extract PR title, reviewer username, and PR URL from the webhook payload
- Action: Post a comment on the linked Trello card with reviewer details and a link to the pull request
Connectors Used: GitHub, Trello
Template
GitHub Issue Closed → Archive Trello Card
Automatically archives or moves the corresponding Trello card when a GitHub issue is closed, preventing stale work items from cluttering active project boards.
Steps:
- Trigger: A GitHub issue is closed in the monitored repository
- Transform: Identify the linked Trello card using the issue number stored in the card description or custom field
- Action: Archive the Trello card or move it to a 'Closed' list based on the configured preference
Connectors Used: GitHub, Trello
Template
GitHub Release Published → Comment on Related Trello Cards
When a new GitHub release is published, this template scans the release notes for referenced issue numbers, finds the matching Trello cards, and posts a deployment notification comment on each one.
Steps:
- Trigger: A new release is published in a GitHub repository
- Transform: Parse the release body for issue or card references and look up each corresponding Trello card
- Action: Post a release notification comment on every matched Trello card with the release name, version, and link
Connectors Used: GitHub, Trello