Skip to main content

For the following automation:

When {status} changes to {something}, 
do my custom action with {Files}

where

  • {status} changes to {something} is a built in trigger
  • {Files} is restricted to columns of type File

If I have

  • a main board with columns Item Status and Item Files,
  • a subitem board with columns Subitem Status and Subitem Files

I’ll be able to select

  • ✅ either of Item Status or Subitem Status for {status}.
  • ❌ only Item Files (but not Subitem Files) for {files}

What’s the best and simplest way to allow Subitem Files in the {Files} field?

Hey David,

Bill here from monday.com 👋

This is likely happening due the the board context of the automation looking at the parent board ID and not the subitem board ID where the subitems files column is.

So that we can look into this further would you be able to please fill this form adding as much information as possible to it (such as account ID, board IDs, item IDs, timestamps, etc.) so that our team can take a look into it?

Cheers,
Bill

Hi @dvdsmpsn. Shanine here from Mindflows! I understand that you want to do a custom action with Files. Would you mind sharing what type of custom action you want to achieve? This may be doable with Make/Zapier.

Hi @Mindflows_Shanine,

I’m using our own Microsoft 365 SharePoint integration for monday.com, which is available on the marketplace:

monday.com

I’m just trying to debug some of the nuances of how monday automations support subitems for some fields, but not for others in recipe sentences.

Hi David. I certainly agree with you! monday should support all type of fields - this would be amazing if they’d be able to allow this.

@Billchenau thnx. submitted as #3993045

Terms & ConditionsCookie settingsAccessibility statement