API & Apps framework

HI, I am using the API version 2024-01 and since recently the value field returns null on connect boards.As an example  { boards(ids: my-id) { items_page(limit: 1) { items { column_values (ids: "boards_verbinden__1") { id type value text } } } }}returns{ "data": { "boards": [ { "items_page": { "items": [ { "column_values": [ { "id": "boards_verbinden__1", "type": "board_relation", "value": null, "text": null } ] } ] } } ] }

Hello, I would like to understand the output fields that are available for all automation triggers. Including pre-defined Monday triggers.  There does not appear to be a tool in the UI, not in the automation runtime view, in the sentence creation or in the app development UI. Is there an API I can call that will provide me the outputs for a trigger.  Say, for example: “When a status-column changes to X” Do I get the boardId, itemId, status-column and status-column-values? Where is this defined? How do examine the output field schema? CheersJem 

Hi,due to migration of my app to workflows I try to use the credential feature to initiate OAuth to a Mattermost server. Unfortunately, Mattermost only accepts a length of 1024 characters for the state field. The state that the credential feature sends is about 1152 character long and so the request is rejected. Is there a chance to set a limit of the state field in the feature?Thanks and best regards, Marcus

Hey builders 👋We’ve just published the first monday Marketplace & Developer Monthly Digest of 2026.The goal of this format is simple:Once a month, we’ll recap the most important platform updates for app developers in one quick video.This first one comes with a slight delay, but we’re officially kicking things off. I’d really love your feedback on the format. Watch it here:Here’s what we covered🚀 Build Skills for monday SidekickSidekick is officially out of beta, and developers can now build AI-powered skills for their apps.Read the full announcement here⚠️ Action Required: Migrate Legacy Automation FeaturesLegacy automation features mus

Hi everyone,I’m working on an integration where, when a user triggers an API action, my app fetches data from a third-party service and updates multiple columns on a Monday board.The main challenge I’m facing is how to handle column IDs in a clean and scalable way.Currently: I usually rely on column fields in the recipe to get the columnId, which works fine. However, when I need to update many columns (for example 5–10 columns), adding that many column fields makes the recipe sentence very long and not clean. I tried using item values, but they only return the columnId without any clear reference to which column it belongs to. If I use dynamic mapping, I lose access to the actual columnId, which my integration logic still needs. So my question is:Is

Hi there!The docs recommend using change_multiple_column_values when possible but never mention how it reduces complexity cost and by how much.Let’s put the question this way: If we use change_simple_column_value to change 1 column it costs 30k complexity points. So 10 column changes = 300k.Is it that if we use change_multiple_column_values all of 10 changes at once costs only 30k? How does this get calculated?

Hello,I am currently building an automation app for monday.com that allows users to automate workflows within their boards.So far, I have successfully completed authentication and all other required setup. I have also built several custom views and implemented the Integration Sentence Builder feature. The recipe sentence automation builder is working well overall.However, I am currently stuck while building a dynamic recipe sentence UI inside the Integration Sentence Builder. I have already posted in the community and sent an email to monday.com support, but I have not received a response yet. That’s why I’m writing with a detailed explanation of what I’m trying to achieve and where I’m facing difficulties.What I want to buildI want to create a recipe sentence like:When {status} changes to {something}, send {template name} {dynamically loaded inputs based on the template} from {WhatsApp account num

Hi everyone!I’ve been experimenting with the change_multiple_column_values mutation to update the Files Column with external links (like Google Drive). While the documentation currently lists this as unsupported for this specific mutation, I found that it actually works—with one major catch regarding fileId. The MethodI am using the following mutation:mutation updateFileLink ($columnValues: JSON!) { change_multiple_column_values( item_id: "my_item_id", board_id: "my_board_id", column_values: $columnValues ) { id }}With this JSON as columnValues variable:{ "file_column_id": { "files": [ { "fileId": "file1_id", "fileType": "GOOGLE_DRIVE", "linkToFile": "https://drive.google.com/...",

Hi there,I am curious to know if you have plans to drop support for settings_str at any point since you have switched to the settings instead?

Hi everyone,Between January 28 and January 29, we identified an issue that caused temporary disruptions to some apps and integrations across a limited number of monday.com accounts.What happenedDuring this time, certain API requests intermittently failed to retrieve user API token scopes, which may have affected: App functionality Integrations Short-lived automation or authentication flows The issue has now been fully resolved, and all systems are operating normally.If you continue to experience any unexpected behavior or have questions, please feel free to reach out.

Hi everyone,I’d like to ask for feedback and ideas on whether we’re using the SDK Storage method correctly.Our custom app consists of a form-based flow: Form A is used to set up boards and item columns using monday.com’s GraphQL API. After a successful submission of Form A, Form B receives the generated board and column IDs from the GraphQL mutations. These IDs are then used in another mutation to create new items in the board (like a record table). App flow: Fill out Form A and click Submit Run GraphQL mutations to create boards and columns Retrieve the generated board and column IDs Store the IDs in monday Storage Redirect to Form B Form B retrieves the stored IDs For step #4, we are currently using monday

Hello,I am planning to develop a Monday.com automation app that will allow users to send messages to phone numbers stored in a Phone column.The app will work as follows: Users will have access to a list of pre-approved message templates. The user can select one template, and the message editor will automatically populate with the template text. Inside the message editor, users will be able to map values dynamically using suggested column names (Monday automatically suggests columns with the “Message” field type). Once the automation is configured and saved, it will listen for the specified trigger event. When the event occurs, a custom execution API endpoint will capture the event and process the operation (sending the message to the phone number).

Hello Monday Dev Community. I’m brand new to building apps within Monday (haven’t coded in a long time, but getting back into the game). I’ve followed this Quickstart guide and everything worked up to step 6 which is the following: When I run npm run build, I get an error that the build script does not exist. I checked the package.json file and it does not include the “build” script. I’m thinking that the quickstart guide is out of date, but I don’t like to assume. This is a list of scripts that npm run shows:

SDK SDK SDK. So many SDKs! Help me understand if I’m wrong. Software development kit https://developer.monday.com/apps/docs/introduction-to-the-sdk - Last commit: 1 month ago JavaScript SDK https://developer.monday.com/apps/docs/monday-code-javascript-sdk - Last commit: 9 months ago API SDK https://developer.monday.com/api-reference/docs/api-sdk - Last commit: 1 week ago Seems like the last one is the most actively maintained but I still cannot trust it because there are so many SDKs! Which one should be my go to and how do I kn

Hi monday devs. We receive daily support request from users reporting that they receive the following error message when they run a General Caster integration: Your automation has failed due to a resource not being found. We discovered that this error is returned by monday when the app is not installed on the workspace where the integration is running on. By design, even if an app (like General Caster, featuring custom integrations) is not installed in a workspace, the user can add and set an integration up in his boards, but when he runs it the error is returned. So if you don’t want to change this behavior and keep showing an app available in the workspace where it’s not installed on, please change the error message with something like: The app is not installed in this workspace. Please enable it in the admin area. cc @Matias.Monday

Hi everyone,I’m building a full-stack app using monday code (React UI + Express backend) and I want to make sure I’m following the correct authentication and authorization best practices.Current architectureUI → Backend authentication From the UI, I fetch monday.get("sessionToken") I send it to my backend in a request header In the backend, I verify/decode the sessionToken using my client_secret This works well for validating that the request comes from monday and from my app When decoding the sessionToken JWT, I noticed that it does not include a short-lived token that can be used to call monday APIs. OAuth & monday API calls I implemented a standard OAuth flow In the OAuth callback, I store the returned

Hi everyone,I'm building a Monday App using React and Express. I'm using SecureStorage to store the OAuth access_token after the handshake.I have a concern regarding Scope Management and Token Validation.Currently, I define my required scopes in an Environment Variable (e.g., MONDAY_SCOPES="boards:read users:read"). In my authentication middleware, I simply check if an access_token exists in the storage. If it exists, I assume the user is authorized.The Logic: Env: SCOPES="boards:read" User authorizes: I get a token with boards:read and save it to SecureStorage. Later: I update my app features and change Env to SCOPES="boards:read boards:write". The Problem:

Hi everyone,I am building a React + Express app and deploying it using the Monday CLI (mapps code:push).I am currently implementing the OAuth flow, but I am stuck in a tedious manual loop regarding the Redirect URI.The Scenario: Frontend: I initiate the OAuth flow using window.location.origin to build the redirect URI dynamically. Backend: In my callback function, I use an environment variable (MONDAY_VERSION_URL) to validate the redirect_uri during the token exchange. The Code:Frontend (Initiating Auth):JavaScript const startOAuth = async () => { const { data: context } = await monday.get("context"); const currentOrigin = window.location.origin; // This changes on every deploy

The monday.com Foundation Emergency Response Team is seeking a freelance developer to support an existing marketplace integration: KoboToolbox.The app is already built. The scope of work is ongoing technical support and bug fixing as issues arise.High availability during support requests is required. Our team operates in active emergency response contexts, where the stability and reliability of this integration is critical.This role is best suited for someone comfortable working under time-sensitive conditions and responding quickly when issues occur. We are a pro bono initiative from our Philanthropic Foundation, so we are looking for affordable services 🙏

Just thought I’d put this here.You can get the region of the monday account by decoding the shortLivedToken from an automation and getting the value of rgn and  extracting the first 2 letters for au, eu, il or us.It contains other information too, but what is aai?Example decoded shortLivedToken:{ "alg": "HS256", "typ": "JWT"}.{ "shortLived": true, "uid": 6......4, // user_id: number "actid": 2......2, // account_id: number "aid": 1......4, // app_id: number "aai": 2....1, // ???????????????????????????????????????? "rgn": "euc1", // region: string "exp": 1768213333, // token expiry: number "iat": 1768213033 // token issued at: number}.[Signature] 

Dear Community, I hope this message finds you all in good spirits. I would like to inquire about the fate of account Storage once a user decides to uninstall the app. Are the data wiped out entirely upon uninstallation, or does Monday.com retain any portion of this data for a certain period or under specific circumstances? Thank you all for your contributions and support. I eagerly await your insights and feedback.

Hi everyone,Has anyone found a way to support standard or managed templates in cases when an app stores board related data that should be duplicated when new boards are created from a template?In our case, the app stores column related metadata (in monday storage) used for column views (https://developer.monday.com/apps/docs/column-views). If a user adds our column to a managed template, we would like the app data to be automatically populated for all boards created from that template, so they don’t need to configure it in each boards. New boards created from template should have the app data populated from template as well.So far, we have not found a way to associate boards with the template they were created from. Having something like a parentBoardId or template reference on boards would make this much easier. Also having the a

Hello, I have some questions regarding ability of creation custom Column Views:Will be there some mechanism of conversion of ordinary column to custom one, without losing data and attached automations? Now if application is deleted, custom column becomes unclickable instead of turning to usual column as common sense suggests. Is it a bug? Will custom column views be supported in mobile app?In general it would be good to know roadmap for Custom Column improvements at least for nearest quarter to plan what can be get from platform and for what workarounds should be prepared.