I’ve built a custom workflow trigger (“When Time Tracking stops…”) and action. My backend needs to activate the trigger’s specific webhookUrl (saved during subscribe) when a relevant Time Tracking column stops.
To detect this change, I understand I need an app-level webhook listening for change_column_value. How and where exactly in the Developer Center do I configure this app-level webhook subscription to send events to my backend endpoint (e.g., /monday/events)?
Or maybe I’m wrong and it actually happens in a different way?
In conclusion - how to correctly call a custom trigger from Monday and not from another application?
you can create a custom trigger (with a subscribe and unsubscribe endpoint) and create a webhook through the API in the subscribe event. Don’t forget to delete the webhook in the unsubscribe event. You webhook endpoint can analyze the payload of the webhook and (in the app) you decide to post to the subscription URL, which will trigger monday to post to your action endpoint from your custom action.
Thanks for outlining those two potential approaches! I have a follow-up concern about both:
Regarding Option 1 (Using built-in “column changes” trigger): My main issue here is how to enforce that the user only selects a Time Tracking column in the recipe configuration? The standard trigger allows selecting any column type, which would break my custom action’s logic if the user chooses incorrectly. Is there a way within the recipe sentence or action input field definition to restrict the column picker to only show time_tracking columns when using this built-in trigger?
Regarding Option 2 (Creating a webhook via API during subscribe): Based on my experience, webhooks created via the create_webhook API mutation do seem to appear in the user’s board automation management interface (often looking like “When [event] happens, send a webhook”). While functionally this works for detection, it adds clutter to the user’s automation list , which I’d prefer to avoid for a cleaner user experience. My goal is for the user to only see the single, primary automation recipe they configured (“When Time Tracking stops…”).
Is there perhaps a third way, or a variation of Option 2, that allows my backend to listen for the change_specific_column_value (or similar) event without creating an entry visible in the user’s automation center? Or is the backend validation (checking column type in the action’s Run URL) the only practical way to handle the limitation of Option 1?
Appreciate any further thoughts on achieving both specific column type detection and a clean user interface.
Thank you!
But what trigger my app?
How my app know that the the user changed the time tacking column?
Should I create a webhook via the API during the subscription process, considering that this action adds an automation to the Automation Center and causes load on the user interface (UI)?
Im asking, if my CRM system (green) is Monday.
how do i set it? the Registers the webhook, set webhook when lead created?
Do i have to add a webhook to the board via API?
