Question about handling multiple column IDs cleanly in Monday integration

Hi everyone,

I’m working on an integration where, when a user triggers an API action, my app fetches data from a third-party service and updates multiple columns on a Monday board.

The main challenge I’m facing is how to handle column IDs in a clean and scalable way.

Currently:

• I usually rely on column fields in the recipe to get the columnId, which works fine.

• However, when I need to update many columns (for example 5–10 columns), adding that many column fields makes the recipe sentence very long and not clean.

• I tried using item values, but they only return the columnId without any clear reference to which column it belongs to.

• If I use dynamic mapping, I lose access to the actual columnId, which my integration logic still needs.

So my question is:

Is there any way in Monday to pass multiple columns at once — including both the columnId and some kind of alias / logical name — so that the integration app can handle column updates more easily?

I’m looking for a pattern or best practice to avoid:

• Overloading the recipe sentence with too many column fields

• Losing the mapping between column name ↔ column ID

Any suggestions, recommended approaches, or existing limitations I should be aware of would be greatly appreciated.

Thanks in advance!