Issues
Receive the selected repository’s issues webhook with opened already selected in Actions. Edits, comments, closures and reopenings are excluded.
Workflow template
Turn newly opened GitHub issues into Trello cards for your triage list. Use the issue number and title as the card name, with repository, author, creation time and GitHub link in its description.
How it works
Receive the selected repository’s issues webhook with opened already selected in Actions. Edits, comments, closures and reopenings are excluded.
Create a card in the selected Trello list, naming it [#number] title. Add repository, issue number, author, creation time and source URL to the description without copying the issue body.
The result
The card provides a place to triage the issue in Trello while retaining a direct link to its GitHub source.
[#42] Improve the project onboarding checklist
Repository: example-studio/project-tracker Issue: #42 Opened by: alex-example Created: 2026-09-15T10:00:00Z Open issue: https://github.com/example-studio/project-tracker/issues/42
Fictional issue. No issue description, attachment, label or assignee mapping is prepared for the card.
Before activation
Connect the FastHook GitHub App with access to the intended repository and choose it in the trigger. Keep opened selected in Actions for new issue creation events.
Connect Trello, browse to the destination board and choose its triage list in Create issue triage card. Confirm the connection can create cards there and review who can access the board.
Activate and wait for GitHub to connect, then open a fictional issue in the selected repository. Check the card’s list, number-and-title name, source metadata and GitHub link.
Card creation without status synchronization. Only new opened events received after activation create cards. Existing issues are not imported. Later edits, comments, closures and reopenings do not update or move the Trello card.
The description contains selected metadata. The prepared card includes repository, number, author, creation time and source link. It does not copy the GitHub issue’s body or attachments, and it does not assign Trello members or labels.
Board access and duplicate cards. Board members can read the copied title and repository details; GitHub access is still required for the source issue. The workflow creates a new card rather than finding an existing one, so manual reruns can create duplicates.
The list you select in Create issue triage card. Choose its board first, then the intended triage list, using a Trello connection allowed to create cards there.
No. The prepared trigger listens for opened only, and the action only creates cards. Later GitHub status changes do not move, archive or update them.
No. It contains number and title, repository, author, creation time and GitHub link. Body text, attachments, labels and assignees are not mapped.
Yes. There is no existing-card lookup or update step. A manual rerun can create another card for the same GitHub issue.
Turn published GitHub releases into Trello cards for release checks and follow-up tasks.
View template →Turn newly opened GitHub pull requests into Trello cards for your review queue.
View template →