For the complete documentation index, see llms.txt. This page is also available as Markdown.

3. Send HTTP Requests

Create and update Trello cards from a workflow by mapping API inputs into a Send HTTP Request node.

Challenge overview

Build a workflow that creates Trello cards from structured user input.

Then extend it to update existing cards by matching the user’s request to the closest card name.

Scenario

Our project team is creating Trello cards manually for every new task that comes in — typing titles, descriptions, and due dates one by one.

We need an internal tool where a team member can describe a task, and the system automatically creates a properly structured Trello card in the to-do list on our board.

Setup

  1. Create a free Trello account at trello.com.

  2. Create a board with at least three lists.

    • Example: To Do, In Progress, Done

  3. Get your API key.

  4. Generate a token.

Interface

Build a Form interface with these inputs:

  • Task

  • Description

  • List

The List input should be a dropdown that contains the list names from your board.

Sample inputs

  • Task: Design new onboarding screens

    • Description: Create mockups for the 3-step onboarding flow discussed in Monday's sync

    • List: To Do

  • Task: Write Q2 marketing brief

    • Description: Cover campaign goals, target audience, and budget breakdown for the Q2 push

    • List: Done

What to build

Your workflow should:

  1. Accept the three form inputs.

  2. Map the selected list to the correct Trello list ID.

  3. Use Send HTTP Request to call Trello’s Create a New Card endpoint.

  4. Create the card in the right list.

Hint

  • You may need a second Trello endpoint to retrieve list IDs.

  • You can get the board ID from the board URL.

  • The mapping from user-facing list name to list ID must stay dynamic.

Key considerations

  • Use the Send HTTP Request node for the API call.

  • Read the Trello docs closely.

  • Focus on the cURL example and query parameters.

  • Translate each API field into the correct request section:

    • URL

    • HTTP method

    • headers

    • query parameters

    • request body

Extension

Add support for updating the description of an existing card.

When updating, the user provides:

  • The card name

  • The list the card belongs to

  • The new description

The workflow should:

  1. Find the closest matching card name in the selected list.

  2. Update the matching card description.

  3. Support approximate matches.

    • Example: work on workflow should match Build workflow

Then recreate the same workflow using Code Execution or the Terminal tool instead of the earlier approach.

Helpful docs

Last updated

Was this helpful?