We've recently made a few updates and improvements to our webhooks to help provide you with a better developer experience. Let's check them out!

  1. New app_webhooks_only argument

This new argument returns just the webhooks created by the app initiating the request when querying the webhooks object through the API.

query {
  webhooks (app_webhooks_only:true, board_id:1234567890) {
    id
    event
    config
  }
}
  1. Added missing authorization headers

Before these updates, we were missing a feature that sent the authorization header for some webhooks. We added the missing feature, so now the authorization header will be included in all webhooks. Make sure to start validating your requests from monday!

Please note that this only applies to apps created in the Developer Center. You will not receive the authorization header if your API call was made with a personal token.

  1. Users can't remove app webhooks in the UI

While webhooks created by apps were always labeled internally on monday as belonging to a specific app, we enabled this labeling in the Active integrations page on the board so users can’t remove your webhooks from the board!

We're excited to announce the release of the first phase of our app analytics 🚀

App analytics was one of the most frequently requested features, and we understand how important that data is to improving your app's performance.

Now, you can access comprehensive and detailed information about your app to provide clear insight that allows you to make data-driven decisions. App analytics gives you data related to your app's installs, reviews, and listings in the marketplace.

You can read more about app analytics and the data you can access in our documentation!

We recently changed the unsubscribe behavior of the custom triggers for the Integration/Workflow app feature.

Previously, the trigger's unsubscribe endpoint was only called when the integration or board was deleted. However, we've updated it to also unsubscribe for three days (subject to change in the future) after the automation was disabled.

This change streamlines resources and unsubscribes stale automations that have been out of use for over three days. Before this change, such automations could remain disabled and subscribed to indefinitely, wasting resources on both ends.

This change will help both the monday app infrastructure and app developers' infrastructure save resources and only trigger truly active automations moving forward.

We recently created built-in logic that monitors and enforces plan limits based on the customer’s monday.com account size. The following changes will be released on August 28th, 2023.

For view apps, we will automatically monitor the number of monday.com seats an account has and compare it to their app subscriptions. If they do not have a large enough plan for your app, we will prompt them to upgrade their plan on both the Installed Apps page and an additional pop-up in the app’s view. Users will not be blocked from the app, and this update only applies to view apps.

If a user has a trial subscription and it expires, they will be blocked from accessing the app and prompted to select one of the available plans. Account admins will also receive notification of the trial expiration and be prompted to choose a plan on the Installed Apps page.

When a user churns from monday.com, their app subscriptions are also canceled. Therefore, the app_subscription_cancelled webhook will now contain a reason field indicating their subscription was canceled upon renewal. Currently, this is the only instance when the reason field appears, though we plan on adding support for additional reasons in the future.

{
  "type":"app_subscription_cancelled",
  "data":{
    "app_id":1000000000,
    "user_id":1,
    "user_email":"[email protected]",
    "user_name": "User 1",
    "user_cluster": 'other',
    "account_tier": 'free',
    "account_name": "Demo Account",
    "account_slug": "test",
    "account_max_users": 10000,
    "account_id":777777,
    "version_data":{
      "major":1,
      "minor":2,
      "patch":0,
      "type":"minor"
    },
    "timestamp":"2022-06-23T00:00:00.000+00:00",
    "subscription":{
      "plan_id":"plan1",
      "renewal_date":"2022-07-19T00:00:00+00:00",
      "is_trial":false,
      "billing_period":"monthly",
      "days_left":26,
      "pricing_version":5
    },
    "reason":"monday_subscription_cancel_on_renewal"
  }
}

Developers can now build AI apps using our AI assistant app features 🙌

We've developed six app features that live in various locations in the platform, use different SDK methods, and work best with certain types of apps. You should decide which feature you'd like to build based on your app's logic:

We've also compiled a quickstart guide that walks you through each step of creating an AI assistant app feature. If you have any other questions, please open a ticket by emailing [email protected]!

Happy building 🔨

We're excited to present three brand new board menu app features:

  • Board group menu
  • Board item menu (coming soon)
  • Board multi-item menu

These new features enable to you create apps that work on a single group, a single item, or on multiple items. You can create these just like any other feature, but make sure you have developer mode turned on!

You're able to start building with the board group menu and board multi-item menu features TODAY, but the board item menu feature will be available soon. As always, we will announce the release both here in the changelog and the community.

We recently released 3 new monday.storage SDK methods that allow you to maintain storage across each application, rather than each instance. With the new methods, the storage is not tied to a specific instance so it does not reset between major versions.

  • monday.storage.getItem(key)
  • monday.storage.setItem(key, value)
  • monday.storage.deleteItem(key)

Please note that with global-level storage, developers are the ones responsible for managing how items are stored on the client side - not monday.

Yesterday we implemented the new sandboxing restrictions, but we have decided to revert the update to give app developers more time to test their apps against the new restrictions.

As of now, the five original directives will remain the same. If your app requires a popup, please check out the new SDK method that allows you to open links in a new tab.

Please test your app in the sandboxed environment to ensure that you don’t have any issues when the new restrictions are implemented. If you do, please reach out to us as soon as possible to identify a possible workaround.

We will update you shortly on any changes to the restrictions, including the new release date, in the changelog and in the community.