We just released a major improvement to how lifecycle events work in monday apps. This update gives you greater flexibility in deciding which events your app listens to and how you want them delivered.
What’s new
Until now, external developers could subscribe only to app-level lifecycle events (such as install or uninstall), which are configured at the app level and sent to a single webhook URL.
With this release, we’re introducing lifecycle events at the app feature level. These events are triggered by user interactions with the features, giving you fine-grained control over how your app responds to those actions.
You can now subscribe your app only to the feature-level events you care about, route them to different URLs, choose sync or async handling per event, and clearly identify which feature triggered an event using app_slug::feature_slug.
Feature-level lifecycle subscriptions are managed through a new GraphQL API. App-level lifecycle events remain unchanged.
What you can do now
Feature-level lifecycle events are now supported across several app feature types, including Objects, Board Views, Column Extensions, and Columns, allowing you to:
- Set up event subscriptions per app feature
- Assign different webhook URLs for different event types
- Choose sync or async handling per event
- Work with cleaner event identifiers using slugs
- Test or update event subscriptions directly through GraphQL
If there are other feature types or additional events you’d like supported, feel free to reply or submit a feature request.
To get started, make sure the Active Version capability is enabled and that your app and app features have defined slugs. It allows you to select which app version is active in your test environment, ensuring that lifecycle events are triggered from the version you expect.
Why this matters
This upgrade gives you clear visibility into how users interact with your app’s features and lets you respond to those interactions outside the scope of your app’s code.
Instead of relying only on in-app logic, you can now observe feature usage patterns through lifecycle events and react when users create, duplicate, or delete parts of your app. This makes it easier to understand how features are being used and to trigger follow-up actions reliably.
For example, you might route board view duplication events to one service and handle column extension deletions in another, depending on the structure of your app.
We’d love to hear your feedback, ideas, and use cases as we continue to expand these capabilities across the apps framework.
Dive into the documentation and start implementing app feature-level lifecycle webhooks for your app.
