How senders prove they are allowed to post. Token Header: a shared token in a header (or Authorization: Bearer). HMAC SHA256 Signature: the sender signs the raw body with the secret. None: anyone who knows the webhook URL can post.

Header carrying the token or signature. Defaults to X-Webhook-Token (Token Header) or X-Signature-256 (HMAC SHA256 Signature, value sha256=<hex> or <hex>).

Shared token or HMAC signing secret. Required unless Authentication is None.

After storing a delivery, start the enabled sequences whose trigger is this webhook.

Optional event name sent when starting sequences. Only sequences with no event filter or this event start.

When a sequence is still running, try starting it again after this many seconds so new deliveries are picked up.

Credentials to use to access the MySQL database.

Target table name, in schema.table format, where the deliveries will be stored.

Automatically create the Target Table, if it does not exist, otherwise end the Task.

Select a Shared Config with the webhook payload property to MySQL column mappings (API Property is a dot path such as message.from.email) and MySQL column definitions. With Autodetect, top-level payload properties become columns. The URL's engine_id is available as the property nnd_engine_id.

With Autodetect Column Mappings, add a column when a delivery has a new top-level property.

Optional column that identifies a delivery (e.g. message_id). A delivery whose value is already in the table is acknowledged but not stored again. Senders retry on timeouts, so this is recommended.

Acknowledge deliveries that cannot be stored instead of failing them (failed deliveries return HTTP 500 so the sender retries).

Optional name of the table, in schema.table format, where ignored deliveries will be stored.