The Actions workspace shows what a Payload does, in the order it does it. Select an Action on the left to configure it in the centre. Use the Jobs panel on the right to inspect previous runs.

Open the Payloads app, select Integrations, open an Integration and then open a Payload. Payloads upgraded to the Actions execution model use this workspace.

The expanded Actions panel shows the sequence, insertion points and required lifecycle Actions.

Follow the Actions from Start to End. Each card shows its name, type, position and output reference. Select the card to see the configuration for that step.

Start and End are sequence markers. They are not editable Actions and Start does not open an input editor. Dynamic Inputs are declared in the mappings that need them, then supplied when the Payload runs.

The Payload type supplies required Actions. For example, an Outbound Payload has HTTP Request followed by HTTP Response. A lock and Required label identify protected Actions. Configure these cards rather than trying to replace them through the New Action modal.

Plus buttons appear at positions where you can insert an optional Action. The type choices depend on the Payload type; saving also checks whether that Action is valid at the selected position. See Add and configure Actions.

The centre heading identifies the selected Action and shows its API Name and output reference. Check that heading before editing, especially when the sequence contains several Queries or Targets.

For an Outbound Payload, select HTTP Request to configure Request Settings, Body, Headers, Parameters and Modifiers. Select HTTP Response to define the response structure and response status policy. For an Inbound Payload, HTTP Request describes incoming data and HTTP Response defines what the caller receives.

Select the pencil beside a settings section to edit it. Save that section with its Save icon, or use Cancel to discard its unsaved changes. Body and field mappings have their own New, Import or Edit controls where applicable.

Query, Target, Flow and Payload Actions display the configuration for that particular step. Their own Edit and Delete controls operate on the selected Action. The icons in the Payload header operate on the whole Payload.

Request Settings are edited on HTTP Request, with separate Save and Cancel icons.

The Payload header provides Edit, Delete, Export and Run Payload icons. Hover over an icon to confirm its label. Run Payload is enabled only for supported Payload types.

Use Collapse Actions or Expand Actions to change the left panel. Use Expand Jobs or Collapse Jobs to change the right panel. Expanding one side panel collapses the other. Collapsing a panel gives the configuration editor more space; it does not change the sequence.

The Jobs panel shows recent execution history. Select a Job to inspect that run, use Refresh Jobs to refresh the list, or use View All to open the wider Job view.

Expanding Jobs exposes recent executions and collapses the Actions panel.

A Payload card describes the current configuration. A Job describes a particular execution. Changing a Payload does not prove that an earlier Job ran with the new settings.

For new runs, the Job Action timeline shows recorded outputs and execution details. Older Jobs can show reconstructed data labelled Recorded; those views do not establish original per-Action timings or execution order.

After saving a change, run a controlled test through the intended entry point and inspect its Job. Continue with Map data between Actions.