Skip to main content
Automations deliver to the project’s contact points, the same destinations Alert Rules use. You create contact points once and reuse them across automations.

Create a Contact Point

1

Open Contact points

Go to Settings → Contact points and click Create Contact Point.
2

Name it and pick an integration

Enter a Name, such as Engineering Team Email, and choose the Integration: Email, Slack, Webhook, or GitHub dispatch.
3

Fill in the settings

Enter the fields for the integration you chose. See the sections below.
4

Save and send a test

Save the contact point, then click the test action on its row. Netra sends a test event and shows whether the destination accepted it. You can send one test per contact point every 10 seconds.
Tokens and secrets are encrypted at rest. After you save, Netra shows only the last four characters.

Email

Each event arrives as an email with the subject [Netra] <event title>, and a summary of the event details. Test run and red team events also include a link back to Netra.

Slack

Choose one of two integration methods: Each event arrives as a Slack message with a header and the event details. Test run and red team events also include a View in Netra link.

Webhook

Netra sends a JSON POST to your HTTPS endpoint for every event. Your endpoint must:
  • Be reachable over the public internet. Private and internal addresses are rejected.
  • Respond within 10 seconds. Redirects are not followed.
  • Return a 2xx status to mark the delivery as Delivered.

Verify the Signature

When you set a Secret, each request includes an x-netra-signature header:
v1 is the hex-encoded HMAC-SHA256 of <t>.<raw request body>, keyed with your secret. To verify a request, rebuild the HMAC over the raw body (before parsing JSON), compare it in constant time, and reject old timestamps to block replays.
Compute the signature over the exact bytes you received. Parsing and re-serializing the JSON changes the body and the signature will not match.

GitHub Dispatch

A GitHub dispatch contact point triggers a repository_dispatch event, so you can run a GitHub Actions workflow whenever an automation fires. For example, you can run regression tests when a new prompt version is published. The workflow receives the event payload in github.event.client_payload:
.github/workflows/netra.yml
GitHub limits client_payload to 64 KB. If an event is larger, Netra replaces the largest fields in data with a [TRUNCATED: ...] marker.

Payload Format

Webhook and GitHub dispatch destinations receive the raw event. Email and Slack receive a formatted message built from the same data.

Event Data by Source

url links to the item in Netra. In evaluation_completed, an evaluator counts as passed only if it passed on every item. failedItems counts every item that did not pass, including items that failed to run. result is a one-line summary, such as 4 of 5 evaluators passed, 18 of 20 items passed.

Test Events

The test action on a contact point sends an event with type set to test and action set to ping. Handle or ignore it in your endpoint.

See Also

Create an Automation

Set up triggers, conditions, and destinations

Alert Rules

Get notified when metrics cross a threshold
Last modified on November 11, 2026