The Payload type tells Payloads what kind of integration step the Payload represents.

It controls which configuration sections appear, which runtime behaviour is available, and what Payloads expects to do when the Payload runs.

If you are creating your first Payload, start with Create your first Payload.

The New Payload modal shows the current starting types: Outbound, Inbound, Email Handler, and Credential Payload.

Most Payload type decisions start with one question: who starts the interaction?

If Salesforce starts the interaction, choose Outbound.

If another system starts the interaction over HTTP, choose Inbound.

If the interaction starts with an email message, choose Email Handler.

If the Payload exists to maintain authentication, it will usually be a Credential Payload created automatically for a Bearer Token Credential.

Use Outbound when Salesforce sends a request to another system.

This type is a good fit when you need to:

Common examples include creating a checkout session, notifying a fulfilment system, creating a customer in an external platform, or sending an order update.

An Outbound Payload can be simple or detailed. If the response body is not important, treat the response status as the delivery result. If the response contains data Salesforce needs, model the Response body and Data Targets.

For setup steps, see Configure an Outbound Payload.

For a simple webhook-style example, see Configure an outbound webhook.

Use Inbound when another system sends a request to Payloads.

This type is a good fit when you need to:

Common examples include receiving payment events, accepting order updates, returning payment status, or exposing a small Salesforce-backed response to a portal.

An Inbound Payload has a Request side and a Response side. Use Data Targets when the request should write data into Salesforce. Use Data Queries and Response Body elements when the caller should receive Salesforce data back.

For write-focused setup steps, see Configure an Inbound Payload that writes to Salesforce.

For read-focused setup steps, see Configure an Inbound Payload that returns Salesforce data.

Use Email Handler when the inbound event is an email rather than an HTTP request.

This type is a good fit when you need to:

Common examples include processing billing emails, supplier notifications, support updates, or mailbox-based operational messages.

Email Handler Payloads usually need Email Contents, Data Targets, and at least one Email Service record.

For setup steps, see Configure an Email Handler Payload.

Use Credential Payload when the Payload exists to maintain authentication for another Payload.

You should not normally create this type manually. Payloads creates Credential Payloads automatically when you create a Bearer Token Credential that needs a token refresh flow.

This type is a good fit when you need to:

Common examples include OAuth token refresh flows.

For setup steps, see Configure a Credential Payload.

Choose Outbound when Salesforce sends a request.

Choose Inbound when another system calls Payloads over HTTP.

Choose Email Handler when the inbound message is an email.

Use the generated Credential Payload when the Payload supports authentication rather than a business process.

Before you save the Payload, check that:

If the visible sections do not match what you expected, check the Payload type first. The type is what determines which configuration areas Payloads shows.