Skip to the operations

Productivity

Trello in a decision flow.

4 Trello operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Productivity
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Kanban boards for team work, from Atlassian.

Trello organizes work as cards on lists on a board, and a team moves each card from list to list as the work advances. Atlassian owns it. Its REST API reads boards, cards and the history of each card, and it can move a card or add a comment as the user who approved the token.

What a flow can call

4 operations, each one a step you can place on the canvas.

  1. GET/boards/$data.trello_board_id/cards?token={token}

    List the cards of a board

    Returns the open cards of one board. Set data.trello_board_id to the board ID.

  2. GET/cards/$data.trello_card_id/actions?filter=updateCard:idList&token={token}

    Get the moves of a card

    Returns the actions of one card that moved it to a different list.

  3. PUT/cards/$data.trello_card_id?token={token}

    Move a card to a list

    Moves one card to a different list. Set data.trello_card_id to the card ID and data.trello_list_id to the ID of the destination list.

  4. POST/cards/$data.trello_card_id/actions/comments?token={token}

    Add a comment to a card

    Adds a comment to one card. Set data.trello_card_id to the card ID and data.trello_comment to the comment text.

Where it sits in the decision

Productivity calls have a natural place in a flow.

Operational work begins where the decision ends. Creating an issue, adding its evidence and keeping its state current from the flow gives the team one durable record of what was decided and what must happen next, without a second copy drifting in a handoff.

Whatever Trello returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Trello as a connection authenticating with an API key.
  • 02Trello has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “List the cards of a board” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Trello in a flow.

How do I connect Trello to a decision flow?

Add Trello as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Trello in a decision without ever seeing the secret.

Can I test Trello without touching production?

Trello exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Trello?

4 operations, including “List the cards of a board”, “Get the moves of a card”, “Move a card to a list”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “List the cards of a board”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Trello be called?

Operational work begins where the decision ends. Creating an issue, adding its evidence and keeping its state current from the flow gives the team one durable record of what was decided and what must happen next, without a second copy drifting in a handoff.

Also in Productivity

Ready when you are

Wire Trello into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs