Replacing an Unavailable Action

Replace an unavailable Step action, remap its inputs and outputs, and verify the full automation route. Check the account, resources, and downstream results before returning the automation to service.

At a glanceVerified in app · Oct 30, 2026

Use it to: Replace an unsupported or deprecated app action, remap downstream {{ N.field }} references, and verify the updated route
Find it: Canvas App drawer and Step Executions tab
Cost: Real test runs in Draft or Live consume Step credits
Instead: Reconnecting on the Connections page (when the action is supported and only account authorization expired)

What needs attention?	Next step
The action is unavailable	Follow the replacement procedure below. Reconnecting an account does not restore an unsupported action.
The account needs authorization	Ask its owner to follow Reconnecting.
The trigger is unavailable	Choose a supported trigger for the required event, or contact support. Custom API request is an action, not an event source.

Replace and Verify

Record existing StepChoose replacementValidate and remapTest full route

Real action tests and automation runs, including in Draft, consume credits and can change external data or incur provider charges. Use test accounts and safe destinations. Check the connected app before repeating an uncertain write.

Record the existing Step’s work

Note what the Step reads or changes, its account and target resources, and every later Step that references its output. Keep its settings open while preparing the replacement, and coordinate changes to a live automation with its owner.

Choose a supported replacement

Check the app’s available actions for the required operation; similar names do not guarantee identical inputs or outputs. If no pre-built action fits, use the app’s Custom API request where available, or contact support with the app, task, and automation link.

Validate inputs and remap outputs

Select the intended account and recheck resource selections, required fields, and upstream references. Run a controlled read check first, inspect the output in Executions, and update every downstream Step reference to match the returned fields.

Test the complete route

Run the intended automation route with controlled input and safe downstream destinations. Run with test data only replays saved output; for automatic triggers, also complete the activation checks.

Verify it works

Run: Add the replacement Step, map its inputs, delete the unavailable Step, and click Run step
You should see: The replacement Step passes in Test & Debug and downstream references resolve to the new Step number.

What’s Next?

Testing & Debugging: choose the right test and inspect its results.
Managing Connections: restore account access and check dependents.