General

I am trying to use the Speakatoo API, but I am getting an API key error, even though I am confident that I have entered my API key correctly. I am not sure why the API is rejecting my API key, and I am looking for help troubleshooting the issue.

Since the 2023-10 API update. Our API has no longer been returning the values of connected columns as text. The only way we can retrieve the information is by using value, which only returns the item ID in a list and not the text value. Am I doing something wrong or is this part of the update? query { items (ids: 12345) { column_values { value text } } }

I saw that in the newest API version, many IDs are changing from type [Int] to type [ID!]. Is the type ID! alphanumeric or also an integer? I couldn’t find any documentation for what this data type means.

Hello, How does one download files via the SDK? I get a url which I can follow to get a 302, which points me to a url I can download from, but I have to go through all the hassle of generating an application session; I can’t seem to do it directly via the SDK. Am I missing something? Thank you!

Hi, I’m fairly new to Monday and I would like to get pointed in the right direction (or corrected if it isn’t possible): Use case: I have a board where each each item is a buying customer. Among other things the item consists of a start date, end date and monthly recuring revenue. I would like to have a button (or similar) that generate a 12 month forecast (e.g. one column for each month) in Google Sheets (or in Monday if possible) by for each item (customer) take the start date and for all months until the end date place the monthly recuring revenue in that month’s column. Is that possible and if so, how do I do that? Cheers,

I’m trying to create a Monday app and integrate a board view. After creating a Feature in the app and running the following command, no URL is being retuned: npx @mondaydotcomorg/monday-cli@latest scaffold run ./ quickstart-react -t board-view-XXXXXXXX The following output is given: Need to install the following packages: @mondaydotcomorg/monday-cli@2.2.1 Ok to proceed? (y) y npm WARN deprecated @types/source-map@0.5.7: This is a stub types definition for source-map (https://github.com/mozilla/source-map). source-map provides its own type definitions, so you don't need @types/source-map installed! npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instea

Hey all, I’m currently trying to figure out the fastest way to load all board items with the new API versions (2023-10 and above). One thing I realized during my tests is that using ... on MirrorValue has quite a negative impact on the loading performance. Here are two screenshots of queries to fetch a slice of 500 items in a board. In the first example, ... on MirrorValue isn’t used, it takes the API about 8 seconds to respond. In the second example ... on MirrorValue is used, it takes the API roughly 48 seconds to respond. So it’s about 6 times slower. Is this something that could be improved? If I use the main board view on monday.com, it loads very fast in comparison. Without “… on MirrorValue”: With “… on MirrorValue”:

Good morning! Currently, we are using PowerShell to send emails containing spreadsheets generated from our SQL scripts. We would like to stop sending it via email and instead send them to a board in Monday.com. Is this possible using the API? Now, I know there is the email to item function. But, we operate out of an Outlook public folder and do not have the rights to forward email out of that folder. The best solution would be to take email completely out of the workflow and have the PowerShell script send it directly to a board in Monday.com. From my searching there doesn’t seem to be very much documentation for PowerShell & Monday.com. How could I go about my next step?

Hi Team, I have a relatively specific case regarding Connect Board column values and moving items across boards. I understand the limitations created and the reasons involved with moving items across boards when they are connected to other boards. Our use case is that most of our day to day tasks are held on one ‘Main’ board, with lots of bits of data being fed in from/to other boards. Many items are even created by other boards before being added to the Main board. Connect Board column values allow us to track where those items have come from, and to create report dashboards etc that filter by these values or values mirrored from the connected boards. Our Main board is now becoming full and we will need to start removing some of these items. We are not deleting them or archiving them, as we need them for the reporting dashboards. Instead, I’ve created a duplicate of the main board and am attempting to move the items there, but can’t actually move any items as lots of data is lost. It’

I am having trouble creating items. I have read through the api documentation and have tried setting up my post request exactly shown in the docs. I unfortunately cannot share my code one for one since some of the information is sensitive. Though the problem seems to be coming from how the “column_values” are formatted. Code The purpose of the update_payload variable is to fix the column values. I created some code that parses data and correctly formats the forward slashes to how create_items mutation example looks like. # python 3.10 import json import requests apiKey = 'xxx' apiUrl = "https://api.monday.com/v2" headers = {"Authorization" : apiKey, "Content-Type" : 'application/json', "API-Version" : '2023-10'} def create_item(board_id, group_id, item_name, column_values): payload = f""" mutation {{ create_item (board_id: {board_id} group_id: {json.dumps(group_id)} item_name: {json.dumps(item_name)} column_values: {json.dumps(column_values)})

As I’m looking at the API, I’m noticing that the old “person” and “team” columns aren’t listed as supported column types any more. Which makes sense since they are deprecated. Has in all the mondayDB work, etc. those legacy columns on old boards been converted to “people” columns? Just wondering what’s going to happen if those columns show up on boards (if they even exist on boards now). Its not something I think about much, since I can’t even make them to test them. But, if they can show up on really old boards… I’d like to know if I still need to attempt to account for them.

monday.com has announced that support for the current default API version, 2023-07, is ending January 15, 2024. The new version, 2023-10, is set to become the default as of January 15, 2024. According to monday, there are breaking changes coming with this new version. This community post in the Make community precisely captures my concerns. We can afford to wait until Monday for a potential solution, but waiting for months is not an option. Especially because we don’t know what the solution will be. I’m also concerned about the long-term implications of these API changes. If we’re facing breaking changes now, will this happen more often in the future? The investment of 40+ hours (for the company that I work for) for each significant API update from Monday is already steep. As we continue to build more integrations and create scenarios, this time will only increase. I’m interested in understanding whether Monday has plans to introduce breaking changes more frequently. This information i

Hey! As far as I understand, with mondaydb formulas now get calculated in the backend. So I was wondering when we can expect the API to return the calculated formula results? In our app, Spreadsheet Gorilla, we are currently executing the formulas client side. This works to some degree but with certain limitations. – Simon

I wanted to perform a search using the Items page by column values query using the “2023-10” API version. I want to get the sub-item details—that has an Item-ID column type—by using the value in that field. Using items_page_by_column_values with column_id and column_values gave me an error: Error Code: UnsupportedItemsByColumnValueQuery Error Message: Column of type pulse-id is not yet supported for this query Error Data: {“column_id”:“item_id”,“column_type”:“pulse-id”} Looking at the docs I found that searching for items_page_by_column_values, item-ID column is not supported. Are there any ways that I can get the column details by performing a search with the “item-Id” column type? Given is a screenshot of the column where I want to find the details of the sub-item.

Hi All, my first post in the forum so please bear with me. 😊 I want to send a notification to a team just like you can do through the UI via @TeamABC, but as far as I can see it is only possible to choose user_id as identifier for the graphql mutation. Is it possible to address a team somehow? My workaround so far is to extract all the users for a given team and notify them one-by-one, but it is not very elegant.

Im trying to write a query to move an item from one board to another. this is the example from the docs: mutation { move_item_to_board (board_id:1234567890, group_id: "new_group", item_id:9876543210, columns_mapping: [{source:"status", target:"status2"}, {source:"person", target:"person"}, {source:"date", target:"date4"}]) { id } } This is my query (I’ve removed the ids for this post) : mutation { move_item_to_board ( board_id: 0000000000, group_id: "0000000000_group", item_id: 0000000000, columns_mapping: [ {source:"id_number", target:null}, {source:"email", target:"text9"}, {source:"text", target:"text0"}, {source:"text8", target:"text"}, {source:"status1", target:null}, {source:"dropdown", target:"dropdown37"}, {source:"dup__of_referral", target:"dup__of_referral"}, {source:"phone5", target:"phone7"}, {source:"date", target:null},

Hi team, I feel it would be better to input Account Slug in the monetization section for extending the trial or offering a discount instead of Account Id. The slug is more easily accessible to customers as it shows up in the browser url, and I believe there should be a 1 to 1 mapping between account Id and the slug.

Hi there! I’m migrating a Monday API python wrapper to work on the 2023-10 version of the API, and I found out that the field items doesn’t accept the item ID anymore! How is anyone supposed to find data about a specific item using only the item ID? For example, this query gets the item updates, works perfectly on 2023-04: query{ boards (ids: %s){ items(ids: %s){ updates (limit: %s) { id, body, created_at, updated_at, creator { id, name, email }, assets { id, name, url, file_extension, file_size }, replies { id, body, creator{ id, name, e

Hi I need to extract BoardID name,itemID name and date created and date updated {“query”:"{ boards{ id name columns { title id type } groups { title id } items { id name group { id } column_values { id text value }}}} "} i use like above but i can find date column how to extract date with respet to item

Hello everyone I am building an integration app and would like to host it somewhere. But I’m not sure where this should be. Should I treat the app like a normal REST API built on node and express? Because that’s what I could comprehend. And in that case, should hosting services like Digital Ocean be good enough? This is my first app and I might not be making a lot of sense over here. So apologies for that. Highly appreciate any feedbacks. Thanks!

We’re working on improving our Glances app onboarding flow in Monday. Is it possible to know when an App was installed in monday? Or a way to know if it’s the current user’s first time to use the app? We’re trying to find a way to determine if the current monday user just installed the app so we can trigger certain things on our backend. We have the app webhooks installed, but I don’t know how reliable the timing is between when we get the actual “app installed” hook vs. when the user actually clicks the install button from the monday marketplace. Any ideas? Thanks!

i am trying to integrate from our git into monday and need to transfer the git’s ticket description into a long_text column. as the description can include markdown, it will include hashes and other special characters that seem to break the graphQL api (e.g. hashes are comments in graphql etc.) should be easy to fix if I knew the expected encoding for long_text api input strings. But could not find any. working in nodejs with raw data. First try (which works api wise but does not result in proper display of the texts): ` ${mutationName} : change_multiple_column_values( board_id: $boardid, item_id: 1273911846, column_values: "{ \\\\"name\\\\":\\\\"${gitlabIssue.title}\\\\", \\\\"text\\\\":\\\\"${gitlabIssue.title}\\\\", \\\\"long_text\\\\":\\\\"${encodeURIComponent(gitlabIssue.description)}\\\\" }" ) { id name } ` before I try all string encoding

Hi, Does the new version of the API (2023-10) include features to deactivate and delete users? Br, YH

Hello Monday.com dev forum! As the title suggests, I am trying to integrate Monday.com with Dialpad to send SMS Text messages. Only users at my current company will use it. My plan is to use Salesforce as both the integration endpoint as well as the database layer as that is where most of my experience is. The idea is that my workflow recipe will have an Authorization URL that is my Salesforce endpoint that will decode the JWT token and retrieve the userId, recipeId, and backToUrl. Then it will redirect to the Dialpad OAuth URL where the user will then login. Once they have successfully logged in, Dialpad will redirect to a different Salesforce endpoint where it will get the Dialpad API Key. The Salesforce endpoint will then save the userId+recipeId and API Key as a key value pair that can be accessed whenever the Workflow Recipe is fired. This seems like it would work in theory but I am running into some problems. When Dialpad succesfully authenticates and redirects to my endpoint, I

I am attempting to update a people column, with relevant teams to the user in the column. The mutation in the API playground appears to by syntactically correct, but returns a 500 error. I am very much a novice in this arena still and can’t seem to sort this out. The query is as follows: mutation { change_column_value( board_id: 11111111111111111 item_id: 22222222222 column_id: “multiple_person1” value: {personsAndTeams: [ {id: 12345, kind: “team”}, {id: 678910, kind: “team”}]} ) { id } } Any help would be appreciated.