avanai SAP Connect OData Trigger icon

avanai SAP Connect OData Trigger

Receives SAP events via webhook (real-time notifications for OData changes)

avanai SAP Connect OData Trigger

AI-generated

Summary

Receive and process SAP OData events via a webhook to trigger n8n workflows in real-time based on configured filters and authentication methods.

Inputs

  • authentication — Choose the method to authenticate incoming webhook requests: None, HMAC Signature, Header Auth, or Query String token.
  • responseMode (required) — Select when to respond to the webhook request: immediately or after the workflow finishes.
  • responseCode (required) — Set the HTTP status code to return to SAP after receiving the webhook event.
  • eventFilter (required) — Define the filter to trigger the workflow on either all events, specific SAP entity types, or specific operations (Create, Update, Delete).
  • entityType — If filtering by entity type, specify one or more SAP entity types (comma-separated) to trigger on.
  • operationType — If filtering by operation, select which operation types—Create, Update, Delete—should trigger the workflow.
  • options — Additional options including custom JSON response body, enable/disable rate limiting with request limits, IP whitelist for allowed clients, parse SAP-specific date formats to ISO 8601, extract only changed fields from the event data, and payload format validation.

Output shape

a list of items each containing the received webhook payload along with extracted event information

The webhook receives POST requests from SAP OData notifications and outputs JSON data containing headers, parameters, query, the full webhook payload, and parsed event details. It supports filtering events by entity type or operation. Authentication of incoming requests is configurable (including HMAC signature verification). Rate limiting and IP whitelisting help prevent abuse. The node can respond immediately or wait until the workflow finishes before responding with customizable HTTP codes and response bodies.

Examples

Example 1: Trigger a workflow upon creation or update of SalesOrder entities in SAP

Set 'Event Filter' to 'Specific Entity Type' with 'SalesOrder'. Select operation types 'Create' and 'Update'. Use 'HMAC Signature' authentication with a shared secret to verify request authenticity. Enable rate limiting and optionally whitelist known SAP IPs.

Example 2: React to all SAP data change events without authentication

Set 'Event Filter' to 'All Events' and 'Authentication' to 'None' (not recommended). Respond immediately with HTTP status 200 and a simple JSON acknowledgment.

Links

Discussion