Via HTTP · Tasks and projects

Trello, in every client’s workflows.

Add a card to a list, with the client’s own Trello account.

Triggers: 0start a workflow
Recipe: 1one web request step

Via HTTP

Add a card to a list, with one step

Each job request becomes a card on the client’s board, in the list they work from. The web request step, filled in: paste it, swap in the client’s ids, add their key.

01
Add the client’s credential
On the client’s page in Thrum: Add credential, type Other (JSON). trello.com/power-ups/admin → New (a Power-Up for the client’s workspace) → API key → Generate a new API key → copy it, then follow the Token link on that page, allow it, and copy the token.
```
{
  "key": "…",
  "token": "…"
}
```

Add a web request step

Name it “Add a Trello card”, set it as here, and pick the credential. Values in double braces are read from the run: here, the lead the form brought in.

LIST_ID: Open a card in the list, add .json to its address, and read idList.

{
  "method": "POST",
  "url": "https://api.trello.com/1/cards",
  "headers": {
    "Authorization": "OAuth oauth_consumer_key=\"{{ credential.key }}\", oauth_token=\"{{ credential.token }}\""
  },
  "body": {
    "idList": "LIST_ID",
    "name": "{{ lead.name }}: {{ lead.summary }}",
    "desc": "{{ lead.phone }} · {{ lead.email }}",
    "pos": "top"
  }
}

What goes out, and what comes back

The key and token go in the Authorization header, so they never appear in an address.

POST https://api.trello.com/1/cards
content-type: application/json
authorization: OAuth oauth_consumer_key="••••••••", oauth_token="••••••••"

{
  "idList": "LIST_ID",
  "name": "Nadia Karim: Quote for a new bathroom, two basins and a shower",
  "desc": "+447700900222 · nadia@example.com",
  "pos": "top"
}

200
{
  "id": "66f7c1d2e3a4b5c6d7e8f901",
  "name": "Nadia Karim: Quote for a new bathroom, two basins and a shower",
  "idList": "LIST_ID",
  "shortUrl": "https://trello.com/c/AbCd1234"
}

Watched like everything else

When Trello stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

Trello and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early access See pricing