Product updates

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.

In the next few weeks, we will stop supporting major and minor app versioning and only offer one app version. This new version functions like a minor version and will automatically be pushed to users, but it allows you to do everything you previously could in major versions (e.g., changing scopes, deleting features, etc.). The main changes include: App feature deprecation and un-deprecation User approval for updated permissions App view banners to communicate with users This new versioning mechanism will be available for new apps starting January 31st, 2024. Existing apps will continue versioning with major and minor versions until February 11th, 2024, and at that point, they will be automatically migrated to the new versioning mechanism. Existing app developers are not required to create a new version as part of this migration. All previous app version numbering will remain the same, but the next version you create will utilize sequential numbering. You can read more about versioning here.

You may have noticed that our API documentation looks a little different… 👀 We’ve been updating the docs to create a more straightforward and user-friendly experience - starting with the site navigation. The API documentation has been split into two sections as part of these updates: API reference and guides. The API reference section houses docs about every object, argument, and field you can query or mutate using the API. You can now search inside the API reference docs themselves to return smaller batches of more relevant results. The Guides section contains all the other important information to know when using the API like versioning, introduction to GraphQL, and error codes. You can easily flip between the two sections (+ the changelog) using the dropdown pictured below ⚡

📢We are thrilled to unveil a new feature that will take your marketplace apps to the next level. Say hello to the Demo Experience! 🚀 What is the Demo Experience? The Demo Experience is a powerful tool that enables you to create immersive demo environments for your marketplace apps. This game-changing capability allows potential users to get a hands-on experience of the core functionalities of your app without the hassle of installation, admin approval, or granting access to account data. What value Deme experience can give you 🔎 A Seamless App Exploration: With the Demo Experience, users can try out your app safely and securely, ensuring they find the right fit right away. 🕐 Reduced Time to Value: The Demo Experience greatly accelerates the decision-making process, allowing users to experience firsthand the benefits of your app and increasing the chances of them becoming long-term users. 🫱 Enhanced Decision Making: By providing users with a real-life experience of your app, they can make more informed decisions about its relevance to their specific needs. ✅ Streamlined Approval Process: Allows users to present a solid case to their administrators, making the approval and installation process smoother than ever before. We believe that this feature will revolutionize the way users interact with marketplace apps, providing an immersive experience that will drive them to install and use the app. Next steps: Here is our suggested implementation strategy! Watch @dipro video and/or read the documentation to get all the details you need (ETA- 10 minutes). Set a time for you and your team to brainstorm on the most effective way to showcase your app value (in the shortest time to value) using a demo experience. Implement the demo experience technically for your app (ETA differ between apps). Excited to see your demo’s experience 😊

We recently added two new mutations that allow you to add or remove users from a team. These are available in API versions 2024-01 and later! mutation { add_users_to_team (team_id: 7654321, user_ids: [123456, 654321, 012345]) { successful_users { name email } failed_users { name email } } } mutation { remove_users_from_team (team_id: 7654321, user_ids: [123456, 654321, 012345]) { successful_users { name email } failed_users { name email } } }

Hi all, Nimrod from the monday design team here. On Feb 5th, we’re bringing our magic touch to monday products and kicking off a design and experience event. Have you ever encountered confusing texts, unexpected behaviors, broken UI, or screens that need a fresh new look? Share your feedback with us in the comments below (+screenshots) and be part of shaping a better Monday. What are we looking for? While we love getting ideas from you on new features, this time we’re focusing on improving the existing experience. Here are some examples: I expected a button to do X, but it actually does Y. This text color makes it hard to read. This layout doesn’t work well on my small screen. I don’t understand this description. I use this feature a lot and I wish I could access it more easily. Let’s make monday.com a perfect(er) place together!

Hi Community! 🌏 A lot is occurring on right now and it’s probably not that easy to keep track of so here is a short summary. AppDates 😎 Technical updates: We are deprecating API version 2023-07 starting next week, and you can find all the resources you need to implement the change for API version 2023-10 in this post. Value Events: Gain Valuable Data 1 One Easy Change- By incorporating Value Events into your application, you’ll gain future visibility into how users interact with your app. (on the app analytics page). See details here in this post. Events The annual partners summit in London will take place next month and we wish to see you all there. This is the right place in the right time for you to be on, to learn and mingle. Register here, read more about it here. Get to know monday dev. Join us for a monday dev session where you can find all that you need to know about the new monday dev product and the opportunity that comes with it. Register here. Community We have a new support form. Need technical assistance? Open a ticket here. Missed our last community session? Getting to get some more helpful information? Subscribe to our monday app developer youtube channel and see it all.

Starting today, we have a new support form to open a technical ticket with our team! This new form helps us to route your requests and gather useful information about the issues you are experiencing. This will allow us to address your concerns more effectively and provide you with a faster resolution. The appsupport@monday.com email address will no longer be valid. It is set to auto-close and will become a no-reply email address. Moving forward, we encourage all developers to utilize our new support form. App users should reach out via the monday.com support center as usual. This transition is aimed at improving the support process and enhancing your overall developer experience with our API and app marketplace!

We rebuilt our monday tunnel functionality from the ground up! It connects your development environment to the monday apps framework, via a public URL. Generate one with the mapps tunnel:create command. The tunnel has the following NEW features: A static URL - Tunnel URL that stays the same no matter how many times you restart the tunnel Improved reliability - We use ngrok to deliver the core tunneling functionality Compatible with all samples - All our welcome apps now use the new tunnel when running in development mode Note: to use the tunnel, you need to install the apps CLI and initialize it with your API key.

We’re excited to introduce the first release of the new year - workspace app features! This new app feature enables you to build apps that work across the workspace level to compile the workspace’s data in one place! We currently support one workspace app feature called a workspace view. These apps will live in the left-side menu under the Workspace apps dropdown. If the user doesn’t have any workspace apps installed, the dropdown will not appear. When a user opens the app, it will open a separate view in the main window. You can read more about the app feature in our documentation. Happy building!

2024 is just around the corner, and we have some very exciting changes planned for the year… As part of those updates, the Workflow app feature will be renamed to Integration templates, and it will now fall under the Automation Builder label instead of Integration 💥 These changes are effective immediately and apply to both new and existing app features, but don’t worry - this update requires no action from you. Happy new year! 🎊

We recently added a new field, argument, and mutation related to teams in version 2024-01 🚀 Check out each update below! New team_owners_subscribers field on workspaces queries New delete_teams_from_board mutation New kind argument on add_teams_to_board

We’ve recently added seven new commands to make your monday.com app development experience easier: mapps tunnel:create to create a networking tunnel to publicly expose code running on the local machine mapps app-features:build to create a new app feature build mapps app-features:list to list all features for a specific app version mapps app-version:builds to list all builds for a specific app version mapps app:list to list all apps for a specific user mapps storage:search to search keys and values stored on monday for a specific customer account mapps storage: export to export all keys and values stored on monday for a specific customer account You can read more about each command and see examples in our documentation!

You may have noticed something new in the context of all view-based app features (or you can check it out here)… We recently added the themeConfig property to provide insight into the current custom theme applied within the monday.com platform. This information enables you to align your app’s color scheme with that of the platform’s custom theme. Using the ThemeProvider in our Vibe design system, you can maintain visual coherence with the platform and provide an overall better user experience! { "themeConfig": { // defines the color scheme and styling configuration for the app, may be "undefined" if the default theme is used "name": "crm-product-theme", "colors": { "light": { "primary-color": "#007f9b", "primary-hover-color": "#006278", "primary-selected-color": "#bee3e8", "primary-selected-hover-color": "#d4ebef", "brand-colors": { "brand-color": "#007f9b", "brand-hover-color": "#006278", "text-color-on-brand": "#ffffff" } }, "dark": { "primary-color": "#007f9b", "primary-hover-color": "#006278", "primary-selected-color": "#004858", "primary-selected-hover-color": "#003844", "brand-colors": { "brand-color": "#007f9b", "brand-hover-color": "#006278", "text-color-on-brand": "#ffffff" } }, "black": { "primary-color": "#007f9b", "primary-hover-color": "#006278", "primary-selected-color": "#004858", "primary-selected-hover-color": "#003844", "brand-colors": { "brand-color": "#007f9b", "brand-hover-color": "#006278", "text-color-on-brand": "#ffffff" } } } }, "boardId": 4213911112, // unique board ID "boardIds": [4213911112], // list of connected boards "boardViewId": 122234064, // unique board view ID "viewMode": "fullScreen", // or "split" or "widget" "instanceId": 122234064, // unique instance ID for the feature on the board "instanceType": "board_view", // app feature type "workspaceId": 2581779, "theme": "light", // or "dark" or "black" "account": { "id": "1233" }, "user": { "id": "28659824", "isAdmin": false, // or true "isGuest": false, // or true "isViewOnly": false, // or true "countryCode": "IL", "currentLanguage": "en", "timeFormat": "12H", // or "24H" "timeZoneOffset": 2 // timezone offset based on GMT }, "region": "use1", // availability zone ID "app": { "id": 10089476, "clientId": "78643ruyagduyg743tyr812uygd74" }, "appVersion": { "id": 10124592, "name": "context printer", "status": "draft", "type": "major", "versionData": { "major": 1, "minor": 0, "patch": 0, "type": "major" } }, "appFeature": { "type": "AppFeatureBoardView", "name": "context printer - v1.0.0" } }

We recently introduced a hotfix to 2023-10 that returns "" instead of null for most empty column values when querying the text field through column_values V2. This hotfix aligns the 2023-10 behavior to what was returned in 2023-07. Each column does NOT have the same expected behavior. It is essential to check out the column types reference to verify the expected result for each column. The list below summarizes the expected behavior: Most columns will return "" if the column is empty; otherwise, they’ll return the column value as text Mirror, connect boards, and dependency columns will always return null monday doc columns will always return "" Color picker, status, and dropdown columns will return null if the column is empty; otherwise, they’ll return the column value as text Some other columns (e.g., vote) will return a default value if the column is empty

Although 2023 is winding down, our roadmap plans aren’t—and there’s a lot to be excited about in the coming months. We’ve been listening a lot and it’s generated amazing new features and capabilities, like monday Code, expanded sales info, and a conversion-boosting sandbox capability. Check your mail box for our developer newsletter, read and learn, and ask us any questions you might have in the comments.

Webhooks will now return the current pricing version ID in the pricing_version field for free plans. Previously, the field would return null. Check out the sample payload below, and you also can read more about webhooks in our documentation! type: "install", data: { app_id: 1000000000, user_id: 2, user_email: "user1@users.com", user_name: "User 1", user_cluster: "other", account_tier: "free", account_max_users: 10000, account_id: 777777, account_name: "Demo Account", account_slug: "test", version_data: { major: 4, minor: 5, patch: 0, type: "minor" }, timestamp: "2023-06-26T00:00:00.000+00:00", subscription: { plan_id: "5", renewal_date: "2023-07-10T00:00:00+00:00", is_trial: false, billing_period: "monthly", days_left: 14, pricing_version: 5 }, user_country: "IL" }

The new pricing_version field on app_subscription queries returns the subscription’s pricing version. This field is only available on API versions 2024-01 and later. query { app_subscription { pricing_version billing_period renewal_date } }