Targets

A Target is a delivery destination within Event Channels. Targets define where matching events are sent. A single target can be attached to multiple subscriptions, so you can reuse one Slack channel or webhook endpoint across different event routing rules.

Target Types

Email targets deliver batched event summaries to a list of users on your site. The batch interval is configurable between 10 minutes and 24 hours. Recipients do not need to be Site Administrators.

Webhook targets deliver a JSON event payload to an HTTPS URL for each matching event. Custom request headers are supported. Webhook targets can optionally use Dedicated IPs, which routes deliveries through a fixed set of IP addresses you can allowlist in your firewall or receiving system.

Slack Webhook targets deliver a human-readable message for each matching event. The message content is generated from the event title, summary, and key fields.

Teams Webhook targets deliver a human-readable message for each matching event using the same generated content as Slack.

Amazon SNS targets publish event payloads to an SNS topic. The target requires a topic ARN and AWS credentials. For security, the secret access key is not retrievable after saving. Record it before saving the target.

Google Cloud Pub/Sub targets publish event payloads to a Pub/Sub topic. The target requires a project ID, topic ID, and Google credentials. For security, the private key inside the credentials is not retrievable after saving. Record it before saving the target.

Delivery Batching

Email targets batch events together and deliver a summary on a configurable schedule between 10 minutes and 24 hours. This is separate from the admin email alert batching that uses exponential backoff. See Event Channels vs. Admin Email Preferences for the distinction.

All other target types (webhook, Slack, Teams, SNS, Pub/Sub) deliver one payload per event as events occur.