Automate GitHub + Trello
Where the code — and half the process — lives. Boards and cards — simple enough to automate deeply. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
First-Pass Reviewer is a ready-made agent built around GitHub; point its last step at Trello to finish this hand-off.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from GitHub into Trello.
When a PR opens or merges in GitHub…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When an issue is filed in GitHub…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a release is cut in GitHub…
…an agent can summarise a board in Trello — after reading the context and deciding it should.
When a card is created or moved in Trello…
…an agent can comment on PRs and issues in GitHub — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can open issues with structured detail in GitHub — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can draft release notes in GitHub — with the reasoning recorded in the run’s receipt.
GitHub to Trello, setup template
Start with the github-api node and a custom-api call to api.trello.com. Configure the GitHub source payload, the agent input, and the Trello operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "5ffd0622-e78e-492d-a840-99d3f01d105a",
"name": "GitHub → Trello",
"nodes": [
{
"id": "ab9fe598-ad02-4b17-ac50-c4f36e6bfef2",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "00ced482-2b19-4041-afc7-9bc960dc29a2",
"text": "Read GitHub",
"x": 512,
"y": 336,
"isEditing": false,
"type": "github-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_AUTHENTICATED_USER",
"owner": "CONFIGURE_OWNER",
"repo": "CONFIGURE_REPO"
},
"description": "Setup template for GitHub API. Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "7916bda0-fa48-482e-a144-0bb460de6ebc",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the GitHub item. Decide whether it warrants action in Trello, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "e49fa9f4-af6b-4d49-af96-6e37ae22a0e6",
"text": "Call Trello",
"x": 512,
"y": 720,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.trello.com/1/cards?key={key}&token={token}",
"method": "GET",
"authType": "None",
"query": "",
"headers": "{}"
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "c0d92a22-13bd-40d9-a152-e14b183ac31e",
"start": {
"id": "ab9fe598-ad02-4b17-ac50-c4f36e6bfef2",
"type": "output"
},
"end": {
"id": "00ced482-2b19-4041-afc7-9bc960dc29a2",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "59f7136d-fce1-4fae-a729-4935089335f4",
"start": {
"id": "00ced482-2b19-4041-afc7-9bc960dc29a2",
"type": "output"
},
"end": {
"id": "7916bda0-fa48-482e-a144-0bb460de6ebc",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "9e38392b-2e0d-40ac-ac28-a9f1183ffa7c",
"start": {
"id": "7916bda0-fa48-482e-a144-0bb460de6ebc",
"type": "output"
},
"end": {
"id": "e49fa9f4-af6b-4d49-af96-6e37ae22a0e6",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure GitHub API
Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search.
- action — The action to perform on GitHub Current example:
GET_AUTHENTICATED_USER. - owner — The owner of the repository (not needed for account-level or search actions) Current example:
CONFIGURE_OWNER. - repo — The name of the repository (for CREATE_REPO: the name of the new repository) Current example:
CONFIGURE_REPO.
Configure Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
https://api.trello.com/1/cards?key={key}&token={token}. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Install First-Pass Reviewer
First-Pass Reviewer is a working agent built around GitHub. Install it, point its last step at Trello, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Trello (an API key pasted into the vault) and GitHub (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; github-api does the reading and custom-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
GitHub and Trello — common questions
Can I connect GitHub to Trello without writing code?
No code is required. Add both connections in the vault (GitHub uses one OAuth sign-in, Trello uses an API key pasted into the vault), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping GitHub to Trello automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the GitHub item in full and decides — whether it matters, how to summarise it, and what belongs in Trello. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my GitHub and Trello data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: GitHub, Trello, and your chosen model provider — which can be a local one.
What does a GitHub and Trello run leave behind?
Every run is recorded end to end — the GitHub items examined, the decision and its reasoning, the resulting Trello write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
