Install Payloads, assign access and verify its services before running integrations. For v1.53, also verify that existing Payloads migrated to the Actions execution model.

Use the package installation link supplied by Payloads. Open the Payloads app from the App Launcher and assign Payloads Admin to the users who build and support integrations.

Check the business-object access needed by Queries, Targets and Flows as well as the package permissions. For public inbound endpoints, review the Site Guest User separately. See Set up permissions and access.

Open Billing and start or refresh the subscription service as appropriate. Confirm a recent successful verification. If the subscription service stops or fails for any reason, Payloads stops operating after the seven-day recovery window expires.

Check Batch Engine and Job cleanup status if those services are used. CSV imports started from Flow need an authenticated Salesforce file connection; see Set up the Salesforce file connection.

Test the upgrade in a sandbox before production. Preserve an export of important configuration and record representative request/response outcomes before changing the package.

After installation:

The post-install migration converts legacy configuration to Actions. A visible Payload record alone does not prove migration completed correctly. If Actions or linked configuration are missing, use Check the upgrade to Actions and troubleshoot migration.

Do not rebuild or rerun production configuration blindly to clear a migration symptom. Preserve the affected records and error details for diagnosis.

Payload-level configuration now lives in Action detail panels. Credential, Endpoint, Method, Timeout and request content settings are under HTTP Request; response content and status policy are under HTTP Response.

Validate entry-point restrictions as well as visual configuration. Inbound firing mode determines whether the caller receives a final result or an early acknowledgement. General Flow Batchable execution rejects Actions Payloads with Target or Flow Actions. CSV has its own asynchronous runtime.

See Navigate the Actions workspace and Understand Action order and execution limits.

Use Export to obtain a .payloads file and Import in the destination Integration to apply it. API Names identify matching records; importing can replace existing child configuration.

The on-screen export preview redacts Credential secrets, but copied or downloaded exports can contain their original values. Store those files securely.

Before importing, prepare the destination’s objects and fields, Flow definitions, Sites, certificates and file-connection authentication. Review all referenced Action dependencies and test after import.

For the complete process and v1.53 dependency checks, see Export and import Integrations with Actions.

Open a genuine new Job and inspect the Action timeline. Confirm the request, response, queried data, Target writes and any Flow or child Payload outputs. Check unsuccessful cases as well as the happy path.

Only treat the upgrade as complete when the configuration and runtime outcomes match the integration contract.