Unanswered questions

OK, at some time there has been an undocumented change to the create_timeline_item mutation. You used to be able to send a timestamp in and it would respect that timestamp as the created_at  time.Example:mutation createTimelineEntry($customActivityId: String!, $itemId: ID!, $title: String!, $summary: String!, $content: String!, $timestamp: ISO8601DateTime!) { create_timeline_item( item_id: $itemId custom_activity_id: $customActivityId title: $title summary: $summary content: $content timestamp: $timestamp ) { id }}GraphQL Variables:{ "timestamp": "2024-05-08T11:34:39.000Z", "customActivityId": "e589f9c3-b4a7-4a7f-bcc1-d6164f4460b7", "itemId": 2957556816, "title": "🕰️ Historic walk around Sheffield", "summary": "Dear John\n\nThank you for signing up to the historic walk around Sheffield, starting at the Peace Gardens. \n\nThe walk will take in some of the city's most fascinating landmarks and stories, from its medieval origins through to its industrial heri

Let's say my app is an integration with M365/Outlook and has a trigger "When email is flagged in Outlook"...I need to create this automation block as a trigger with:A subscribe URL - create the incoming webhook subscription from Outlook to listen to events An unsubscribe URL -  deletes the incoming webhook from OutlookBoth of these will use the credentials feature and monday will pass me a valid, but short lived access token for use with Microsoft 365.Here's the hard part...I also need to regularly update the Microsoft Graph to renew the webhook subscription (as mail subscriptions expire after 3 days)This will need to be done with a monday-code cron job which:requests a new access token from monday for the correct user sends the webhook subscription renewal to MicrosoftIn the old infra, we’d use a credentials field and handle the logic ourselves, in our app, but with the new infra, the credentials are stored by monday and are abstracted away completely.👉 How do I request a new Microso

I have a credentials block configured in my automation with scope x. I'm adding a new automation block that requires an additional scope y, so the combined scopes are now x y.New sign-ins will correctly receive the x y scope. However, users who previously authenticated only have the x scope stored.My question: When one of those existing automations runs for a user with only the x scope, what happens?Does the OAuth token refresh using the original x scope and continue to work? Or does it attempt a refresh with the new x y scope, fail due to the mismatch, and break the automation?Follow-up: If existing users do need to re-authenticate, what's the recommended way to surface that to them — is there a built-in mechanism in monday.com for prompting re-auth, or does that need to be handled manually?

I’m finalising our recipes as part of the migration, the last ones we have is to sync data from an external system to an item. In the sentance builder, we had a custom trigger than output a dynamic mapping object and we mapped this to “item mapping”.in the automation builder, the migration guide says to use “Item Values” now. We have a custom Trigger (“Object Created”) which outputs the custom object definition and a string of the objectIdWe also have an Action “Create item from 3rd party” which accepts a boardId, itemValues  and an external object id and then we have  the automation template joining these blocks together. This works fine in the Workflow Builder, it shows the Object from the previous trigger as expected. However it fails in the automation builder. It simply shows “No options available”. If I look at the network requests, I can see it retrieving my custom field defintions, it just doesn’t allow me to map my external data into columns to then process Has any been able to

Hi monday team,I’m debugging a monday-code live installation issue and wanted to confirm expected behavior for the signed JWT aud field.For a new user installing the live app, the authenticated request context contains this public base URL derived from aud:https://ee78c-service-14856766-dfa...But the expected live app URL is:https://live1-service-14856766-dfa...Example log:[userId=103522...] Authenticated monday request context: { accountId: 14856..., userId: 103522..., hasBackToUrl: true, hasShortLivedToken: true, publicBaseUrl: 'https://ee78c-service-14856766-dfa...' }We use the JWT aud value to build OAuth redirect URIs and Google Calendar webhook URLs. If aud can contain a transient/internal service URL instead of the canonical live URL, those redirects/webhooks may be registered against the wrong host.Is it expected that aud may point to a non-live monday-code service URL for live installations? Or should live app requests always include the canonical live URL in aud?If this is ex

Hi everyone,I'm running into an issue with the Apps Framework regarding custom automations, and I wanted to see if anyone else has experienced this or if it's a known bug.The Setup:I've built an integration that relies on a custom trigger for file uploads. In the setup, the user authorizes and selects their credentials, which are tied to their external platform's team ID and user ID.The Issue:When a user builds the automation from scratch using the custom recipe, everything works perfectly. The credentialsValues object is properly populated in the webhook payload, allowing us to route the request to the correct external team.However, when we package this exact same setup into an Automation Template and the user installs it, the webhook fires but the credentialsValues object drops entirely and comes through as empty ({}).I think this wouldn’t be the expected behaviour. 

Hi,I added an "action" feature and set up a dialog box to "large," but it doesn't take up that much space.Can I somehow render larger dialog?

Hello!With the deprecation of “Integration for sentence builder”, I need to migrate my existing workflow blocks to the new automation blocks. I’m struggling to reproduce the same behavior.My current, working sentence builder action works like this:When column changes → user selects the relevant column → user selects my action → user maps the fields.For example:When Registration changes → then set vehicle brand in >brand column<When the automation runs, monday sends the following parameters to my Run URL:boardId itemId columnId — the selected Registration column columnValue — the actual Registration value brandColumnId — the column where I should write the brandUsing these parameters, I can update the item through the GraphQL API.Below are the input fields from my old sentence builder action:Input fields of the old action in my integration for sentence builder With the new automation blocks, I tried to recreate the same behavior: the user enters a license plate/registration, and t

Hi,I need to include two separate views in the document. One that perfectly matches the "Doc Action" is great for "actions" called from the document content. Second, I want a top bar-level "button" that will show different content for that document. Can I use the "Doc toolbar AI assistant" because it seems to match my needs? However, my feature is not related to AI at all.

I recently connected Claude Chat to Monday. Claude said it created three new boards for me, but I can’t see them. We are subscribed to CRM and I just started the trial for Work Management. As the conversation with Claude progressed, it told me that via the connector it can only see the Main workspace. It can’t see CRM or Work Management. And I don’t see a Main workspace, only CRM and Work Management. How do I open up visibility so Claude can work in our CRM and Work Management workspaces?

For a Multi-level board, when I create a column of type Date, and then query the boards columns again, I do not see the Date column I just created returned via the API, even though I can see it was created in the UI.This also applies to the default Timeline column. Is this a bug?How can I get the Ids of a Date typed columns in order to insert the data into these columns via the API?

Hi everyone,I’ve been diving into the updates and it’s great to see the new support for querying multi-level subitems and the hierarchy_types: [multi_level] argument.However, I’ve hit a wall regarding programmatic creation. Currently, create_board seems to default to the classic structure. While we can now query deep hierarchies, I don't see a way to initialize a board as "Multi-Level" via the API.Are there plans to support multi-level boards creation via API?

I want to know the whole process from the scratch how to prepare app for the marketplace ?In terms of the security pricing and all related issues ?Is there any specific checklist to follow for this ?The app is deployed on the monday Code [Monday Server Side].

Hi everyone,I'm trying to post to a board's discussion section (not item-level updates) using the API. I can successfully read board-level updates using:query { boards(ids: [YOUR_BOARD_ID]) { updates(limit: 25, page: 1) { id body creator { id name } } }}However when trying to write, the create_update mutation only seems to support item_id — there's no board_id argument (confirmed via the playground autocomplete).Is there any workaround for posting to board-level discussion via the API? Or is this simply not supported as a write operation?Thanks!

Hi there, I am currently working on a use case that would involve retrieving all information from boards/projects using MCP, so that the agent can extract relevant information needed.I have familiarised myself with all the MCP tools from here and I have created an AI agent that can use these tools, however, I have noticed that whenever agent is using tools get_board_items_page and get_board_info to extract all relevant information available in the board it doesn't retrieve any subitems or linked columns, when I specifically name the subitem name or linked column name, it simply comes back to me saying it can't find it. The payload returned from using these tools confirms is as well. Could you please help me understand if I am missing anything? Is there another tool that should be used for linked columns and subitems? I have noticed that there is a tool create_item which allows the creation of subitem, so does that mean the current MCP tools don't allow to read subitem and linked column

Hi everyone,We are on an Enterprise plan and are trying to programmatically manage our product seat allocations via the API.Currently, we use the GraphQL invite_users mutation to provision our developers with access to the monday dev product: { "query": "mutation { invite_users(emails: [\"[Trigger.User.Email]\"], product: dev, user_role: MEMBER) { errors { message code email } invited_users { name id } } }"} We have a requirement to unassign/remove the work_management product seat from specific users while ensuring they keep their active monday dev seat.Testing in the API Playground, we couldn't find a GraphQL mutation to modify or strip an existing user's product allocations.Is there an undocumented or upcoming GraphQL mutation to update/remove specific product licenses from a user? Any guidance or workarounds from the team would be highly appreciated!

Hi everyone,I am currently trying to connect my Outlook calendar with my calendar so that both can sync together.I attempted to set this up using an integration.However, I ran into an issue where, even though I am using my office email account with admin rights, the system rejects the connection and prompts me to login in using an admin account instead.What’s confusing is that I am already the admin, so I am not sure why the sync is being blocked.Has anyone experienced this before, or could anyone guide me on what I might be missing or what I should try next? Thanks in advance for your help!

Hi everyone,I am opening this topic regarding the automation features migration (referenced here: https://developer.monday.com/apps/docs/automation-features-migration-overview).We are currently attempting to migrate our app, General Caster, to the new infrastructure, but we have encountered a critical, blocking compatibility issue: the "message" field is entirely missing.This field is strictly required for our users to write formulas using column references. Because the new infrastructure does not support this legacy feature, our migration is completely stalled.There is absolutely no workaround or alternative available to replicate this functionality on our end. With the migration deadline on April 30th, we need an urgent fix or a clear path forward to avoid breaking functionality for General Caster users.Could anyone suggest a fix for the missing "message" field or guidance on how to proceed?Thank you for your swift assistance.

With Portfolio (and I know most ppl here don't have access to that)...When I create a project board from a portfolio board, how do I know which project board a portfolio item is connected to, unless there's already an item in the project board?Once there's an item in the project board, they are automatically connected and I can access them using this:query linkedItems($portfolioBoardItemId: ID!) { items(ids: [ $portfolioBoardItemId ]) { column_values(types: [ board_relation ]) { id column { title settings # contains a list of *all* connected project boards } ... on BoardRelationValue { id linked_items { id name board { # Project board id name type } } } } } }...but if there are no items on the project board, how do I know which portfolio item is linked to which project board?It's stored somewhere, because all

What happens to an async automation block that has OAuth access to monday, but doesn't complete in the 30 minutes allowed for the shortLivedToken for async blocks?If I have OAuth access to monday in my block, I can take all the time in the world to complete, but will it say "In progress" after 30+. minutes, or "timeout failure" in the automation history?Let's say that I am importing a 20k row Excel spreadsheet into a boardIf I do this using the client side SDK in a view, like you can with Ripple Import, it will take about 4 hours to write everything to monday – I know, I've done it. You have to keep the computer awake and the browser tab open.But what happens if my async automation block takes 4 hours to complete?Can I publish a % completed back to monday as I go along? Or will I just get a "timeout failure" in the automation history?I'd really like the former and not the latter.If I could publish a % completed back to monday, maybe then it could reset the 30 minute timer to prevent a

Hi,We are migrating the authorization url to new credentials feature. After completing the OAuth process the account is not added in the recipe and there are no error message. We have followed the steps shown in this tutorial by monday.com. We tried multiple times and it’s not working at our side. Below is the extra details json body we are returning.{    "providerUniqueIdentifier": "728e0ec1-8a0b-403d-86e4-8a9d65b3e85e",  "displayName": "Mock Account"}Has anyone else run into this issue? If so, how did you resolve it?Thanks