Issues
Emit an event when GitHub delivers the issues webhook.
→
Ready-made Workflow
Create Trello cards from new GitHub issues
Turn newly opened GitHub issues into Trello cards for your triage queue. Each card includes the issue title, number, repository, author and a link back to GitHub. Connect the FastHook GitHub App and Trello, select the repository you want to track, then choose a destination board and list. The Actions filter is prefilled with opened: edits, comments, closed and reopened issues do not create cards. Includes a fictional English issue example. Only new webhook events received after activation are processed; existing issues are not imported. This is one-way card creation, not status synchronization. Issue bodies and attachments are not copied. Issue titles and repository details become visible to members of the destination board.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Create issue triage card
Create a card in a Trello list.
Before activation
Connect your accounts in the Draft
GitHub
Connect your own GitHub account and review the provider settings used by this Workflow.
Trello
Connect your own Trello account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
GitHub · Trello
Create Trello follow-up cards for published GitHub releases
Turn published GitHub releases into Trello cards for release checks and follow-up tasks. Connect the FastHook GitHub App and Trello, browse to the repository to track, then select a destination board and list. Each card includes the release tag, optional title, repository, author, pre-release flag, publication time and GitHub link. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not create cards. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates a tracking card; it does not deploy code, verify deployment or synchronize later changes. Card details become visible to members of the destination board. Manual workflow reruns or unpublishing and republishing a release can create duplicate cards.
- 1. GitHub · Release
- 2. Trello · Create release follow-up card
GitHub · Trello
Create Trello review cards from new GitHub pull requests
Turn newly opened GitHub pull requests into Trello cards for your review queue. Each card includes the PR title, number, repository, author, source and target branches, draft flag, creation time and GitHub link. Connect the FastHook GitHub App and Trello, browse to the repository to track, then choose a destination board and list. The Actions filter is prefilled with opened. Draft pull requests are included, with their draft flag shown in the description. Edits, new commits, reviews, closed and reopened PRs do not create another card. Includes an independent fictional English review example. Only new webhook events after activation are processed; existing PRs are not imported. This is one-way card creation, not review assignment or status synchronization. PR bodies, code changes and attachments are not copied. Card details become visible to members of the destination board. Manual workflow reruns can create duplicate cards.
- 1. GitHub · Pull Request
- 2. Trello · Create pull request review card
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own GitHub, Trello accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.