Recently active topics

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 OAuth access token in Secure Storage When calling monday APIs from the backend, I retrieve that token and use it like this:  import { ApiClient } from "@mondaydotcomorg/api"; const mondayApiClient = new ApiClient({ token: accessToken }); const query = ` query { custom_ac

Hi everyone!As part of our ongoing efforts to improve the stability and reliability of monday code we’ve identified that the current Secure Storage limits are too permissive which impose constant stability risks to our Secure Storage solution which have a negative impact on many app developers and monday customers (“noisy neighbour problem”). In order to reduce this risk we’ll be lowering this limit over the next few weeks from the current limit of 30 requests per second to 7 requests per second.This will impact a very small number of apps which currently do not use any method of caching for fetching tokens from the Secure Storage. The final ETA for this change is February 2nd Greg

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:Am I missing something?  Is this quickstart guide out of date?  I appreciate any help you might provide.Jeff.

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: My middleware still sees the old token in SecureStorage. It returns 200 OK for the auth check, but the API calls fail later because the token lacks the new boards:write permission. Here is a simplified version of my check:TypeScript // Middleware or Auth Check Logicexport async function checkAuth(req, res, next) { const secu

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 const redirectUri = `${currentOrigin}/oauth/callback`; const authUrl = `https://auth.monday.com/oauth2/authorize?client_id=${ context.app.clientId }&redirect_uri=${encodeURIComponent(redirectUri)}`; monday.execute("openLinkInTab", { url: authUrl });};Backend (Callback):TypeScript export async f

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 🙏

Hi partners 👋We’d like to share an upcoming change related to the Integration for Sentence Builder feature.In two weeks (Jan 26th), we’ll be moving the Integration for Sentence Builder app feature into maintenance-only mode.This means:🚫 Creating new Integration for Sentence Builder features will be blocked ✏️ Existing Integration for Sentence Builder features can still be edited and maintained 🛠️ The feature in your app will be supported for maintenance only, with no new capabilities addedWe’re making this change as we continue to invest in and evolve our newer automation infrastructure, which offers improved security, scalability, and reuse across monday products.If you’re currently using Integration for Sentence Builder, there’s no immediate action required. If you’re planning new integrations, we recommend building them using our newer integration capabilities instead.We’ll be sharing documentation and guidance on how to build equivalent integrations on the new infrastructure to

You can now test any app version locally by setting it as your active version. Once selected, your personal development environment will run that version so you can test in isolation or compare it with production, without impacting end users. This setting applies only to your local environment.By default, the most recently created version is set as active. You can manually choose any live, gradual release, or draft version for internal testing.Not supported for active version testingWorkspace templates Integration for sentence builder (Read here the latest news about the New Automation Builder)How to designate an active versionIn the left-side menu, go to Manage > App Versions Find the version you want to test and click the three dots in the Actions column Select Set as active versionRead the full documentation here >If you try it out, let us know what workflows it helps with and what you would like to see supported next.

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] 

Hello everyone,Over the past months, we’ve been rebuilding the foundation that powers automations on monday. This new, workflows-based infrastructure now drives how automations are built across the platform, including the new automation builder, monday workflows, and future automation experiences.In the coming weeks, we’ll begin gradually rolling out the new automation builder. This rollout is part of a broader shift toward a single, shared automation foundation that allows automation features to be reused across multiple experiences, rather than being tied to a single builder.What this means at a high level: Existing automations will continue running as they do today. There’s no immediate action required. To continue appearing in the new automation experiences as they rollout, apps with automation features will need to migrate to this new foundation. Starting today, we are running an A/B test for the new Automation Builder, which will be rolled out to 5% of users who are creatin

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 app notified when a new board is created from template would allow us to duplicate the configuration straight away.

Hi Everyone!We have some news regarding monday code, our hosting service for monday apps.To better support our global customer community and meet growing data residency needs, we are expanding our infrastructure.Starting January 2026, we are officially adding Israel (IL) as our fourth hosting region, joining our existing locations in the US, AUS, and EU.What this means for developersThis is a significant update for anyone maintaining multi-region apps. Please take note of the following requirements and limitations as you prepare for the rollout: Mandatory IL deployment: If you have an existing multi-region app, deployment to the IL region will now be mandatory when promoting a new version to "Live." Scheduler availability: At this time, the monday code Scheduler is not supported in the IL region. If your app relies on scheduled jobs, please plan your regional logic accordingly. Why is this happening?As more customers move toward regional data residency, it is essential that the apps

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.

  Hi everyone,   Quick question about Monday.com app publishing:  We built a third-party CRM integration for another platform. Our Monday.com app is  OAuth-only - no UI, no features within Monday.com. Users authenticate via OAuth to  allow syncing CRM data to Monday boards.   Current issue: OAuth only works for our organization (dev mode). External users can't  authenticate.  Question: Must we publish to Monday.com Marketplace just for OAuth, even though the app   has no standalone features in Monday.com? Is there an alternative for production OAuth   access?   All user interaction happens in the external platform. The Monday app just enables API  access.   Thanks for any guidance!

 Hey everyone! 👋  I'm building a custom Monday.com app and running into an issue with custom field dependencies. Hoping someone here has encountered this before!  The Problem  I have two custom field types with a dependency relationship:  - Boardz (parent field) - Lists boards ✅ Working  - Viewz (dependent field) - Should list views from selected board ❌ Not working  When I select a board and then click on the view dropdown, no network request is made at all. The field just shows "Please select a board first" even though a board IS selected.  My Setup  Field Type 1 - "Boardz":  Type: List (Remote Options)  Remote Options URL: https://...app/integrations/remote-options/boards  Default field key: boardId  Dependencies: None  Status: ✅ Works perfectly - returns board list  Field Type 2 - "Viewz":  Type: List (Remote Options)  Remote Options URL: https://...app/integrations/remote-options/views  Default field key: viewId  Dependencies: Boardz (Field key: boardId)  Status: ❌ No network req

My automation has been successfully running the following mutation daily for weeks:```mutation updateItem($board_id: ID!, $item_id: ID!, $column_values: JSON!) { change_multiple_column_values( board_id: $board_id item_id: $item_id column_values: $column_values ) { id }}```With the following variables:```{ "board_id": 8767955035, "group_id": "topics", "column_values": "{\"date4\":\"2026-07-24 00:00:00\"}", "item_id": "8954255421"}```The `group_id` variable is set, but not used, so this is just a red herring.Today when it ran, I got the following response:```{ "data": {}, "errors": [ { "message": "Unauthorized field or type", "path": [ "change_multiple_column_values" ], "extensions": { "code": "UNAUTHORIZED_FIELD_OR_TYPE" } } ], "extensions": { "request_id": "601955a7-20fb-9f36-badf-826dbf31145e" }}```Nothing has changed on the app, automation, or board, but today it failed.Running the same mutation in the GraphQL pl

I am working on a Custom Widget. And I am adding a Field, of type Column and only allowing Timeline-type columns.  When I go to Settings in my implemented Custom Widget, it’s only showing the item columns, but no the subitem columns that mach with this criteriaI want to be able of selecting also which subitem column, of type Timeline, I want to use.

Hello everyone.I see monday recently added support for API Key Authentication in Credential Feature for workflow blocks, is there something similar for sentence recipe automations?But more importantly, would an app using API Key Authentication be accepted in the marketplace?I know OAuth is the recommended method and that’s what I’ve used for my other apps, but there are some third party services that don’t have OAuth.

Hi all!Excited to be part of the community, and to share that I finally managed to push this over the first major milestone: launching in the marketplace!The app is for vertically grouping columns together, hiding/showing them, and colorizing them. The initial users of the app seemed to feel like it had lots of potential and I’m curious to hear what you all think. You can make custom groups of columns per horizontal item group or globally across all item groups.You can find it here: https://monday.com/marketplace/listing/10000997/column-groupsWhat can be better? What doesn’t work well for you?Thanks for the feedback and encouragement, it’s been both fun and frustrating to navigate the development ecosystem, but I think things are moving along now.Cheers,Brad

Hello,We are experiencing an issue while configuring webhooks in the Developer Center. Specifically, we are unable to add our Live version URL; the system returns an error every time we attempt to save it but the version-specific URL is accepted without any issues. We have followed the official documentation and the setup guide, both of which recommend using the Live URL. Could you please help us understand why the Live URL is being rejected?Thank you for your assistance. 

Hi everyone,I’m excited to share a new app I’ve been working on called Team Glossary.The Problem: We found that as teams scale, unique internal terminology and acronyms often lead to confusion, especially for new hires. Static boards or Workdocs help, but they require users to manually search for definitions, which creates friction and leads to low adoption.The Solution: Team Glossary allows you to build a central repository of terms, but the real value is in the Item View integration.Key Features: Auto-Detection: The app automatically identifies defined terms within your item views and shows their definitions in the Glossary item view. Centralized Management: Easily add and update terms from one central location(only admins can add/edit/delete new terms). Standard terms import: You can easily import 200+ standard terms across industries to get started quickly Why I built it: I wanted to bridge the gap between "having a glossary" and "using a glossary."I’d love to get your feedback