If you spend any time building integrations in Payloads, this is the page you will come back to most often. The Integrations page is the place where you can see what is already configured, start something new, and understand how each external system is organised inside your Salesforce org.

This guide is for Salesforce admins and builders who are setting up, reviewing, or maintaining integrations in Payloads.

When you first land on the Integrations page, think of it as your integration index. Each integration shown on screen represents one external system. Inside that integration, you can have multiple payloads, which are the actual connection points to that system. That means if you connect Salesforce to three different systems, you would usually expect to see three separate integration records here.

That one-record-per-system pattern is important because it keeps your configuration clean. Instead of credentials in one place, mappings in another, and transformation logic somewhere else, everything for that system is grouped together.

At the top-right of the page, you have two actions that cover the most common day-to-day needs.

New Integration is what you use when you are connecting a new external system and want to start from scratch.

Import from Backup is useful when the integration already exists somewhere else, for example in another org or environment, and you want to bring that configuration in rather than rebuild it manually.

Inside each integration, Payloads separates the setup into three practical areas that work together.

Payloads are the request and response definitions for the data moving between Salesforce and the external platform.

Credentials handle authentication, so Payloads can securely connect to the target system.

Transformations let you shape values as they move in or out, using formula-style logic similar to what many Salesforce admins already know.

A simple mental model is to treat each integration as a complete contract with one external system. If anything changes, whether it is authentication details, request shape, or data formatting, this is the place you return to. Over time, that makes reviews, troubleshooting, and handovers much easier because everything is kept in one clear context.

The Integrations page is the operational home for integration management in Payloads. It gives you one place to create integrations, import existing ones, and manage payloads, credentials, and transformations together for each connected system.