How does one go about using Dependencies in Custom Recipes?

Platform discussions monday dev
, ,
1

I am working on an automation app that I would like to be available as a custom recipe option.

The problem I am running into is whenever I add any dependencies to my Field Types (which I believe is the only way to get this to work), the option for the workflow block to be published as a custom recipe gets greyed out.

I am using the dependency to pull data on the boardId, and columnId for a dropdown column so I can display, and select the dropdown column options in my automation.

I don’t see anyway of achieving this without using a Field Type with dependencies.

Any help/direction would be greatly appreciated!

Thanks!!

2

Hi MondayAdmin, I believe this is by design. Workflow blocks that use dependent fields (e.g., column with dependencies on boardId, dropdown options that depend on columnId) can’t be published as Custom Automations recipes, so the toggle is greyed out.

Ideas to try?

  • If you must show and pick dropdown options at config time: publish it as a regular Integration recipe (under your app’s recipes). Dependencies are fine there.

  • If you want it available in the Custom Automations builder: remove dependency-based fields and use Dynamic Mapping.

    • In your action, use a mapping field with allowedColumnTypes: [“dropdown”].

    • At run time, use the mapping context (boardId, itemId, columnId) and GraphQL to read the dropdown column settings_str to get labels/options.

    • If you need a specific label choice, add a simple text/number field for the label or value to match, rather than a dependent selector.

Pattern examples:

  • Custom Automations–compatible action:

    • input field: type “mapping”, allowedColumnTypes [“dropdown”] (no dependencies)

    • optional: a text field “Label to match”

  • Regular recipe (not Custom Automations):

    • fields with dependencies: board → column (dropdown) → option list

So: use a regular recipe if you need dependency-driven pickers; use Dynamic Mapping (no dependencies) if you need the block inside Custom Automations.

Let me know if that’s help.

3

In monday.com custom recipes, using dependencies in Field Types currently prevents publishing the workflow block as a custom recipe — this is a known limitation. Dependencies dynamically pull board or column data (e.g., dropdown options), but custom recipes require static field definitions. To work around this, use static or predefined fields and handle dynamic data retrieval inside your app’s execution logic or custom trigger/action endpoint instead of through dependencies. Essentially, keep the recipe definition static, and use runtime API calls in your backend to fetch board-specific data after the recipe is created.