I need to update the title of an item in my app when a user changes it in another view.
I see that there is a method called monday.listen, which takes “event” as an input. This listener gets triggered when a new item is added, or a column value is changed. But it is not fired for other common events like
Is there a plan to add these, or an alternative workaround?
The title of an item is not considered a column value, so when it changes it does not emit the “column_value_changed” event.
Instead, you’ll need to poll the API regularly to check if an item’s name was changed. Same for item deletion.
Thank you Bhowmik.
In our case, we have to poll for all the items in a board, and then do a diff with the previous response to see if some item was deleted. Which seems a bit tedious and network intensive. If we have a lot of simultaneous users, we could be hitting our API rate limits easily.
It would be amazing if these two events - title change and item deletion were also a part of the api specification. Hope these could be added in the near future.
Regards.
Hello @kranthi_thoughtflow,
Thank you for that feedback!
What about using webhooks? Would that be a possibility for you?
You could create some webhooks in the board. One with the trigger "When an item is deleted, one with the trigger “When an item’s name changes” and maybe one with the trigger “When an item is archived”.
What do you think?
Cheers,
Matias
Hey Thanks Matias.
I was not aware about webhooks. But I am a bit confused after watching the video.
Who creates the webhook? - Do we developers create the webhook and bind it to our app, or does the user create a webhook?
Hello again @kranthi_thoughtflow,
Anyone who has access to the board can create the webhook via UI, or you can create it yourself via API.
You will have to have an endpoint on your end that returns the challenge as explained in the article.
Let me know if you have any other questions!
Cheers,
Matias
Sounds great @Matias.Monday . I’ll give it a shot
Amazing!
Let us know if you need anything!
Hey @dipro . Wanted to circle back on this.
Since the listen api already exists, this could be extended to all other edit events on the board, like adding a new item, updating item title and deleting an item ( or subitem ).
I understand that title is not a column value. From the perspective of an app developer though, we would like to have a uniform api to listen to all edits or updates on the board. ( this could also include bulk updates )
Thanks for this suggestion! I’m happy to pass this on to our development team for their consideration.
@Matias.Monday - Can this be added as a feature request?
I think most of the framework is in place, and only support needs to be added for new columns.
Setting up a web-hook and backend seems like a lot of effort for something so trivial.
Hello @kranthi_thoughtflow,
We now have “When an item name changes” as a webhook! Is that what you needed?
@Matias.Monday - No. I want the monday.listen events to support the name column and item deletion. monday.listen
In our case, this would make it possible to build fully frontend applications without the need for a webhook or a backend.
Is there any specific reason why these should not be supported by the listen method?
The item name is not a column! Thats the underlying issue. Its a property of the item, not a column that belongs to the item.
(As weird as it seems, since you can get then name column existence back when you query a boards columns, and you mutate it like a column, you cannot get the actual value of the item name through column_values)
This is why it can’t be listened to.
I have opened a feature request to make the name a column_value. IF they can update the name through a column value mutation, it means the name is getting passed through the the column_values code to get back to the item. That means its entirely reasonable they could store then name as an actual column value and then forward the change also on to the item itself (as they do now). Would it be a bit of a change? Of course but it would really make the API/apps make a bit more sense since the name column is a column… sort of.
I understand there could be many ways to implement it.
I believe folks at monday are smart enough to figure out the internal architecture 
I’m just sharing a API consumer’s perspective. Without these things, the listen method feels half-cooked.
