How to set up Salesforce for outbound message and Make for Webhook

How To
,
1

Hello all,

Make support was unable to resolve a communications issue with my current solution, so I’m reaching out for a best practices approach.

My goal is to send a remote message with key fields from the User object to the Make webhook address.

The webhook should capture this incoming data and make it available for further processing.

Could someone please direct me with a fully self-contained tutorial on doing this or provide some guidance to help me design a solution that doesn’t return a 403 error when the message is sent?

Original discussion is here: 403 forbidden when sending outbound message to webhook - #5 by RevOps1

Thanks,
Brandt

3

Hey Brandt.

If you’re triggering a Salesforce Outbound Message, then you don’t need to configure Make as a Connected App within Salesforce.

Instead, you just need the right processing in your Make scenario.

This comment of mine on an old topic has all the details.

2 Likes
4

Hi David,

Thank you for the resource.

My scenario is the Webhook and Webhook response, as described by the post you linked to.
The webhook is configured using Salesforce SOAP as the API. I copied the webhook URL to the Callback URL field in the SFDC outbound message. When I test this, I get further than before, as the Make nodes both report success. However, Salesforce reports “Version Mismatch” from the response. SFDC uses API version 59.0. Could this be mismatched against the API version that Make is using? If so, is there a way to enforce a specific API version in the response?

My scenario can be viewed here: https://us1.make.com/397862/scenarios/1723943/edit

Thanks,
Brandt

5

Hello there @RevOps1 :wave:

I’m just quickly jumping in to let you know that we cannot access your scenario via the url :arrow_down:


:bulb: Quick tip: For the community to be able to best assist, it’s a good idea to

  • Give a detailed explanation of what you’re trying to achieve
  • Mention any steps you’ve tried so far
  • Include screenshots of
    • your scenario flow and setup (functions, mappings, variables, etc.)
    • module configurations and outputs
    • any error messages you are getting
  • When posting screenshots, remember to exclude all sensitive data
1 Like
6

Ah, very good point Michaela.

My response node looks like this:

Make Response
Make Response898×1042 81.3 KB

There are no errors in the scenario when I run it once and trigger it from Salesforce.

Beside this, is there anything else I can show here that would be useful?

2 Likes
7

Hi Brandt.

I think you’re trying to initiate the Outbound Message from a Salesforce Connected App. That’s not the recommended mechanism.

Instead, you just need to create an Outbound Message from a Salesforce Flow or Salesforce Workflow.

There’s no Callback URL parameter on the Outbound Message configuration panel - only an Endpoint URL.

2 Likes
8

Hi David,
I misspoke. This URL is indeed the Endpoint URL. The connected app is no longer involved. When the outbound message is triggered and the scenario runs, the scenario completes without errors, and the Outbound Message Delivery Status in Salesforce is “Version Mismatch”. Notes that I have found on line indicate that this is an API version issue.
Thanks,
Brandt

9

Ah, great.

Can you provide a screenshot of the Outbound Messages Delivery Status panel in Salesforce?

2 Likes
10

Sorry for the delay. I just saw your response. Screenshot below

Screenshot 2024-01-17 at 11.12.46 AM
Screenshot 2024-01-17 at 11.12.46 AM3048×746 189 KB

11

It would help if Salesforce identified what the version mismatch relates to … XML, or an XML name space.

One other thing you could try is to add the following line at the beginning of the SOAP response body to ensure that it’s reading it as XML (I’ve never seen this needed before though!):

<?xml version="1.0" encoding="UTF-8"?>

If that doesn’t help, I’d suggest reaching out to Salesforce support to ask them exactly what the version mismatch relates to.

2 Likes
12

Thanks David. I tried that, and it didn’t help. I’ll go out on the Salesforce developers forum and see whether anyone has ideas.