Receive updates in Salesforce through Webhook

Question

I would like Salesforce to receive updates from a webhook. I have found that I need to set up a site and build some apex code for this.  Is there any way to do this through flow instead or easily get the data into flow, so I can handle the mapping in there?    I have found Streamscript which I need to investigate more. Is this the best approach? Does anyone have experience with this?

Iain Clements ☁ · Accepted Answer

Hi  @Karoline Sass https://trailblazers.salesforce.com/profileView?u=0053000000A7PLPAA3     That Steamscript solution looks really powerful and I believe would suit your use case based on the overview. If you have multiple integrations to setup, having a standard approach in Steamscript could be another benefit.    Or, to build everything yourself though I would recommend a new custom object (to store the input from the external service), the webhook and a small piece of code to save the incoming data into that object - I found one example here using Account -  Webhooks in Salesforce - How to Setup and Configure for Integration | LWC Stack )    When you have the data saved you can use standard flow record-triggered actions to take that data and do more useful things with it. I would recommend you split the incoming data within the webhook code - so if it is 4 pieces of information, have 4 fields on the custom/temporary object and store each part separately - as it is slightly easier to parse JSON within the Apex snippet than within Flow at present (without using something like Steamscript)    Good luck    Iain

Hannah Recker · Answer

Hopefully Steamscript is working for you!    As you saw, Salesforce Flow can’t receive an inbound webhook by itself. You need either (a) an HTTP endpoint you host in Salesforce (Apex REST exposed via Sites/Experience Cloud) or (b) an external listener/middleware that catches the webhook and then talks to Salesforce.    Good patterns that keep most of the logic in Flow: Apex REST “shim” → Autolaunched Flow Create a lightweight @RestResource Apex class to accept the POST. In the Apex handler, do minimal validation/parse JSON, then invoke an  Autolaunched Flow  (or create/update records so a  Record-Triggered Flow  runs). Pros: stays inside Salesforce, full control. Cons: tiny Apex needed; you must secure the endpoint (OAuth/JWT/API key, IP allowlist, etc.). Middleware webhook → Platform Event → Flow Use something like Make/n8n/Zapier/AWS API Gateway+Lambda to receive the webhook. From middleware,  publish a Platform Event  (or call REST/Bulk upserts). Build a  Platform-Event-Triggered Flow  to map and process. Pros: no Apex, great for retries/throttling/format transforms. Cons: adds an external component. Notes: “External Services” and Flow’s HTTP Callout are  outbound , not inbound. Streamscript/other gateway tools can work, but they’re essentially the middleware approach above. If “real-time webhook” isn’t a hard requirement and you just need the data landing in Salesforce reliably, a low-lift alternative is to land the payloads in a Google Sheet or Excel spreadsheet (sounds like your data might already be in a spreadsheet to begin with), then use  Coefficient from Salesforce AppExchange  to  write them into Salesforce  on a schedule (or on-demand).    Coefficient gives you a 2-way sync between Sheets/Excel and Salesforce, so you can map/clean in the sheet and upsert to SF without building Apex. It’s a simple way to finish the workflow if you’d rather avoid maintaining an HTTP endpoint.

Receive updates in Salesforce through Webhook

Flow

Verwandte Lerninhalte

Weitere Hilfe