Howdy 👋

One of the initiatives in DesignOps at my company is to improve quality of design. As part of this work, I’m trying to make it as easy as possible for designers to record design debt in a systematic way and have a neat way to the prioritise and clear that debt.

I’ve built a proof-of-concept that allows anyone to add a #designdebt comment in Figma and have it create a corresponding debt record in our Design Team Airtable. From here, they can enrich the debt with additional information, categorise it and assign it.

The issue I have is that this is made using Figma webhooks (via Julian Pfeil’s Webhook Configurator plugin) and a webhook seems attached to a single team - Does anyone have any suggestions for a way to elegantly handle this across all existing and future teams?

We’re a large org with more than 60 teams and I don’t want a webhook (and corresponding Airtable automation) per team.

Some more nuanced technical flow for the setup right now:

1. User adds “#designdebt” comment in Figma or FigJam


2. This fires the FILE_COMMENT event


3. An Airtable automation fires from a single webhook address


4. The automation drops irrelevant events (any PING events and any FILE_COMMENT events that does not contain “#designdebt”)


5. If the event contained “#designdebt” it creates an Airtable record, setting the creator of the record as the comment author (via email lookup), including a link to the comment, and then fires the reporter a Slack message with a link to the Airtable record for them to add any extra info