Publishing a step

Make a completed step available in automations and account for the constraints when changing it.

Before publishing, create the step, prepare a configuration form if needed, and implement step execution.

Publish and test the step

When the embedded page and webhook are ready, return to the list. In the required step row, the Not published label shows the current state. Open the ⋯ actions menu and select Publish.

The published step appears in the step catalog for projects where the application is installed and active. Its row in the Developer section shows the name and technical name, parameter and result counts, continuation mode, and status. To update a step, open its row or select Edit in the actions menu.

Immediately after publication, add the step to an automation in a test project. Check each enabled automation type, the configuration form, every output, and the selected completion mode. Verify that the webhook accepts nullable context, response mode completes within 60 seconds, callbacks arrive within 7 days, and a retry with the same idempotency_key does not duplicate the external change.

What you can change after publication

A step is edited without creating a separate version. After the first publication, Senler blocks incompatible contract changes so saved automations continue to work. Changes to the execution URL apply to the published step, so verify backward compatibility before saving.

You can update names, descriptions, the webhook URL, the icon, the completion mode, and the configuration mode; add optional fields; and enable an additional automation type. New nodes receive the current completion mode, while nodes already added to graphs keep the previous option.

You cannot change the technical name or continuation mode, remove an already enabled automation type, change the type of a published field, add a new required input parameter, or assign a published branch's technical key to another branch.

Saved nodes use the current configuration mode when opened. Switching to an embedded page alone does not delete parameters, values, or result bindings: they are passed to the application form through reserved configuration fields but are no longer rendered as separate Senler fields. If you remove a parameter, result, or fixed output from the step, the Cabinet marks it as obsolete in a saved node and requires the user to remove it explicitly.

You can disable a published step. It disappears from the catalog for new nodes but is not removed from saved graphs. A disabled step can be published again. Only a step that has never been published can be deleted completely.