bug(ish): creating a card widget using Zapier asks for a hex color, but requires # and that is not documented

  • 5 February 2023
  • 1 reply

Badge +1

Hi there. Was dumbfounded for a while when setting up an airtable → miro card widget Zap in zapier. Setting card color is possible, but requires the hex color code to have a preceding #. That’s fine, but it’s not documented in an easily-accessible way outside of the API docs and not all apps require it. The Miro docs are a bit obtuse for non-developer pro users, and the error returned via zapier was just ‘method argument.’ Searching for that in the API docs didn’t lead me anywhere. Digging around and reading carefully, noticed the need for #, but I recommend making more verbose error codes or being clear about data validation requirements somehow. 400-Bad Request did not make it clear. 

Thanks for considering.



1 reply

Userlevel 2
Badge +1

Hello MJ,


Thanks for the feedback and sorry to see that you had a hard time out there.


As for the documentation about the color codes, you can take a look here: 


Please let me know if this is not clear and what part is confusing so that we can enhance the documentation accordingly.


As for the error codes, I will pass on your feedback to the team. 


Thanks again and have a good one.