Feature-level lifecycle event subscriptions let app developers receive webhook notifications when users interact with specific app feature instances (for example, when a board view is duplicated, an object is created, or a column extension is deleted). These subscriptions give developers fine-grained control over how and where events are delivered.

• Feature-level subscriptions: Subscribe only to the feature-level events you care about
• Per-event routing: Route different event types to different webhook endpoints
• Sync/async handling: Choose synchronous or asynchronous handling per event
• Clear identifiers: Manage subscriptions using clear feature identifiers

<tbody>
  <tr><td>AppFeatureBoardColumnExtension:delete</td><td>When a column extension is deleted</td></tr>
  <tr><td>AppFeatureBoardColumnExtension:duplicate</td><td>When a column extension is duplicated</td></tr>
  <tr><td>AppFeatureBoardColumnExtension:export</td><td>When a column extension is exported</td></tr>
  <tr><td>AppFeatureBoardView:delete</td><td>When a board view containing your app feature is deleted</td></tr>
  <tr><td>AppFeatureBoardView:duplicate</td><td>When a board view containing your app feature is duplicated</td></tr>
  <tr><td>AppFeatureBoardView:restore</td><td>When a board view containing your app feature is restored</td></tr>
  <tr><td>AppFeatureColumn:create</td><td>When a custom column is created</td></tr>
  <tr><td>AppFeatureColumn:delete</td><td>When a custom column is deleted</td></tr>
  <tr><td>AppFeatureObject:archive</td><td>When a custom object instance is archived</td></tr>
  <tr><td>AppFeatureObject:create</td><td>When a custom object instance is created</td></tr>
  <tr><td>AppFeatureObject:delete</td><td>When a custom object instance is deleted</td></tr>
  <tr><td>AppFeatureObject:duplicate</td><td>When a custom object instance is duplicated</td></tr>
  <tr><td>AppFeatureObject:import</td><td>When custom objects are imported</td></tr>
  <tr><td>AppFeatureObject:publish</td><td>When a custom object is published</td></tr>
  <tr><td>AppFeatureObject:restore</td><td>When a custom object instance is restored from the archive</td></tr>
  <tr><td>AppFeatureObject:unpublish</td><td>When a custom object is unpublished</td></tr>
  <tr><td>AppFeatureObject:update\_attributes</td><td>When a custom object's attributes are updated</td></tr>
</tbody>

Queries

Get app lifecycle subscriptions

• Only works for app collaborators
• Returns an array containing metadata about an app's feature-level lifecycle event subscriptions
• Can only be queried directly at the root; can't be nested within another query

query {
  get_app_lifecycle_subscriptions(app_id: "123", version_id: "456") {
    id
    entity_id
    event_type
    webhook_url
    is_sync
  }
}

Arguments

Fields

Mutations

• Event types must match the app feature type. For example, you cannot subscribe to AppFeatureObject:create events on a board view app feature.
• 🚧 You can't delete subscriptions for live app versions.

Update app lifecycle subscription

Updates all existing subscriptions' configurations. Returns [LifecycleSubscriptionKind!].

mutation {
  update_app_lifecycle_subscription(
    entity_identifier: "my-app::my-object-feature"
    entity_type: "appFeature"
    input: {
      lifecycle_events: [
        {
          event_type: "AppFeatureObject:create"
          webhook_url: "https://myapp.com/webhooks/lifecycle"
          is_sync: false
        }
        {
          event_type: "AppFeatureObject:delete"
          webhook_url: "https://myapp.com/webhooks/lifecycle"
          is_sync: false
        }
        {
          event_type: "AppFeatureObject:update_attributes"
          webhook_url: "https://myapp.com/webhooks/lifecycle"
          is_sync: true
        }
      ]
    }
  ) {
    id
    event_type
    webhook_url
    is_sync
  }
}

Arguments

Delete app lifecycle subscription

Deletes all app lifecycle subscriptions. Returns a Boolean indicating if the deletion was successful or if no subscriptions exist.

mutation {
  delete_app_lifecycle_subscription(
    entity_identifier: "my-app::my-object-feature"
    entity_type: "appFeature"
  )
}

Arguments

Event flow

Once a feature-level lifecycle subscription is configured via the API, the following flow occurs whenever a subscribed event is triggered.

sequenceDiagram
    participant MondayPlatform as monday platform
    participant MondayAppsService as monday app service
    participant YourApp as Your app

    MondayPlatform->>MondayAppsService: Lifecycle event triggered
    MondayAppsService->>MondayAppsService: Look up subscription
    MondayAppsService->>YourApp: POST to webhook URL

    alt Sync Mode (is_sync: true)
        YourApp-->>MondayAppsService: HTTP 200 (success) or 4XX (failure)
        MondayAppsService->>MondayPlatform: Notify result
        Note right of MondayPlatform: Update UI
    else Async Mode (is_sync: false)
        YourApp-->>MondayAppsService: HTTP 202 (acknowledged)
        Note right of YourApp: Process event...
        YourApp->>MondayAppsService: POST to back_to_url with result
        MondayAppsService->>MondayPlatform: Notify result
        Note right of MondayPlatform: Update UI
    end

Webhook security

All feature-level lifecycle webhook requests are authenticated using a JWT signed with your app’s signing secret.

Your server must verify the JWT in each request to confirm it was sent by monday.com. Receiving a payload without verifying the signature doesn't guarantee that the request is authentic.

Webhook request

When a subscribed feature-level event is triggered, monday.com sends a POST request to the configured webhook URL.

Verifying the webhook request

To ensure the request was sent by monday.com:

1. Retrieve the JWT from the Authorization header.
2. Verify the JWT signature using your app’s signing secret.
3. Reject the request if verification fails.

Read more about the Authorization header here.

Synchronous vs asynchronous mode

Each feature-level lifecycle event can be handled independently, either synchronously or asynchronously.

curl -X POST "{back_to_url}" \
  -H "Content-Type: application/json" \
  -d '{"success": true}'

curl -X POST "{back_to_url}" \
  -H "Content-Type: application/json" \
  -d '{"success": true}'