←

Add Delivery Target

General

Identity and connection parameters for this delivery target.

Human-readable name shown across the UI and in hook references.

Delivery protocol. Determines how data is pushed and which credentials are expected.

Inactive targets are skipped when hooks fire. Existing hooks remain attached.

Root URL or URI used as the base for all deliveries. Sub-paths defined on individual hooks are appended to this value.

Credentials

Stored encrypted at rest. Provide a JSON object containing any keys, tokens, or secrets required by the chosen protocol.

Arbitrary JSON. The expected keys depend on the protocol — see Protocol Help for examples.

Protocol Help

Quick reference for the supported delivery protocols.

Apprise

Notification gateway that supports Slack, Discord, email, and many others. Provide notification URIs (e.g. slack://, mailto://) in the Base URI field, or embed them in the credentials JSON.

Fsspec

File-system abstraction supporting S3, SFTP, FTP, SCP, Google Cloud Storage, and local paths. Credentials should map to the arguments expected by the underlying fsspec implementation.

Webhook

Standard HTTP POST. Credentials can contain custom request headers or bearer tokens under an Authorization key.