Automate Discord + Trello
Community chat with an automation-friendly API. 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.
Support First Responder is a ready-made agent built around Discord; point its last step at Trello to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Discord side, works out what it means, and only then decides what — if anything — should happen in Trello.
When a message posts in a channel in Discord…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When a member joins in Discord…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a keyword appears in Discord…
…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 post channel messages in Discord — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can DM members in Discord — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can publish digests in Discord — with the reasoning recorded in the run’s receipt.
Discord to Trello, setup template
Start with the discord-api node and a custom-api call to api.trello.com. Configure the Discord 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": "1b8813e3-32ca-4689-a2e7-3c28d129e7ca",
"name": "Discord → Trello",
"nodes": [
{
"id": "29a9af81-8931-4ec9-aa1a-30741804cd9e",
"text": "Watch Discord",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-discord-message",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"channelId": "CONFIGURE_CHANNELID"
},
"description": "Setup template for Receive Discord Message. Listen for incoming Discord messages in a specified channel and trigger the workflow when a new message is received. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "c5421bb8-64ee-4788-afc0-7fde4e42dd68",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Discord 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": "088440df-c2cc-4233-a993-756c75bd9566",
"text": "Call Trello",
"x": 512,
"y": 528,
"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": "107bbff9-c284-4b64-ae57-dbdfc002f3e4",
"start": {
"id": "29a9af81-8931-4ec9-aa1a-30741804cd9e",
"type": "output"
},
"end": {
"id": "c5421bb8-64ee-4788-afc0-7fde4e42dd68",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "819c7f08-a70a-490b-a881-ac5f163faa16",
"start": {
"id": "c5421bb8-64ee-4788-afc0-7fde4e42dd68",
"type": "output"
},
"end": {
"id": "088440df-c2cc-4233-a993-756c75bd9566",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Receive Discord Message
Listen for incoming Discord messages in a specified channel and trigger the workflow when a new message is received.
- channelId — The ID of the Discord channel to monitor Current example:
CONFIGURE_CHANNELID.
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 Support First Responder
Support First Responder is a working agent built around Discord. 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 Discord (an API key pasted into the vault). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; discord-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.
Discord and Trello — common questions
Can I connect Discord to Trello without writing code?
You can build it entirely from the canvas. Authorise Discord with an API key pasted into the vault, Trello with an API key pasted into the vault, then tell the agent what community questions answered from your docs should look like once Trello is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Discord to Trello automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles community questions answered from your docs the way a colleague would — reading the Discord context, judging it, then writing to Trello with the reasoning recorded.
Does my Discord and Trello data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Discord, Trello and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Discord and Trello run leave behind?
You get an auditable trail rather than a success flag. It shows the Discord context the agent worked from, the judgment it made about email requests become cards instantly, and the exact change applied in Trello, with approvals attached where you required them.
