Product updates

Check out what’s new in the past few weeks! 👀 API Access the AI bot in the API playground Hotfix for ComplexityException errors Apps New secrets manager for monday code Developer center UI improvements New monetization requirements for marketplace approval Removed directives on June 1st, 2024 New monday tunnel domains New ability to reorder integration recipes

You can now access our API/apps framework AI bot in the API playground using the Ask AI button in the top right corner!

We recently held a one-day hackathon focused on quick updates based on known issues and feedback from our community. Check out what’s new below! Personalized welcome headers with your profile name 👋 Search by app name to make locating your app a breeze (and it even auto-focuses on the search bar when you open the app page!) 🔍 Open links in new tabs or windows (with a right-click) 🪟 Create a new app version or promote a draft from any page 💥 Search by feature name instead of scrolling through a long list (and it even auto-focuses on the search bar when you open the feature page!) 🔍 More descriptive app feature names for new app features (e.g., Board View feature or Account Settings View feature) ✍️ The left-pane menu won’t jump when you switch between tabs ⚓ Smaller header on the App versions tab so you have more real estate to manage versioning 📂

Dear partners, We want to inform you that starting July 1st 2024 (the effective date), new apps will not be able to be published with a monetization system external to monday.com. When monetizing your apps, you will be able to use the monday native monetization. Our monetization handles the entire payment and billing process, it takes the hassle out of billing users and processing payments, giving you more time to focus on building and improving your app. We are constantly upgrading and improving our native capabilities and are committed to continue focusing on it. This change does not affect existing apps, and it will be applicable to new apps submitted after the effective date. Read more about our monetization here: Monetization

On June 1st, 2024, we will remove the allow-top-navigation and allow-top-navigation-by-user-activation directives from iframes to increase app security. See previous announcement here. These directives enable apps to redirect customers from their monday account to another website, which poses a security risk for many customers. Here are good and bad examples of what’s currently allowed: // Open link in a new tab - GOOD window.open("https://www.mozilla.org/", "mozillaTab"); // Open link in a new window - GOOD window.open("https://www.mozilla.org/",'name','height=300,width=650,screenX=400,screenY=350') // Redirect the user outside of monday - BAD window.top.location.href = "https://www.mozilla.org/"; After deprecating these directives, any links utilizing this functionality won’t work but won’t impact app functionality. This update will only disable window.top.location.href (see example below): window.top.location.href = "https://www.mozilla.org/"; If you need to direct customers to an external link from the app, you can still do so by opening it in a new tab using the SDK or the window.open method. window.open("https://www.mozilla.org/", "mozillaTab"); Got questions? Drop them in the thread below 👇

Here’s what’s new in the past few weeks: API Breaking change rollback: data object in error codes Apps New create item dialog SDK method Changes to seat-based app calculations Removing directives on June 1st New ability to create secrets for monday code through the UI

It’s been a while since our last round-up of changes to the API, apps framework, and marketplace…but we’re back with many new and improved features! Check them out below 🤠 API 2024-07 Bug fix: Changes to ComplexityException error reverted 2024-04 New app_subscription_operations query and mutation New ability to create a doc column Bug fix: Date column filtering with multiple exact dates Bug fix: Changes to ComplexityException error reverted 2024-01 Bug fix: Changes to ComplexityException error reverted Apps New SDK method to open app rating popup Important updates to workspace templates board permissions New self-service requests to update your app listing page Updated sales and app analytics widgets New monday code alerts

On June 1st, 2024, we will remove the allow-top-navigation and allow-top-navigation-by-user-activation directives from iframes to increase app security. These directives enable apps to redirect customers from their monday account to another website, which poses a security risk for many customers. Here are good and bad examples of what’s currently allowed: // Open link in a new tab - GOOD window.open("https://www.mozilla.org/", "mozillaTab"); // Open link in a new window - GOOD window.open("https://www.mozilla.org/",'name','height=300,width=650,screenX=400,screenY=350') // Redirect the user outside of monday - BAD window.top.location.href = "https://www.mozilla.org/"; After deprecating these directives, any links utilizing this functionality won’t work but won’t impact app functionality. This update will only disable window.top.location.href (see example below): window.top.location.href = "https://www.mozilla.org/"; If you need to direct customers to an external link from the app, you can still do so by opening it in a new tab using the SDK or the window.open method. window.open("https://www.mozilla.org/", "mozillaTab"); Got questions? Drop them in the thread below 👇

I have an exciting update about the feature request backlog in our community. We have managed to put a TON of requests onto our product roadmap! 🔮 This is part of a larger campaign to make our product roadmap more transparent for YOU, our developer community. What’s on the roadmap: We’re planning to release the following features by the end of the year 👀 Things can shift, but this is what we’re planning so far. Querying Formula column values Add item_count to groups Accessing archived Items in a board via monday API Add new pulses at the top of board/group SEO improvements for public marketplace (loading time, proper HTML links, etc) Change pricing for apps using a web UI (not form) ItemCard - delete item & create item feature Trigger: “When an item is deleted” Enable some blocks with dependencies to be published Custom conditions for automations Workflow block ID in app payload In our long-term roadmap: These features are in our vision for the platform, but we can’t share a specific ETA yet. Api feature request: expose user.time_format & date_format Rename of column IDs Bulk update of Items through API? Expose board order value on items/subitems Create Multiple items at once Changing/Setting Group ID values Monday storage as a database Affiliate / Referral commission in the monetization SDK Subitems columns in custom integration Lifecycle event when user starts the app demo Applying subscription discounts via the API? Allow app developers to test monetization flow in their app App billing - allow devs to prices for existing users (not just new ones) App bundles - to increase sales Are there plans to add graphQL support for vendors to query things like subscriptions? Features we’re still researching These are interesting but require deeper research. We want to invest in them, we are just not sure what the solution will look like. Show warning when app is restricted to specific workspaces & better error messages Custom development profiles with stages/parameters What’s next? Building all of this, of course! In a few months, we’ll repeat the process – update statuses and prioritize the new or newly-popular items. Read this topic for more about our feature request discovery and tagging process. Disclaimer: While these are estimations and the best information so far, our plans can change given shifting business priorities or team capacity!

Effective immediately, we have decided to deprecate the previous monday.com form used to submit marketplace requests, which was found here: https://wkf.ms/44uiZaW . We understand that this change might initially seem inconvenient, but our aim is to streamline the process and make it more efficient for everyone involved. We have designed new avenues to accommodate your requests and we believe these changes will benefit you in the long term. We have aligned our internal processes to give more thorough and timely responses. Please see the list below to determine the best place to submit your request based on the nature of your need: For updating your app’s listing page, this will now be done within the platform. Please use this link to learn more: Update your app listing page For submitting pricing changes, use this form: Plans & Pricing - monday.com Marketplace monetization If you have a feature request, please have a look at our community here: Feature Requests - API and Apps Framework - monday Community Forum For all things related to Marketing, we have a fantastic resource just for you: [https://support.monday.com/hc/en-us/articles/12793031371282-Promoting-an-app-on-monday-com] Finally, for all other requests – including matters pertaining to monetization, billing, and technical issues – kindly use the following form: https://support.monday.com/hc/en-us/requests/new?ticket_form_id=13855862562962. If you are unsure where to submit, you can also utilize this form. As a note, this form will open a ticket with our support team & thoroughly completing all fields on the form will expedite our team’s investigation. We thank you for your understanding, patience, and cooperation as we transition to these new procedures and hope you’ll find them better suited to your needs. As always, we are committed to offering you the best support and we appreciate your partnership.

Board permissions will now transfer to boards created from the templates in workspace template apps. Before this update, board permissions defined by a workspace owner would not transfer to boards created from the template. This change will be automatically applied to all new app usage. It will not impact those who create the template or the app because they already have full permissions as owners. However, it can impact non-owners who may have restricted permissions if they were defined in the template. In these instances, the board owner can update the permissions for those who need access.

We’ve been working with pricing experts Untapped to create a set of recommendations for you to price your app. The result is an extensive document that answers 6 main questions, based on the most common topics our community members have asked about: Do I used seat-based or feature based plans? How many plans should I offer? What do I include in each plan? How do I price each plan? Should I offer a free plan or a free trial? How should i use discounts? Download the pricing report now!

We’ve been busy over the last few weeks making updates and improvements to the API and apps. Check out what’s changed below! API As a reminder, 2024-04 will become the default version on April 1st, 2024 New Javascript SDK and CLI 📣 Breaking changes to app installs queries in 2024-04 Mutations with the column_values argument now accept both strings and integers Apps New parameter for open plan selection SDK method Updates to marketplace user support

Let’s discuss support in the Marketplace! We understand that you may already know about the recent changes we’ve made to enhance support for app developers and API users like yourself. We phased out the old appsupport@monday.com email and introduced a more streamlined form. [See more here: New Support Form]However, there’s more to these changes! We’re excited to announce a small adjustment in how your app customers receive support. Previously, we would simply direct them to reach out to the support email listed on the app page. Now, we’re taking a more active role in the conversation to facilitate support from the monday.com side. If a customer contacts our main support channel, we will CC your email and collaborate with you directly to find a solution. If the issue is on the monday.com side or if the user needs further assistance with a workflow, we’ll be there to assist. This in mind, we’d like to take a moment to remind all our app developers about our support SLAs. According to our Marketplace listings Terms, it is expected that you respond within 2 business days to a request from a User or monday.com, and promptly to urgent issues referred by monday.com. We will be reaching out through the email listed on your app listing page under “contact the developer.” If this email needs updating, please request the change via our form here: https://wkf.ms/44uiZaW. Please don’t hesitate to reach out if you have any questions or concerns. We’re here to support you and make the Marketplace experience even better for everyone.

We’ve been busy over the last few weeks making updates and improvements to the API and apps. Check out what’s changed below! API (2024-04) Breaking changes New kind field enum values Non-breaking changes New is_default_workspace field New create_item mutation arguments New field and argument on app_installs object New display_name field on version and versions objects Apps New demo experience for marketplace apps New security and compliance questionnaire

Many IDs in our platform are returned as integers. These IDs are sequential, which means that they get bigger (and longer) over time. If you are an app developer who stores these IDs in a database, please store them as large integers (Javascript BigInt, SQL BigInt, Java long etc) or character strings, to prevent overflow issues. Even if a specific ID is currently compatible with the integer type, it may eventually become too long to be stored as one. For example, board and item IDs are already too long, and subscription IDs and integration IDs will become too long in the next year or so. Different languages and databases have various ways of handling large integers, so your experience may vary – some applications may throw an overflow error while others will handle it behind the scenes.

Our monday code abilities provides a secure, serverless environment within the monday.com platform. This is where you can host and run apps with monday.com’s security and compliance standards built in, avoiding the heavy lifting of setting up and managing production servers, and creating apps that meet our customers’ unique requirements. Many of you have started using monday code recently, which allows us to learn, fix problems, and add new capabilities. We are GA-releasing monday code with the latest optimization capabilities. With the improvement and with over than 50 apps in production, we feel confident to say: monday code is a performance multiplier solution for you. What’s new? Support for additional programming languages for enhanced flexibility. 🚀 Observation capabilities to boost app performance and address potential issues effectively. 😎 Allow managing subscriptions quota. 🥳 A revamped Software Development Life Cycle (SDLC) process, allowing you to build, deploy, and run full applications with multiple features—all within a single code base. ✅ Improved local development with a direct connection between the local environment and monday.com. 🤩 Deployment directly from your developers’ continuous deployment (CD) environments using Github actions, streamlining the process and saving you time. 🔥 Join us on monday code, explore these exciting enhancements, and let’s create amazing apps together! Don’t forget to check out the video for more details.

We recently released two new query parameters that allow you to retrieve the schema for a specific API version or the SDL version of the schema. API version By default, the schema is in introspection JSON format for the Current API version. You can request the schema for a different version using the optional version=<API-Version> parameter with the version name. For example https://api.monday.com/v2/get_schema?version=2024-04 SDL version You can also retrieve the schema definition language (SDL) version using the optional format=sdl parameter. For example https://api.monday.com/v2/get_schema?format=sdl

The new group_color argument allows you to specify a group’s color when using the create_group mutation. You can find a list of the accepted values here. This argument is available in API versions 2024-04 and later. GraphQL mutation { create_group (board_id: 1234567890, group_name: "new group", group_color: "#ff642e", relative_to: "test_group", position_relative_method: before_at) { id } } JavaScript let query = "mutation { create_group (board_id: 1234567890, group_name: \\"new group\\", group_color: \\"ff642e\\", relative_to: \\"test group\\", position_relative_method: before_at) { id } }"; fetch ("https://api.monday.com/v2", { method: 'post', headers: { 'Content-Type' : 'application/json', 'Authorization' : 'YOUR_API_KEY_HERE', 'API-Version' : '2024-04' }, body: JSON.stringify({ query : query }) }) .then(res => res.json()) .then(res => console.log(JSON.stringify(res, null, 2)));

You can now return an item or board’s URL by querying the url field. This field is available on both boards and items objects in API versions 2024-04 and later. query { boards (ids: 1234567890) { name url } } query { items (ids: [1234567890, 9876543210, 2345678901]) { name url } }

You can now query the voters field on the VoteValue implementation to return a list of users who voted. This field is available in API versions 2024-04 and later. query { items (ids:[1234567890, 9876543210]) { column_values { ... on VoteValue { vote_count voter_ids voters } } } }

I’m hosting a live Q&A about the API migration next Thursday at 12pm EST. It’s aimed at anyone who’s still migrating to version 2023-10 or has questions they want to discuss in realtime. Register here!

Hey, community! We’re committed to improving our attention to you and ensuring your needs are heard and reflected on our roadmap. While we have been attentive, we acknowledge that our current process lacks organization and smoothness. So, let us introduce you to our updated Feature Request (FR) process: Where can you submit a feature request for the monday.com team? You can do so in the community section through this link. There, you’ll find a dedicated space to write and explain your request. You can also vote for other feature requests suggested by fellow developers. What should you include in a feature request? To help us and other users understand your request, please structure it as follows: Summary: Provide a concise overview of your request. The problem: Clearly explain the issue or challenge you’re facing. The use case: Describe how this feature will address the problem at hand. The suggestion: Present your proposed solution or feature idea. Additional details: Feel free to include any supplementary information. What will we do with your FRs? Every quarter, we review the most voted feature requests in our teams. As a result of this review process, we will provide updated status notifications to the community. These tags will indicate if a request is being added to our roadmap and the expected release timeline. What do we need from you for this process to work? First and foremost, 📢 please vote! 📢Your votes help us gauge the importance and priority of different requests. Lastly, please make sure to follow the suggested structure and provide as much information as possible in your feature requests. This ensures clarity and helps us better understand your needs. What else should you know? While we aspire to review every feature request, please note that it will not be possible every quarter due to volume. This is why we encourage the use of the voting system. What’s in it for you? By actively participating in this process, you can make a tangible difference and influence our roadmap. We want your feedback to have an even bigger impact. Here are some recent requests from the community that made it onto our roadmap: 🚀 Hosting your app on monday code ✅ Webhook authentication 🔥 Improved monday tunnel 🤩 API methods for getting app installation info 😎 Quicker pagination with next_items_page 🥳 Sorting items by creation or update date Thank you for being an integral part of our community. We’re excited to hear your ideas and work towards enhancing our product together! ❤️

On Saturday, February 3rd, at 1:00 AM EST (US server), we will conduct planned maintenance, and the monday.com platform will be in Read Only mode. All mutations will be blocked during this period. Any API call containing a mutation will result in the following error: “GraphQL Action Mutations::ArchivePulse has been blocked”. The total maintenance window is estimated to last for 30 minutes. Please plan accordingly!

The new DeleteLastGroupException error occurs when you attempt to delete or archive the only group on a board. To resolve the error, ensure that the board has more than one group. This error will appear in API versions 2024-01 and later.