Use the New Action modal to add a Query, Target, Flow or another Payload at a specific point in the sequence. Create the data-producing Action before configuring Actions that consume its output.

Open the Payload in the Actions workspace. Decide what the new step needs to read and what later steps should receive from it.

For a Flow Action, prepare an active autolaunched Flow. For a Payload Action, prepare an eligible Outbound Payload in the same Integration.

The type buttons are:

The type choices depend on the Payload type. Email Handler Payloads offer Query and Target. Required HTTP, Email and CSV Import Actions are supplied by the Payload type and are not options in this modal.

The selected type must still be valid at the insertion point. For example, an Outbound Target must follow HTTP Response even if Target appears in the type chooser at an earlier plus button. Saving validates the sequence and dependencies.

Choose an Action type, then configure it for the selected insertion point.

Selecting a type opens its configuration editor. It does not create a saved Action immediately.

For Query, enter the query name, select the Salesforce object, then configure limits, sorting, relationships and filters. Map runtime filter values from available data where needed. See Configure Data Queries.

For Target, choose the Salesforce object, operation and single-record or multiple-record behaviour. For multiple records, select the collection in Records From. Save the Target, then add its destination field mappings from the selected Target detail. See Configure Data Targets.

For Flow, select the Flow, name the Action, map its supported inputs and select the outputs to publish. See Run a Flow from a Payload.

For Payload, select the child Payload, name the Action, map its Dynamic Inputs and add named outputs for later Actions. See Call another Payload as an Action.

Use Back to return to type selection if you chose the wrong type. Use the modal close control to abandon creation. Select Save when the configuration is complete, then confirm the new card appears at the intended position.

New Target configures the object, operation and record count; field mappings are added after saving it.

Select the saved card, then use Edit in that Action's detail section. Make the changes and save them. The Payload header's Edit icon edits the Payload itself.

For the v1.53 issue where a saved child Payload input editor shows No actions available, follow the guidance in Call another Payload as an Action.

Use Delete in the selected Action's detail section to remove an optional Action. If another mapping depends on that Action or one of its outputs, resolve the dependency before deleting it. Do not remove a producer while leaving later Actions expecting its data.

Version 1.53 does not provide drag-and-drop or a Move Action control. Choose the insertion point carefully and review dependencies before replacing a step at another position.

Confirm the new Action's name, position and output. Open the next consuming Action and check that the new producer appears in its Payload Data choices. Test the sequence and inspect both Actions on the Job timeline.

For placement restrictions and transaction behaviour, see Understand Action order and execution limits.