Webhooks & API: Expose Card short IDs
complete
Adam Coster
The Favro App shows short-hand, unique, index-based identifiers for cards in the top-left of an open card's UI.
This identifier is not available at all via webhooks or the API.
This is a problem for two reasons:
- There appears to be no way to infer a functional URL for a card given its data, making it impossible to create external workflows that result in links to cards. Exposing this ID in card data would make that possible.
- Git-based workflows typically use short identifiers like those in question to allow programmers to use their tool of choice (like Favro) to manage their work. E.g. adding text like "Closed #32" allows GitHub to automatically close ticket #32 when the programmer resolves it. For automating the same thing with Favro, the programmer would need to have a similar short reference visible inside cards (e.g. the identifier in question), and that identifier would need to be easily mappable. This approach is used by programmers for Jira, ClickUp, and other work management systems. There is no way to replicate this feature with Favro without exposing that short ID on the card data, which significantly limits how good the workflows can be for programmers.
Note: In the absence of exposed short IDs, I still need to be able to generate a link to a Card give its API data. I can't find any documentation for that and none of my experiments with cardIds or cardCommonIds have worked. Can someone please share how to make user-visitable URLs from API data?
Dovidas Baranauskas
complete
Adam Coster
RESOLVED. Got some info from someone at Favro:
There is a field called "sequentialId" on API/webhook data. It's not clearly documented, but it's exactly that number that users can see in the Card UI (without the text prefix). You can use that to generate a URL or fetch a specific card, so that takes care of the problem completely!
Adam Coster
I figured out how to create a link that goes to a card using webhook/API data, but it picks the WRONG card.
Widget Link (WORKS!):
Card Link (YIELDS 403):
Card Link (REDIRECTS TO WRONG CARD):
The second link probably shouldn't work, so this may be intended behavior.
However, that final link does everything I'd expect except actually show the correct card. It loads the Favro webapp properly, which then proceeds to convert that URL into the standard https://favro.com/organization/:organizationId/:collectionId?card=:shortId, but the collectionId and shortId have no relationship to the cardId used.
(Cross-posting from a but report: https://favro.canny.io/bugs/p/direct-card-link-using-cardid-redirects-to-the-wrong-collection-and-card)