I’m developing my first monday app with a custom trigger feature. I’ve created an Automation Block of type “Trigger” and configured:
- Subscribe/Unsubscribe URLs: My backend endpoints (live server) that receive subscription data from monday when the trigger is added/removed in a workflow. They respond with 200 OK and the expected payload.
- Output fields: Defined in the app settings.
- Scopes: boards:read, boards:write.
- App status: Promoted to “Live” and installed on my account (via “Install for my account” in the “Distribute” section).
The trigger worked perfectly when I tested locally with ngrok – it appeared in the workflow builder and I could select it. But after moving the backend to my production server and updating the URLs in the app, the trigger no longer shows up in the list of available triggers when I try to create a new automation in a board.
What could be causing this? I’ve checked:
- The endpoints are publicly accessible and respond with 200 to monday’s subscription requests (I see the calls in my logs).
- The app is installed and shows as “Live” in the Developer Center.
- I’ve tried reinstalling the app, waiting several hours, and using different boards.
There are a few things I’m unsure about.
When configuring the feature block, the “Save Changes” button appears muted/grayed out. I’m not sure if something is missing. For the custom trigger, I have configured: block name, input fields, output fields, API configuration (my /subscribe and /unsubscribe endpoints on my server), and enabled usage in the workflow builder. However, the button doesn’t seem ready to be clicked.
Also, in the features table, even though I configured the feature with a name before promoting it to Live, it doesn’t appear with the name I assigned. Instead, it still shows as “Automation Block Feature” — the default name that appears right after creating the feature.
In another app I had created to test how triggers work, I built an API and made it accessible using ngrok, with fewer output fields. In that test, I was able to select the trigger in the workflow builder and successfully created some items using the data my trigger provided. However, after proceeding to build the app with my real backend and the output fields I actually need, it doesn’t seem to work after promoting to Live and installing.
The place where I expect to use my trigger is here (correct me if this isn’t where it’s used):
Is there an additional step to make a custom trigger appear in the workflow builder? Do I need to publish the app to the marketplace? Are there any specific requirements for the subscribe/unsubscribe responses that might be missing? Any help would be appreciated.