Add endpoint for retrieving board templates

monday Apps & Developers Feature Requests - API and Apps Framework
, , ,
1

Hey monday team!

Since your software is centered around boards, and board structures are defined by templates, it would be incredibly helpful to have an API endpoint that reliably retrieves template IDs.

Currently, there’s no dedicated endpoint for this, which means we have to identify template IDs manually. Adding this feature would be especially useful for operations like board creation (see the example below)

Xnip2024-10-31_08-45-00
Xnip2024-10-31_08-45-001384×2072 380 KB

Request: Add a simple endpoint that returns available template IDs and their basic information (maybe something like below):

{
  "templates": [
    {
      "id": "1234567890",
      "name": "Marketing Campaign Template",
      "description": "Basic marketing campaign tracker"
    },
    {
      "id": "0987654321",
      "name": "Simple Project Template",
      "description": "Basic project management board"
    }
  ]
}

Adding this endpoint would greatly enhance the power and utility of the existing “create board” functionality.

Cheers,

Martin

2

This is what the “board from template” field for recipes is for. It already exists without the API.

That said its broken because monday in its infinite wisdom redid the template system and it returns template_ids the API can’t access.

3

Agree with @codyfrisch. monday’s infinite wisdom did break lot of apps that rely on knowing the boardId of the template. As they now return the templateId an app can’t do anything with the template board (except creating a new board out of it). I really don’t understand that a professional organization makes these kind of breaking changes and on top of it do not document them.

4

@basdebruin is it too much to ask of them to even admit they broke it? because at this point I can’t get acknowledgement they are even aware there is an issue. I have tried several times and it just falls on deaf ears.

5

hi @codyfrisch, it is a typical “it depends” answer. When they started rolling out the new Template Editor the UI element where endusers can create a board out of a template and define the workspace / folder / etc. returns the templateId, where it user to return the boardId of the template board. This broke some of our apps and even their own custom automations to create a board. The API call to create a board failed because of the templateId and not the boardId. They admitted this was a bug and solved it by supporting the templateId in the API call to create a board. What they did not admit or solved is the fact that an app can’t inspect the template (e.g. checking for necessary column types) as the API calls that work on a boardId do not work on a templateId.

This is not the first time that we had to redesign apps because monday has some bright idea to make changes to software.

6

@basdebruin As it stands today, using the “board from template” field, which returns a template ID of the template the user chooses in the field - MOST of them fail when used with the create_board mutation.

7

Hello everyone!

Thank you for the feedback here!

We understand the issue the mentioned changes brought and we apologise for the inconvenience.

If you have a flow that is broken at the moment please do not hesitate to open a ticket with us and we will do our best to help you resolve it.