What are the criteria for an integration column to be created form a custom action trigger.
As an example when using the google calendar integration, when a link it created updates the items integration column with a link to the created event.
As far as I can determine there are some rules that need to be met for this column to exist but those do not seem to be documented anywhere
Welcome to the community.
I’m sorry that you didn’t get an answer yet. I have sent it to tech team you should be answered soon.
Thanks a lot and have a wonderful week ahead.
I will double-check this one and let you know!
I double-checked this with the team. Currently, the integration column is not intended for external use and we will soon take it off our documentation.
Let me know if you have any other questions!
That is unfortunate since as far as I can see an integration column is the best choice for allowing plugins to record data against a item in Monday without having to save everything in a separate DB for each of those items. Same thing for create dedicated result columns based on integrations like the calendar integration does by putting a non mutable link column in the board.
Is there any plan for concept for that going forward that might be brought in?
I must concur.
As an integration developer, a write once, read many column has a lot of use for us in custom integration work to ensure that users don’t break it since we can’t modify permissions on a board.
If anything, I think documentation should be completed (whats missing is not that complicated) if anything.
Thank you for the feedback!
I have shared this with the team
Hi @codyfrisch @BWMuller
After checking with the technical team, this column is used only for internal integration and it will not be open to developers since the column itself is does not seem to be part of future planning.
A new sync mechanism that will replace this column is in progress and will be open for developers to use. However, there is no ETA for that at the moment.
Just be aware that developers have used it because nothing prevented it, beside not being documented (which lets be honest, is a lot of things!)
Hi again @codyfrisch
After speaking with the team, I can tell you that we are aware of the fact that developers use this.
Since it wasn’t the intention, it is not documented and the upcoming solution will be.
If the column will be deprecated, it will be after a proper notice has been given.
hope it’s helps, and have a wonderful week.