swfte
Contact Us

Integration guide

Trello integration for AI agents and workflows

Swfte Studio has a Trello node with six actions in its shipped data: get a board’s lists, get a board’s open cards, create a card, add a checklist, add checklist items and add a comment to a card. A workflow can read a board and add cards with checklists, with a person approving before it does.

Trello is listed in the catalogue under productivity. There is no Trello entry in the MCP tool list, so Trello is a workflow node and not an MCP server. Nothing in the data moves, archives or deletes a card.

Built in Swfte Studio, run as a governed workflow, and held to the same rules as any governed agent.

Build with AITalk to our team

Trello at a glance

Catalogue
Productivity
Actions in the shipped data
6 (2 read, 4 write)
Credential type shown
A stored credential, referred to by id
MCP server
None in the MCP tool list
Shipped templates that use it
multi integration daily digest, trello board automation

What you can do with Trello

Every action below is read from a node in a shipped workflow template. Nothing is listed that the data does not show.

Trello actions in the shipped workflow templates
ActionTypeOperationWhat the data shows
Get Board ListsReadget_board_listsGets the lists on a board, by board id.
Fetch Board CardsReadget_board_cardsGets the cards on a board. The digest template asks for open cards only.
Create New CardWritecreate_cardCreates a card in a list, with a name and a description.
Add ChecklistWritecreate_checklistAdds a named checklist to a card. The template calls it Acceptance Criteria.
Add Checklist ItemsWritecreate_check_itemAdds an item to a checklist.
Add CommentWritecreate_commentAdds a comment to a card.

Two reads and four writes, all of them additive. Moving a card between lists, assigning members, archiving and deleting are not in the shipped data, so a person promotes or closes cards in Trello.

Neither template starts from a Trello event. A card being created or moved is not in the data: <Trello trigger events - founder to fill>.

Boards are shared plans, and a card is an assignment

A Trello board is a shared, visible plan. Lists are stages, cards are commitments, and the people on a card have been told it is theirs. Creating a card is therefore assigning attention. A bot that drops twenty cards into the To Do list changes what a team believes it has to do.

The shipped automation finds its target list by name. It looks for a list whose name contains to do and one containing done, and falls back to the first and last lists if it cannot find them. That fallback is the part to change in real use, because a wrong list is a quiet failure. Name the list explicitly, or stop and ask when it is not found.

How to connect Trello

The shipped templates point at a stored credential by id and read the board id from the environment of the test setup. The credential type is not in the data: <Trello credential type - founder to fill>.

  1. 01

    Create the credential

    Add a Trello credential in Studio, using an account that is a member of only the boards the workflow serves.

  2. 02

    Pass the board in explicitly

    Set the board id once at the top of the workflow. Do not search for a board by name.

  3. 03

    Name the target list

    Replace the shipped fallback with a named list, and make the workflow stop if it cannot find it.

  4. 04

    Gate the card creation

    Put a human-input step in front of the create-card node, addressed to the board’s owner.

Three governed Trello workflows to build in Studio

Each has a label. A starting point builds on a shipped template, which is an integration test with no approval step. A design is intent only.

Onboarding card with a checklist

Starting point

Builds on the shipped template “trello board automation” (9 nodes), which you can find in the template library.

Create a card for a new starter with the checklist the people team agreed, after the hiring manager approves.

  1. Get the board’s lists and find the target list by name.
  2. A human-input step shows the hiring manager the card that is about to be created.
  3. On approval, the create-card action adds the card, then the checklist and its items.
  4. A comment records which request the card came from.

Where the approval sits. The shipped template creates its card, checklist and comment with no gate. The approval and the explicit list are the changes.

Open-cards digest for the weekly meeting

Starting point

Builds on the shipped template “multi integration daily digest” (10 nodes), which you can find in the template library.

Give a team a list of open cards before the weekly meeting, ready to read.

  1. The get-cards action reads open cards from the board.
  2. A code node groups them by list.
  3. An LLM node writes one line per list.
  4. The digest goes to the meeting owner as output.

Where the approval sits. A read-only digest has nothing to approve. The shipped version also reads GitHub and a calendar, so remove what you do not need.

Requests held in a Proposed list

Designed

Let an agent propose cards without anyone being assigned until a person promotes them.

  1. An agent turns incoming requests into card drafts.
  2. A human-input step lets the board owner approve a batch.
  3. On approval, the create-card action adds each card to a list named Proposed.
  4. A person promotes cards from Proposed in Trello, which the shipped data cannot do.

Where the approval sits. Two gates keep a card from reaching a team’s plan by accident: the owner’s approval of the batch, and a human promotion out of Proposed.

Shipped template
A governed template with its approval step already in it ships in the platform.
Starting point
A shipped template runs the same actions. It is an integration test with no approval step, so you add the gate.
Designed
Design intent. It uses the actions listed above plus generic nodes, and nothing has been built as a template.

Approvals and records for Trello

A Trello write changes what a team sees on its own board, so the controls follow who owns the board.

Needs a person’s approval

  • Creating cards on a board that more than your own team uses.
  • Creating more than a handful of cards from one run.
  • Any run that falls back to a default list because the named list was not found.

Can run without one

  • Reading lists and open cards for a digest.
  • Adding a comment to a card the same run created and the owner approved.

What is recorded

  • Each read and each create in the run, in order.
  • The board owner’s decision on a batch, and when they made it.
  • A policy decision on the card text, such as a deny when it contained personal data.

The human-input step, the policy engine and the run ledger are built in the product, and the engine acts only on runs that have a policy attached. Trello’s own permissions decide who can see the board. Swfte decides whether a workflow adds to it, and keeps the record.

A policy step in a design below describes the intent. The policy engine acts only on runs that have a policy attached, and a self-serve way to author policies is not something we describe as built.

Swfte’s own security position and any attestations are on the trust page. How approvals, policy and records fit together is on the governed agents page.

Comparing tools for Trello work

These comparison pages are dated and sourced. Each says who should pick the other tool.

  • Zapier alternatives

    The Zapier comparison covers when a single trigger and a card creation are all you need.

  • Activepieces alternatives

    The Activepieces comparison covers an open-source builder for the same kind of board automation.

  • Best automation platforms

    How automation platforms compare on governance, approvals and records, with the method shown.

Trello questions

Is there a Trello MCP server in Swfte?

No. The MCP tool list has eight entries and Trello is not one of them. You reach Trello through the Studio workflow node.

Can a workflow move or archive a Trello card?

Not with the actions in the shipped data, which read lists and cards and create cards, checklists, checklist items and comments. Design workflows that add cards and leave moving them to a person.

What happens if the target list does not exist?

The shipped template falls back to the first list it finds, which is the behaviour to remove. In a real workflow, name the list and stop the run, or send the case to a person, when the list is missing.

Is there a Trello template to start from?

Two templates use the node: trello board automation, which creates a card with a checklist and a comment, and the multi integration daily digest, which reads open cards. Both are integration tests with no approval step.

Who should approve cards created by an agent?

The owner of the board, because the cards land in their team’s plan. Approve a batch at a time so the owner sees everything that is about to be added.

Keep reading

Build a governed Trello workflow

Begin with a read-only workflow on a test account, then add one write with an approval in front of it.

Build with AITalk to our team

Build this in Studio

Describe what you need in plain language. Studio builds the agents and workflows, and you keep every version.

Start building freeLearn more