Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Butler Http Request

milynnus Rising Star Jul 31, 2020

Butler is Trello's native and must go to tool for your automation requirements and everyone should use it.

However, there are times when you need to interface with external 3rd party services. This is where Http Request comes in very handy.

You can either request for information, have something done for you or update some files, database ...etc.

This demo is to show you the potential of using Http Request and how this Butler feature can help you solve some of the more challenging automation requirements you might have in using Trello.

What would you use this for? Welcome your comments below.

1 comment

milynnus Rising Star Aug 03, 2020

You learn a lot from reading @Vongsawat  's comments especially on Butler rules, commands etc. So I have worked on 2 limitation identified by Vongsawat :

1) finding a next checklist item ... here's a demo where I put it to use in a checklist application. While you can create lookup using list with card name and description fields, it is not flexible since they have to be pre-defined. This is an alternative based on a http request

2) getting the custom fields in a card lookup. Apparently, and also based on limited testing, it seems to be true that while {found....} can be used on cardname, carddescription, ...etc. it does not work for custom fields. This is an alternative based on a http request


Log in or Sign up to comment

Atlassian Community Events