Automate Salesforce Webhooks in Make.com

Using make.com with Salesforce webhooks lets you trigger real-time workflows whenever data changes in your CRM, without constant polling or manual exports. This guide walks you step-by-step through the core webhook options Salesforce offers and shows how to connect them into scenarios.

Salesforce does not provide a single, simple “webhook” button. Instead, it offers several features that behave like webhooks and can all be connected to make.com:

• Flows with the Callout action
• Platform events
• Outbound messages via workflow rules

Each option is suited to different use cases. Below, you will learn how to choose the right approach and how to configure Salesforce so it can call the correct target URL in your scenario.

How Salesforce webhooks work with make.com

Before configuring anything, it is important to understand how Salesforce sends data and how make.com can receive it. In Salesforce, you always configure a process that reacts to a change in your data and then performs an HTTP callout to an external URL.

On the other side, your scenario listens for that incoming HTTP request. In make.com this is usually done with a webhook or a specialized trigger module, depending on which approach you choose in Salesforce.

In practice, all webhook-style integrations follow three basic steps:

1. Create or identify a trigger in Salesforce (flow, event, or workflow rule).
2. Configure an HTTP callout, outbound message, or event publication.
3. Set up a scenario in make.com to receive and process the incoming message.

Option 1: Use Salesforce flows with make.com

Record-triggered flows provide one of the most flexible ways to emulate webhooks. You can define exactly when the flow should run and what data should be sent to your scenario.

Create a record-triggered flow for make.com

To start, build a new flow that reacts whenever a record changes:

1. In Salesforce Setup, go to Flow and click New Flow.
2. Choose Record-Triggered Flow.
3. Select the object whose changes should trigger your automation, for example Opportunity or Case.
4. Define when the flow runs, such as When a record is created or updated.
5. Set entry conditions so the flow only launches when relevant fields or statuses change.

These steps ensure that only meaningful updates send data to your webhook receiver in make.com.

Add a callout to make.com from the flow

Once you have a trigger, you must send data to an external endpoint. In a record-triggered flow you can do this by adding a callout action.

1. Inside the flow canvas, click the + icon to add a new element.
2. Select Action and search for an HTTP callout option or a custom action you have defined for external services.
3. Configure the HTTP method (usually POST).
4. Paste the target URL that belongs to your webhook or HTTP module in your scenario.
5. Map the necessary fields from the triggering record into the request body or query parameters.

Save and activate the flow. From this point, every matching data change in Salesforce will push information directly into your scenario.

Option 2: Use Salesforce platform events with make.com

Platform events are designed for event-driven architectures. Instead of reacting to individual record changes with a flow, you publish events that describe what happened. These events can then be consumed by external systems.

This option is ideal when you need loose coupling between objects, complex event logic, or when multiple subscribers may need the same event.

Define a platform event for make.com

To prepare Salesforce for this approach:

1. In Setup, search for Platform Events.
2. Click New Platform Event.
3. Provide a label and API name that clearly describe the event, for example Invoice_Updated.
4. Add custom fields that represent the data your scenario will need, such as IDs, amounts, or statuses.
5. Save the event definition.

After this, you can create processes or flows that publish the event whenever certain conditions are met inside Salesforce.

Publish events and connect them to make.com

You have multiple options for publishing the event:

• Flows that include a Publish Platform Event element.
• Apex triggers that publish events based on changes.
• Process Builder (in older setups) configured to publish an event.

Once events are published, configure a scenario to subscribe to them. The scenario will receive each event as it is fired and can run any downstream automation you require, such as syncing records, sending notifications, or calling additional APIs.

Option 3: Use outbound messages with make.com

Outbound messages are another traditional method to push data out of Salesforce in near real time. They are typically used with workflow rules and can send a SOAP message containing field values to a specified endpoint.

Configure an outbound message in Salesforce

To configure this option:

1. Open Setup and navigate to Workflow Rules (or the equivalent automation feature in your edition).
2. Create a new workflow rule on the object you care about.
3. Define rule criteria to decide when the outbound message should be sent.
4. Add a new Outbound Message as an action.
5. Enter the external endpoint URL where Salesforce will send the SOAP message.
6. Pick the fields that should be included in the message body.

After activating the workflow rule, any matching record change will automatically send data to your chosen endpoint.

Receive outbound messages in make.com

To make use of outbound messages in your automation pipeline, create a scenario that can accept SOAP content. The scenario must expose an endpoint capable of handling the structure Salesforce sends and then transform that message into the data format your modules expect.

This method is especially useful in legacy environments or when you must integrate with systems that already rely on SOAP. However, flows and platform events are often more flexible for modern web integrations.

Choosing the best Salesforce webhook option for make.com

Each of the three main approaches has its strengths. You should choose based on your data model, integration style, and any existing automation already set up in Salesforce.

• Flows with callouts: Best for direct, simple webhook-like behavior where a record change should immediately send a payload to your scenario.
• Platform events: Best when you need scalable, event-driven architectures and multiple subscribers, or when you want to decouple publishers and consumers.
• Outbound messages: Suitable for environments that already use workflow rules and SOAP-based integrations, or when you must maintain compatibility with older systems.

In all cases, design your scenario to validate incoming payloads, handle errors gracefully, and log activity for troubleshooting. These practices will keep your integration stable and easier to maintain.

Connect Salesforce webhooks to make.com scenarios

Once your Salesforce side is configured, focus on the scenario structure. Most implementations follow a similar pattern:

1. Create a dedicated webhook or HTTP-trigger module as the first step.
2. Run a test from Salesforce to capture a sample payload.
3. Map incoming fields to subsequent modules, such as CRM updates, notifications, or data transformations.
4. Add error handling, like routers and filters, to manage failed requests.
5. Turn on the scenario and test again with real Salesforce data.

Careful testing on both sides ensures that fields align correctly and that all required information reaches your target systems.

Additional resources for make.com integrations

To deepen your understanding of Salesforce webhooks and how they interact with automation platforms, review the original guide on the official blog: Salesforce webhooks article. It provides in-depth explanations of each approach along with conceptual diagrams.

If you need help designing advanced scenarios, optimizing complex automations, or planning a broader integration strategy around make.com, you can also work with specialized consultants such as Consultevo.

By choosing the right Salesforce feature, defining clear trigger conditions, and building well-structured scenarios, you can reliably push real-time data from your CRM to any connected application and fully leverage the power of make.com in your automation stack.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help