Skip to main content

Integration Page

The Integration page is where you manage an external system end to end in Payloads, including its payloads (connection points), credentials, transformations, and recent job history.

Updated over 2 months ago

The Integration page is where you manage one integration end to end. If the Integrations tab is your index, this page is the working area for a specific external system.

Who this guide is for

This guide is for Salesforce admins and solution builders who need to review, maintain, or extend an integration in Payloads.

What this page does

Each integration represents one external system. Inside that integration, you define the payloads that act as the actual connection points, plus the credentials and transformations those payloads rely on.

This gives you one place to understand how the system is configured and one place to make changes safely.

How the page is structured

At the top of the page, you will see the integration name and the actions for Edit, Delete, and Jobs.

The Jobs action opens a modal with recent execution history for that integration. It includes runs across all payloads in the integration. If you need deeper analysis, use

View All in the modal to open the full Jobs tab.

Below the header, the page is split into three sections: Payloads, Credentials, and Transformations.

Payloads

Payloads are the operational connection points between Salesforce and the external system. They define what gets sent, what gets received, and how the exchange is handled.

In day-to-day work, this is usually where most integration changes happen.

Credentials

Credentials control how Payloads authenticates to the target system.

Because different platforms require different authentication patterns, Payloads supports multiple credential types so you can match the setup required by the system you are integrating with.

Transformations

Transformations let you adjust values at runtime using formula-style syntax.

They are applied while data is moving through the integration, outbound from Salesforce or inbound back into Salesforce.

A key detail is that transformations do not rewrite the underlying Salesforce source value. They shape the value used in-flight.

Recommended working model

Treat each integration as the full contract with one external system.

When behaviour needs to change, review the relevant payload first, confirm credentials are valid, then adjust transformations if data formatting needs to change.

This keeps maintenance predictable and makes handover easier for both admins and developers.

Summary

The Integration page is the operational centre for one external system in Payloads. It brings payload definitions, authentication setup, transformation logic, and run history into one place so changes are easier to make and easier to validate.

Did this answer your question?