Salla Webhooks Flow

Stand up a reliable webhook integration — build the server, subscribe to events, verify every delivery, respond fast, and stay idempotent. Work through the steps in order; complete each gate before moving on. Step 2 performs actions with the Salla Partners MCP; the server and verification are runtime code.

Prefer an App Function when the event has one. If a trigger exists in salla-app-functions, use it instead of a webhook — it runs in Salla's sandbox (no signature to verify), gets context.settings, calls the Salla API with built-in auth, and can run synchronously on action events (e.g. shipment.creating) where the return value shapes the operation. Use a webhook only when no App Function trigger covers the event.

Tools & MCPs

Confirm live event payload schemas in the webhooks reference (https://docs.salla.dev/421119m0.md) before coding; never assume a shape. The Salla Partners MCP performs actions: