Hi team — reposting here as suggested in the main migration thread.
Bug report: migrated text input field cannot be configured in templates
Setup (minimal legacy recipe)
-
Trigger: When an item is created (standard built-in trigger)
-
Action: very simple custom action that sends a text value to our backend
-
In the original legacy action, the input was a basic free-text field
Steps to reproduce
-
Migrate the legacy sentence-builder integration using the migration wizard.
-
Open the newly created Automation Template.
-
Notice that the trigger is selected correctly, but the action is not pre-selected (empty).
-
Manually select the migrated Action block.
-
Check the migrated input field inside the action block.
Actual behavior
-
The migrated text input becomes a Single Line Text typed field.
-
In the template builder UI it cannot be configured (shows “No options available” and does not allow entering a static value).
-
Even after changing the field type to plain String, it still does not accept manual input when creating an automation from the template.
-
A newly added String field created manually works correctly.
Expected behavior
-
Migrated free-text inputs should remain configurable as simple text fields in the template builder.
-
The migrated action should be automatically selected in the migrated Automation Template.
-
Migrated fields should behave the same way as equivalent fields created manually.
Is this a known issue with migrated field representations in templates?
As a workaround we can recreate the fields manually, but how will manual changes (adding/removing fields in the new blocks) affect the future legacy→workflow upgrade once legacy execution is deprecated?
