Skip to main content

Configuration Management: Dependencies

  • August 28, 2026
  • 1 reply
  • 26 views
mark-theotcentre
Forum|alt.badge.img

In it’s present form, Pipefy cannot be used as the principal platform for process/workflow implementation at scale for operationally critical processes.

There are insufficient and inadequate safeguards identifying and protecting interdependencies between components, for example;

  • conditional references to phases, fields, field contents
  • automation references to phases, fields, field contents

Delete a field referenced in an automation and the automation fails silently. Before deleting a field, try finding automation references to that field. At scale and for operationally critical processes, this is a critical vulnerability.

    1 reply

    Alan dOliveira
    Pipefy Staff
    Forum|alt.badge.img+1

    Hi ​@mark-theotcentre , thanks for raising this  it’s a real governance concern for pipes that run operationally critical work.

    You’re right that deleting a field used in an automation can break the rule, and that this is risky at scale if the only way to find references is to inspect automations one by one.

    There is a partial safeguard today: Field Dependencies. In the start form or phase form editor, open the field’s three-dot menu (or Field Dependencies in the field details) to see automations and conditionals that use that field.

    Help Center:
     https://help.pipefy.com/en/articles/10844068-field-dependencies

     

    That view is still limited. It is documented as in testing, and it does not yet list every usage (connections, email templates, interfaces, and dynamic fields may be missing). It also does not block the delete. So it helps you look before you change a field; it is not full configuration management.

     

    Safer operational practice right now:

    • Check Field Dependencies before any destructive change
    • Archive the field instead of deleting it, so history and references stay visible
       https://help.pipefy.com/en/articles/12736688-archive-a-field
    • If a rule already broke, the deleted field should appear in red in the automation editor; Card Timeline also surfaces failed automation runs

    The remaining gap is the one you described: no hard protection on delete, incomplete coverage (especially phases and field values/options), and no single dependency map across a large process. That’s fair product feedback.

    Alan d'Oliveira - Support Team
      Terms & ConditionsAccessibility statement