Welcome to the new monday developer community
Your space to ask questions, access resources, and collaborate with trusted builders
Ask questions, solve problems, and network
Shape the roadmap with feature requests
Stay informed on new product updates
Join exclusive events to learn and grow
Be first to try our latest apps and features
I am building an app on monday code, both client side and server side. I am using the workspace app feature to a react page that has a button to fetch data from my database. I am getting a 405 Method not Allowed). It’s a simple fetch() to my server endpoint. Is this not allowed? Do I need to wrap it or something?I also noticed, this is the same error I get with a POST api call.
Hey all, I’m trying to run some Python within Zapier, to get all items where the Status Column is set to ‘In Progress’. I’m really struglling to figure out how to get more than 25 records at a time…?
So I know ```import mondaySdk from "monday-sdk-js";``` mondaySdk has these fuctions async getItem(key: string): Promise<{ data?: { value?: string } }> {return await this.mondaySdkClient.storage.getItem(key);} async setItem(key: string, value: string): Promise<any> {return await this.mondaySdkClient.storage.setItem(key, value);}and they work fine in Browser env but I am have app which needs to update the storage from my server envso for this``` class MondayRestStorage implements StorageBackend {private mondayToken: string; constructor(token: string) {this.mondayToken = token;} async getItem(key: string): Promise<{ data?: { value?: string } }> {const url = `https://apps-storage.monday.com/app_storage_api/v2/${key}?shareGlobally=false`; const response = await fetch(url, {method: "GET",headers: {Authorization: this.mondayToken,"Content-Type": "application/json","User-Agent": "monday-apps-sdk",},}); if (!response.ok) {console.warn(`Storage get failed: ${response.status}`);
I'm learning some Monday app development and I'm trying to get a deployment working on Monday Code from a monorepo setup.I’m using Turborepo and the main issue I’m having is creating a predeploy script to include my packages (which are currently included in my repo as npm workspaces) into the build folder to be included in the tarball. The build system used by Monday Code doesn’t seem to like the workspaces.In this video, @dipro mentions the monorepo scenario and creating a predeploy script at 23:20https://youtu.be/tXAKtabsXqM?si=SU6GhoJpgMSvSRLt&t=1400In the same video, at timestamp 15:07 I can see one of the test projects is called "monorepo monday code", but that project doesn’t seem to be in the “Hello World” apps at https://github.com/mondaycom/welcome-apps/tree/master/appsHas anyone successfully deployed to Monday Code from a monorepo or specifically turborepo?
Hi Monday Development Group,We’re building out a quoting system for our dealership inside Monday and want to know the best setup or Marketplace apps to use. Here’s what we need the system to handle: Choose whether a deal is Cash or Finance. Show unit pricing with the ability to apply both % and $ discounts. Add extras/add-ons pulled from our inventory board (with price, taxable flag, and availability). Automatically calculate taxes based on subtotal. If Finance is selected: show fields for Down Payment, APR, Term and automatically calculate the estimated monthly payment. Generate a client-facing proposal/PDF that includes all line items, totals, and our branded signature block. We have tried several of the third party apps, but have had no success. Please help us build out this pricing option!Thanks for your guidance — looking forward to your recommendations!
CLI Versionnpx mapps --version@mondaycom/apps-cli/4.8.0 linux-x64 node-v22.19.0What I triedCommand:npx mapps scheduler:create --verbose --print-command -a $APP_ID -s "0 * * * *" -n "execute-rules" --targetUrl "/execute-rules" -r 10 -b 60 -d "This execute rules hourly"Result:The request reaches the API but fails with 400 Bad Request.[06:36:38.575] ERROR: Request failed with status code 400 - Bad Request - ERR_BAD_REQUEST - {"error":"Bad Request"}: undefined[06:36:38.576] ERROR: scheduler_create err: { "type": "Error", "message": "Invalid request", ... }Alternative attemptBecause the CLI --help shows a -u, --targetUrl=<value> flag, I tried this instead:npx mapps scheduler:create --verbose --print-command -a $APP_ID -s "0 * * * *" -n "execute-rules" -u "/execute-rules" -r 10 -b 60 -d "This execute rules hourly"ResultThe CLI rejected the argument completely.[06:45:14.622] ERROR: Unexpected argument: /execute-rulesSee more help with --helpEnvironment App ID: $APP_
Is there a `create_labels` mutation in the GraphQL API? Or something functionally equivalent?I need to programatically create (add new) labels to a Dropdown column via the API.After going through the API documentation I haven’t found a way.Any suggestions greatly appreciated.
I’m experiencing the error below when authenticating in my app: {“error”:“invalid_scope”,“error_description”:“Invalid scope param”} The corresponding HTTP call is something like: https://marketplaceapps.monday.com/oauth2/authorize?oauth_payload_token=... followed by a JWT string. The decoded JWT looks like this: { “scope”: “me:read boards:read users:read”, “response_type”: “code”, “client_id”: “my-client-id”, “redirect_uri”: “my-redirect-uri”, “oauth_version”: 2 } The contents of the above has all the right values afaik. The scopes are enabled in my app config. I’ve seen this thread: Check authorization response - monday Apps & Developers / Feature Requests - API and Apps Framework - monday Community Forum Even if I uninstall the app and reinstall it, the error persists. The funny thing is that the behavior is not consistent, sometimes I get through to the authorization page. I can’t reproduce this with the app that is bound to my dev environment. With that app, the authorization
How do I determine if a user is a viewer so I restrict them from using my app?
FetchError: request to https://api.monday.com/v2 failed, reason: read ECONNRESET at ClientRequest.<anonymous> (/projects//node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:524:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:101:11) at TLSSocket.socketErrorListener (node:_http_client:504:5) at TLSSocket.emit (node:events:524:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at processTicksAndRejections (node:internal/process/task_queues:82:21) { type: 'system', errno: 'ECONNRESET', code: 'ECONNRESET'}
I am using the 2025-10 API version, attempting to create a new connected board column. The issue I am having is that the target board is not being connected when I provide a JSON string instead of an object. The mutation is (board IDs have been changed):mutation CreateBoardRelation { create_column ( board_id: 1234567890, title: "Group", column_type: board_relation, defaults: "{\"boardId\":0987654321,\"allowMultipleItems\":false,\"allowCreateReflectionColumn\":true}" ) { id title __typename }}If the defaults are provided as an object, it works as expected. There are no parsing errors in the response.
Hi Guys!Basically I am creating an automized Monday followup system via gmail. The idea goes as follows:Get a client email Have a button to press (g-suit extension), and a short form asking project details (this will be for quoting) This extension then populates a monday group row with the information provided and MOST IMPORTANTLY the original email for reply followups (I don’t want to create a separate email for this).So my question is, how would you guys port the original email over into a monday CRM group?Thanks so much for future help!
Discover proven tactics and built-in tools to help monday marketplace partners drive retention.
Everything you need to work with our GraphQL API.
Learn how to build custom apps on the monday.com platform.
Additional tools and information
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.