When a workflow’s trigger is “Edit record” (fires on an Edit Record form submission, bound to a Softr Database table), every downstream node that references the trigger’s fields (Branch/Filter conditions, variable pickers, etc.) displays raw field IDs (e.g. X6p4P, i273N) instead of the field’s human-readable name (e.g. “Posts To Create”, “Status”). This makes it very difficult to configure conditions correctly, since there’s no way to tell which ID corresponds to which field without cross-referencing the table schema outside of Studio.
By contrast, a workflow using the “Record updated” trigger (SOFTR_TABLES_RECORD_UPDATED, which requires you to explicitly select a database and table when configuring the trigger) resolves field IDs to their proper human-readable names everywhere downstream, exactly as expected.
Reproduction steps:
Step 1 - Create a workflow with an “Edit record” trigger bound to an Edit Record form/button on a page.
Step 2 - Add a Branch or Filter node downstream.
Step 3 - Try to build a condition referencing a field from the trigger’s record. The field picker shows only the raw field ID, not its name.
Confirmed reproducible on two separate Edit Record buttons (a duplicate created specifically to test this).
Why this matters: Unlike the “Record updated” trigger, “Edit record” is the only trigger type that can be assigned directly to a button/action in a Studio page, so anyone building button-triggered workflows against a Softr Database table is forced into this limitation with no workaround beyond manually maintaining an external field-ID reference key.
Related threads:
Workflow runs view shows field ID not field name - same underlying symptom in a different node type (Create Record in a loop)
Edit Record Action - On Form Submission Execute Workflow - Add Field Mapping Options - related gap in what the Edit Record trigger passes through