Product updates

We are proud to announce the latest version of the monday style guide — Monday Vibe! It’s a brand-new central repository for all things monday style: React components, style guidelines, and UI notes in one place. Check it out at style.monday.com! Monday vibe features: Full design guidelines to design your apps like monday’s own design guild 26 components for you to use in your apps A sandbox for testing each component Styleguides for fonts, animation, and presentations A logo library We have also updated the Monday UI kit and you can check it out here! Thank you to @orrgottl, @Evgeniy-monday.com, @moshez, @Rotemde, @OmerD, @dorshaked, @danielmittelman, @etay-monday.com, @VladMonday, @ronen, @EranH-monday.com, and the whole team for your contributions. Happy building 🔧

Hey y’all! Wondering about what’s next for the monday apps framework? 🌻 Join our product roadmap webinar next week, where we’ll be showcasing the vision for the apps framework. On the webinar, we’ll cover upcoming features for app developers and the future of the monday apps framework. I really recommend attending if you’re an active developer or want to just learn more about what’s coming next. The webinar is on Nov 3rd, at 11am EST/3pm UTC/5pm CET. If you can’t make it at that time, I’d recommend registering for the webinar anyway – we’ll send you the recording afterwards! Register for the webinar here!

✨✨Hi everyone! We have made some changes to our API complexity rate limits that I wanted to share with you all.  For all apps, we have broken up complexity buckets for reads and writes to our API. Now, each action (read and write respectively) will have 5 million actions a minute each. You can test this out in your apps! Keep in mind: for all queries and mutations made in your Developer’s Playground area (i.e. with your admin token), the complexity limit will stay at 10 million a minute for both reads and writes. This means we only implemented the complexity buckets for apps . Here is an example of what you will see: It’s also important to note that if you query information back regarding the mutation that you made, the complexity budget of your mutation will be affected, not the complexity budget of your query. This means that if you need to query a lot of information back regarding the change that you made, it might be better to include an entirely separate query call after your mutation runs! I’m also happy to announce that we have added the ability for you to query the complexity field for your mutations in addition to your queries! It will work exactly like it does within queries, with a before, after, and reset_in_x_seconds fields. An example:  Try it out and as always, let us know of any and all of your feedback!

✨:sparkles: Hi everyone! We recently released subitem support in dynamic mapping blocks for custom action blocks in your integration recipes. What is dynamic mapping? For those who are not as familiar with our custom integration framework, dynamic mapping gives you the ability to map values coming from other platforms dynamically into your items’ column values. It also allows you to push values from monday.com to external platforms dynamically. Here is what dynamic mapping looks like within an integration recipe, I’m sure this screen will look familiar to many: For more information, feel free to check out our dynamic mapping resource here. What does this mean? Now we will support subitems in custom action blocks that use dynamic mapping. There are a few limitations to keep in mind: This capability has been released for our backend only. This means that subitems are supported for custom dynamic mapping and action blocks. At this time, our built-in action blocks that use dynamic mapping will not support subitems! The trigger must also be within the subitem board in order to trigger this dynamic mapping support. We know that there is still much more that needs to be done for full support of subitems in dynamic mapping. As such, we welcome all of your feedback and thoughts! Happy building~

Hey monday builders, I’m happy to announce that we have officially released our new API and apps framework documentation! What’s new? A new look 💇🏾‍♀️ Reorganized API documentation, with articles organized by object 📚 You can now search!!! (tip: press CTRL-K to quickly open it) 🔍 Updated changelog for new features and links to relevant documentation articles (subscribe to the RSS feeds now!) 🔈 What does this mean for you? A better developer experience. We did this to make it easier for YOU to find technical details easily. We’d love to hear any feedback you have (you can submit comments at the bottom of every article). More accurate documentation We’ve improved internal processes for updating our docs, to give you relevant documentation at the same time as a feature release is announced. Get notified when we have new features for you If you subscribe to our changelogs, you can learn about new features in the monday apps framework immediately. We’ll also continue to notify you if you’ve submitted any feature feedback that has been implemented or solved by a new feature. ~Happy building!~ Dipro 🔮

✨✨Hi everyone, I’m so pleased to announce that we now have a parent_item field for our subitems! As many of you know, before this addition you could query your subitem column values and you could query the subitem column in your parent items to see your subitem IDs, but there was no direct link between the two. In order to match the relevant subitem column values with the correct parent item them, this required a manual searching mechanism created by individual developers to match subitem IDs together. However, with the addition of this new parent_item field, you will be able to query your subitem column values and also be able to see the relevant parent item information for this subitem! Here is an example of how to use this field: query { boards(ids: 'YOUR_SUBITEM_BOARD_ID'){ items{ // all of the subitems on your subitem board id // your subitem IDs parent_item { id // the parent item IDs for each subitem column_values { // the column values of your parent items id value } } } } } Keep in mind that because querying subitems currently follows the same structure as querying parent items (i.e. you need to first find your subitem board ID, then use that subitem board ID to query your subitems normally), if you use the parent_item field on a parent item, the result will be null. Check out our updated API documentation on this method here. We hope this aids in your subitem queries. As always, let us know your thoughts on this new field. Happy building!

Exciting news! We’re happy to announce a highly requested feature is now available. You’ve heard of webhooks on main items, but get ready for webhooks on sub-items! ⚡ Sub-item webhooks include the same events as the main item webhooks: When a sub-item is created; When any sub-item column changes; When a sub-item name changes; When an update is posted in sub-items; When a specific sub-item column changes; When a sub-item Status changes; You can add those recipes from within our Integration Center by using the Webhooks Integration: For recipes that support sub-items, you’ll be able to select a column from the sub-item level: You will receive a payload like this, which is identical to the main item’s payload. It will include the subhttps://community.monday.com/c/developers/dev-guides/70-item board ID, which you can use to distinguish between Main items and Sub-items. Currently, the event type will also be the same as for main items. You can include a query param for your webhook URL when creating webhooks for sub-item events in order to differentiate between updates to main items and subitems. For example, if my base webhook URL is https://alexscoolwebhook.com/, I can add /?subitemCreate=true to the end of the URL to get the following result: https://alexscoolwebhook.com/?subitemCreate=true You will then see the output with this query param included: To create webhooks for sub-item events via the API, use the following sub-item webhook event types: change_subitem_column_value - equivalent of “When any sub-item column changes” create_subitem; create_subitem_update; change_subitem_name; Note: At this time, it is not possible to use the API to create a webhook for Sub-item Status column changes, or for a specific Sub-item column change. We recommend creating a “change_subitem_column_value” webhook, and check the column ID that was updated. In your API call, use the Main Board ID. For example: mutation { create_webhook (board_id: 1544542904, url:"yourURL/?yourQueryParam", event: change_subitem_column_value) { id board_id } } Here’s a cURL example too: ​​curl --location --request POST 'https://api.monday.com/v2' \\ --header 'Authorization: yourApiKey' \\ --header 'Content-Type: application/json' \\ --data-raw '{"query":"mutation { create_webhook (board_id: mainBoardId, url: \\"yourWebhookUrl\\", event: change_subitem_column_value) { id board_id}}"}' I hope this helps building more complex workflows with sub-items 🙂 -Alex

✨✨Hi everyone! Excited to announce that after much anticipation, changes made to the Hours field of a Date column will now be able to initiate our native “When a Column Changes,” “When any column changes,” “Every day if date has passed,” and “When Date is Set” trigger blocks. This feature has been highly requested for a while. Now, whenever a user makes a change to the time configuration within one of their Date columns, this will initiate these trigger blocks to run. Here is an example of such a change: Try it out and as always, give us any and all of your feedback. We want to know what you think!

✨ ✨ Hi everyone! Happy to announce that we have released a new API method items_by_multiple_column_values() that will allow you to retrieve your items using multiple column values from the same column. This has been a highly requested feature, and we’re very excited to share it with you all! This new method utilizes the same arguments and fields as the items_by_column_values() method. For more information, check out our API documentation on this method here. Here is an example query using this new method: query { items_by_multiple_column_values(board_id: 12345, column_id: "status15", column_values: ["Working on it", "In progress", "Incomplete"]){ id } } In this case, I am querying for items with multiple values within a single status column. The response should return a set of item IDs that contain those status values.  Definitely give this new method a try and let us know your thoughts! Next stop: filtering by multiple columns and their column values. Thanks!

Hey amazing community! I have three new features and changes to announce today 🔮 Additional rate limits for board and group duplication We added a new rate limit when you’re calling the duplicate_board and duplicate_group mutations: you can now call these mutations a maximum of 40 times in a minute. If an app exceeds this limit, it will receive a 429 HTTP status code. We’ve added this to our documentation in the Duplicate Board and Duplicate Group sections. Subscribe to our new changelogs! As you may have noticed, we are revamping our developer documentation. As part of this revamp, each documentation center now has a changelog that you can subscribe to! To get notified every time we push a new feature to our API or apps framework, subscribe to them via RSS here: API changelog API RSS feed Apps framework changelog Apps framework RSS feed New “is_verified” field for users You can use this field to check if a user has confirmed their email address. It will return true if a user has verified their email address, and false if not. Documentation here. Here’s an example query that uses this field: query { users { name email id is_verified } } That’s all for now!

✨✨Hi everyone! We recently released some new features, so I wanted to post an announcement introducing them. In total, we have four new features that I’m so excited to share with everyone. 1. We have a new feedback link for your apps! This will allow you to collect direct feedback from your user base via a link you provide. The link can be to a monday.com form, a Zendesk link or anything you’d like. Here is where you can input your feedback link: On the user end, they should see a little “Feedback” button at the top of their view apps: Here it is for Board Views: Here it is for Item Card Views: Here it is for Dashboard Widgets: Please keep in mind this feature is currently only available for view apps, not integrations! 2. We’ve also added the ability to search for apps by developer names (your names)! This should increase the searchability of your apps, so that users can now not only find your app by its name, but also by your name as well. This new feature should also increase the discoverability of the newer apps that you develop. Try it out! 3. There’s a new built-in action block “Create an item with mapping and link” that will allow you to create an item with mapping in a different board (Board B) and link that newly created item to an existing item on the current board (Board A). Here is a video of how the feature would work: 4. Lastly, there’s a new admin permission setting that can determine who is able to generate API tokens. Previously, all admin and member users were able to generate API tokens. With this new permission, admin users are able to choose if “No one”, “Only admins”, or “Anyone” would be able to generate API tokens. Remember, currently only member users are able to generate API tokens (other than admin users), so this “Anyone” would only apply to member and admin users! One thing to note about this new permission is, should a user reach out to asking why they’re suddenly no longer able to utilize their API tokens, I would ask them first if their admin user had changed this permission! There's a lot of new features to digest, so feel free to ask us if you have any questions!

✨✨Hi everyone! Wanted to quickly jump on and announce our two new monday.execute() methods in our SDK. What are these new methods? You now have the ability to open existing files on a board using the monday.execute("openFilesDialog", ...) method. Additionally, you’re able to trigger a local file upload pop-up window in your app using the monday.execute("triggerFilesUpload", ...) method. Example app We created a very simple example app showing you how these two methods will work. Here is what users will see in the UI of this example app: We built this example app by modifying the App.js file in our Quickstart React code. Here is a screenshot of our modified file: You can see that in this example, we inputted the relevant IDs for these two methods manually. You can also, of course, include other SDK methods that will return the relevant IDs, depending on what the user has selected on their boards. Things to keep in mind 1. The monday.execute("triggerFilesUpload", ...) method will not work in the app preview section. This is something our developers are aware of and are working to address. For now, if you add your view app to an item, board, or dashboard, the feature will work as expected. 2. These methods will not work across boards. You must be sure that the files you are looking to open are located on the board that’s currently open. Same thing applies to uploading a file: the file must be uploaded to the board that’s currently open. We are so excited for you to start using these methods! Feel free to navigate to our SDK page here for more information. As always, let us know if you have any questions. Happy building~

✨✨Hi everyone! In case some of you weren’t aware, we wanted to dedicate a post to our new React components! Mainly, we released and updated four main components: the focus state on components, the alert banner, the button group, and the menu button. 1. The focus state on components This added feature allows you to “focus” on different options using your keyboard. For instance:  You can find the link to our style guide for this here. 2. The alert banner This added component gives you another option to present alerts and notifications. For example: You can find the link to our style guide for this here. 3. The button group This new component is great for switching between states or contents within a feature, as you have a collection of buttons to choose from. For example: You can find the link to our style guide for this here. 4. The menu button This new menu component allows you to use buttons for editing and other actions inside of your menus. For example: You can find the link to our style guide for this here. We hope you enjoy these, and happy building!

Hey amazing dev community! Dipro from the monday.com Dev Success team here 🔮 I wanted to post a quick update about some changes that we have made to how posts are managed in the community, and give you a sneak peek into what’s coming next. If you’re a regular, you’ve already seen these changes in action. This post is to document what we’re doing differently now. Changes to our community processes 1. Subscribe to the Announcements and Guides section We’re adding new features (and guides on how to use them) all the time. I recommend you subscribe to the “Announcements and Guides” section so you get notified the moment we add something new. To subscribe, click the bell icon in the top right corner and select “Watching first post”. This setting will notify you when we announce a new feature or documentation! 2. You can now mark posts in the FAQ sections as solved! When another community member answers a thread with an answer to your original question, you can mark that answer as a solution. This lets other users with the same question know how to fix a specific issue. The monday.com team will also mark posts as solved if we decide that the question has been answered. 3. Topics will be closed automatically, but you can create a follow-up To ensure additional questions and follow-ups don’t get lost in a long thread, solved topics will be automatically closed 7 days after the last reply. This does not apply to topics that don’t have a solution yet. When a topic is closed, you cannot add additional replies to it. However, you can open a follow-up topic. 4. Creating follow-up topics Do you have a follow-up question about a topic that was already closed? You can create a follow-up topic by following these steps: Click the link icon at the bottom of the post you want to follow-up on In the dialog box, click “New topic” The “New topic” pane will open with your follow-up topic already inserted. A link to your follow-up will be listed at the bottom of the original post, so that folks looking at the original will know the conversation continues somewhere else. What’s next? In the next month or two, we’ll be releasing two changes that we hope will improve your ability to keep up-to-date with what’s going on in the monday.com community. An overhaul to our developer documentation (stay tuned 😉) A more integrated changelog in our documentation. We want to notify our developer community about new features in our APIs and apps framework without needing to search through unrelated topics. Questions? Have any questions or feedback? We’d love to hear it! Open a follow-up topic so we can continue the discussion 💬

Hey community! Wanted to give you a heads up about two upcoming maintenances that will affect integration apps and custom recipes. Have a follow-up question about this announcement or any others? Click the 🔗 link icon below this post and select “New topic”: Maintenance 1: Sunday May 23rd at 7:15am UTC (15 minutes) A routine maintenance for our custom recipes and monday apps infrastructure. It will last 15 minutes. During this 15-minute period: Custom recipes and monday apps recipes will be delayed Custom recipes and monday apps automations will not be visible in the automations/integrations center It won’t be possible to create new custom / monday apps automations After the maintenance is over, any automations that were supposed to run will execute. Therefore, you should expect any automations in this window to be delayed by 15 minutes. Maintenance 2: Sunday May 30th at 8:00AM UTC (1 hour) A routine maintenance affecting monday apps developers. If you are a monday.com user and don’t build monday apps, this won’t affect you. During the 1-hour maintenance: Developers cannot create new integration recipes in the Feature Editor Developers cannot update or delete integration recipes in the Feature Editor Developers cannot create new integration features in the Feature Editor Developers cannot promote any app drafts with integration features to live. Have any questions? Create a new topic

✨✨Hi everyone! Jumping on here to announce that we recently released a few mutation methods for our Workspaces. These new methods include: add_users_to_workspace() delete_users_from_workspace() add_teams_to_workspace() delete_teams_from_workspace() As their names imply, these methods will allow you to add and remove users and teams from your workspaces. For adding user(s) to a workspace, you are able to not only send an array of user IDs to subscribe to the workspace, but also you are able to specify the kind of user subscription (i.e. whether the user is a regular subscriber to the workspace or an owner of the workspace). Here is an example query for add_users_to_workspace(): mutation { add_users_to_workspace (workspace_id: 20178755, user_ids: [105939, 105940, 105941], kind: subscriber) { id } } Excited to see how you all implement these in your workflows; happy building! –Helen

Our team will be doing scheduled maintenance on May 9th 2021 at 8am UTC (this sunday). The maintenance will last approximately one hour. During this time, developers will not be able to create or edit integration recipes, custom actions, custom triggers or fields in their apps. Existing recipes will also be in read-only mode. The rest of the monday.com platform will work as expected during this time. Update: you will also not be able to create new integration features during this time. Please note that this maintenance only applies to the editors in the developers section. You will still be able to add integration recipes to your boards and edit them, and recipes will continue to trigger during this time. Here’s a screenshot of the section that will be read-only during this time: If you have any questions, feel free to reply to this post!

✨ ✨Hi everyone! I hope all is well. Wanted to jump on here with a quick update. At this time, our appsupport@monday.com email is experiencing some technical issues. However, our team is working to resolve them in just a few days. We will let you know once it’s up and running again. For now, please send all your requests to support@monday.com, and they will be directed to our Developer Success team accordingly. Additionally, our other channels of communication remain open (i.e. posting on the community in the relevant FAQ sections). Thank you all for your patience and understanding!

✨✨Hi everyone! After much anticipation, you are now able to create new Status and Dropdown labels using our API! To do so, use the create_labels_if_missing boolean argument to create any missing labels in your Status and Dropdown columns. This argument will default to false, so if you don’t define it as true the missing labels will not get created and your API calls will fail. Because creating new labels changes a board’s structure, you must have the permissions to change board structure in order to successfully use this argument. Here is an example query using this argument: mutation { create_item (board_id: 12345678, item_name: "New item", column_values: "{\\"status\\" : \\"New Label\\"}", create_labels_if_missing: true) { id } } Currently, this parameter has been added to the following mutations: create_item() change_simple_column_value() change_column_value() change_multiple_column_values() create_subitem() Thanks everyone and happy building! -Helen

Hi everyone! I wanted to announce that our team has decided to rollback the recent API complexity limit change of 10X the per-minute rate every 10 minutes (i.e. 50 million every 10 minutes). As of today, our complexity limits are: 5 million per query 10 million per minute 100 million per 10 minutes We want to thank everyone who submitted their feedback and for communicating your experiences. Our team is here to listen to any and all of them. We will continue to review the way in which we let our users know of future product releases and updates. Thank you for your commitment to monday.com and your continued feedback! Warmly, Helen

✨✨Hi everyone! We’ve gotten a few questions about this, so I wanted to make a post about our IP ranges for devs who need to white-label any monday traffic. The IP addresses that POST addresses are sent from are 82.115.214.0/24, or 82.115.214.0 to 82.115.214.255. Here is our comprehensive article about this in our support portal: https://support.monday.com/hc/en-us/articles/360012300479-What-are-monday-com-public-IP-ranges-. Hope this helps, and let us know if you have any questions!

Hey everyone 🔮 We made some changes to our rate limiting mechanism to make it easier for apps to understand their limits and prevent abuse of our API. TLDR: Each individual query now has a complexity limit of 5M Most apps/users won’t notice a difference (but let us know if you do). How our rate limits work: a recap GraphQL rate limits are based on how much work you makes our servers do, measured in a unit called complexity. Each account and app has a specific complexity allowance that resets every minute. Trial accounts have a budget of 1M complexity every minute, while paid and developer accounts have a budget of 10M. New error messages When you run out of your complexity budget in a given minute, your app will now see a new error message that tells you how much budget you have left and when the limit resets: "message": "Complexity budget exhausted, query cost 1100010 budget remaining 999819 out of 1000000 reset in 19 seconds" Rate limit per query - 5M complexity We are enforcing a new limit of 5M complexity for each individual query. This is still quite a high limit, and you should be able to comfortably write queries that are under this limit using pagination and other best practices (more on that below). What should I do to prepare for this? We believe that very few users will be affected by these changes. However, you can ensure you don’t hit these limits by making your queries as efficient as possible. Follow these simple rules: Don’t ask for more than what you need. Every field in your query contributes to its cost, so only return the data that your app needs to do its job. Paginate, paginate, paginate. As far as possible, paginate through the returned data using the page and limit parameters. If you don’t add a limit or pagination to your query, we’ll assume you’re trying to return 1000 data points (which could blow up your query’s complexity). Reduce deeply nested fields. Each level of nesting in your query increases its complexity by 10x. Therefore, minimize the complexity of your query by ensuring you are returning the majority of your data in the first or second level of nesting. Here’s an example: # Inefficient (cost: 1011020) query { boards (ids:162169280) { groups { id items { id } } } } # Efficient (cost: 1220) query { boards (ids:162169280) { items (limit:100) { id group { id } } } } Have a question, comment, or feedback? Create a new thread from this topic by clicking the link icon 🔗 at the bottom of the post, and hitting “New Topic”:

Hey there, awesome developers! 🎩 Ever wanted to upload a file to our API using variables without using our SDK? You’re in the right place! Today, I wanted to share a code example you can use as a reference point to making File upload calls to monday.com, including variables. This can make it easier to make the actual API call, instead of using hard-coded values in the call itself. This also helps make escaping JSON easier. You can find the code example here with comments: Code example - uploading files with variables using Node In general, you can take the logic of the code example above, and apply it the programming language you are using. You will be sending a request that consists of 4 parts: Query: The actual API query you’d like to make. In this case, either upload a File to the Files column, or to the Updates section. Variables: Your GraphQL variables, where you can store either the Update ID to be used, or the Item ID and the File column ID to be referenced in the mutation. This is useful as it allows you to avoid an additional layer of escaping JSON; Map: This is the part of the request where you include the name of your variables.file request part. For example: var map = {“image”:”variables.file”} This allows us to use variables in the call, and to also include a different name for the file we upload, if necessary. Variables.file (has to match the Map name) This is where you are passing the actual file to be uploaded. To sum up, you will be making a multipart/form-data request here, which is somewhat different from making the usual “application/json” requests for Queries and Mutations. You can find some more examples of multipart/form-data requests and GraphQL below: Some more general info on using multipart/form-data with GraphQL multipart/form-data general info This code example is based on another example that Dipro made earlier, constructing the request using boundaries and creating a stream of the File to upload before making the API call: Uploading a file to monday.com without variables I hope this helps you make more efficient API calls when uploading files to monday.com 🙂 -Alex

✨✨Hi everyone! We wanted to announce that our API now supports date-time formatting in accordance with the ISO8601 standard. This change will mostly affect the created_at and updated_at fields, as well as times stored in the Time Tracking column. The following types have the created_at and updated_at fields (which will be in accordance with ISO8601 as of today): Updates Boards Users Assets Items One thing to keep in mind: the created_at field for board activity_logs will not be updated to the new standard. As always, let us know if you have any questions!

✨✨Hi everyone! We know that some of our users use Windows computers, so we decided it would be a good idea to release an official troubleshooting guide for our Quickstart guides on these machines. Taking the example of our Quickstart Integration recipe, follow each of the steps until you get to step 4. Instead of copy-pasting the given command in your command line prompt: Download the project from our GitHub library following these steps: Download the Quickstart code from this GitHub repo. Navigate to the directory where you downloaded the code Install the dependencies with npm install Run the development environment with npm run start Following these steps, you may run into the following error messages: Kill-port is not recognized: 'kill-port' is not recognized as an internal or external command, operable program or batch file. If you run into this error message, this means that the kill-port command isn’t available on your machine. To correct this, simply install the kill-port ability with the following command and you should be good to go: npm install --save kill-port. Learn more in this community post. Nodemon is not recognized: 'nodemon' is not recognized as an internal or external command, operable program or batch file. If you run into this error message, this means that, like the kill-port command, the nodemon command hasn’t been installed on your machine yet. You can correct this by running the following command, which should install nodemon globally on your machine: npm install -g nodemon. If you see an error message along the lines of: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (88) you may just need to update your node version by first installing NVM, then run nvm install 10.16.3 to install this version of Node. Lastly, run nvm use 10.16.3 before running the npx command. Learn more in this community post. After resolving these errors, run the same command `npm run start` to start your server. Paste the outputted URL in the URL box from step 4 here: I hope this helps! Feel free to let us know if you run into any other errors when installing. -Helen