Suggest a feature

Right now, when a webhook is activated, the information it sends for tags, CustomFields, etc. is encoded with the internal identifier in Favro. It would be very interesting to see the visible value of the tags or custom fields as well as the name given to the CustomField. Receiving an array of tags that basically reads: ["Nul9aErJoBzezAlx”, “Blw3iztdsFnabKLRM"] is not useful when it comes to integrating with other tools. Especially when there is no way to see those IDs without diving into the API (whose documentation seems to be somewhat outdated) The same goes for CustomFields. The ID is received and the Values array sends only IDs. It would be interesting if, apart from the ID, the Value it has will be sent

I have a team of 24 people and it's a lot of manual work to ping them each as a member or create an automation with everyone. It would be amazing to have a single handle that sends a notification to everyone in that handle - if you're using Slack, think @here or @channel.

The goal is that the required information exists on custom fields or any other dedicated fields. To achieve this, we want to stop the ability to move the card forward from a certain point to the next column unless it has all the required information attached to it.

Webhooks provide card data with the "detailedDescription" field stripped of Markdown. There is no obvious way to change that behavior so that the actual Markdown contents are sent. This means that the "detailedDescription" field is nearly useless in webhooks, since it is guaranteed to be missing information and cannot be used as an accurate reference to take actions based on content or to serve as a starting point for editing and description. In general, if the detailedDescription field matters for a webhook-based workflow, the developer will always have to make an additional request to the API for that card, explicitly setting the desired format type to Markdown, to get the correct contents. Please either allow changing the webhooks to use Markdown, or have them return Markdown by default.

Title says everything

As a user I should be able to get a ping in slack (or whereever) when a Favro Card is created with certain keywords that I can put into the criteria

More automation conditions would be great. It's very limiting to only have a condition based on which kanban status a card has. Some suggestions on conditionals: if card has tag X, if card title contains X, if due date is within X period, if card has members XYZ, if card has field with value X. Comment which conditionals you would like to see!

Timed triggers relating to due dates would be useful to be possible to set with an offset to the due date.

Parent-child relations are lost when getting comments using the Favro API. This means that there is no thread ordering as in Favro, just a list of comments that could only be sorted by their corresponding dates. Inline replies to other comments cannot be traced back to the parent comment. Maintaining the message context is impossible in this way. What is needed is a parentCommentId in the API response for all child comments.