Webhooks

Webhooks let Ternary deliver notifications to other tools, in addition to email and Slack. For example, when a budget alert fires, Ternary sends the alert to each Webhook subscribed to it. This can start a Claude routine, a ChatGPT workspace agent, or a workflow in a tool such as Zapier, Make or Power Automate.

Who can set up and use Webhooks?

An admin creates a Webhook once. After that, anyone who can set up alert notifications can send alerts to it, alongside email recipients and Slack channels. To attach a webhook to a budget and see example workflows, see Automate budget follow-up with Ternary Webhooks.

Which Webhooks are available?

What do you need before you start?

• An admin role in Ternary.
• An endpoint URL from the tool that will receive alerts, and a token for it. A token is required for Claude Routine and OpenAI Workspace Agent Webhooks, and optional for Custom HTTPS. Any token must be at least 16 characters. Step 1 explains where to find them for each kind.

How is a Webhook configured in Ternary?

Step 1: Get the endpoint URL and token

Create the destination in the receiving tool first, then copy its endpoint URL and token.

Claude Routine

1. In claude.ai, go to Code › Routines and open your routine, or select New routine to create one.
2. Make sure the routine has the Ternary connector, so it can look up the alert in Ternary.
3. Edit the routine, select Add another trigger › API, then select Generate token.
4. Copy the fire URL and the token. The token is shown only once. The URL has the form https://api.anthropic.com/v1/claude_code/routines/trig_…/fire, and Ternary checks it matches that form.

See Automate work with scheduled tasks in Anthropic's documentation for more about routines.

OpenAI Workspace Agent

1. In ChatGPT, create the workspace agent and publish it. Ternary can't start an agent that hasn't been published.
2. Open the agent's API channel.
3. Copy the API URL and the access token. The URL has the form https://api.chatgpt.com/v1/workspace_agents/agtch_…/trigger.

Custom HTTPS

Create an incoming webhook in your tool and copy its URL. For example:

• Zapier: trigger Webhooks by Zapier › Catch Hook.
• Make: module Webhooks › Custom webhook.
• Power Automate: trigger When an HTTP request is received.

The URL must use https://, must point to a public host, and must not contain credentials such as a user name, password or key. Pass credentials as a bearer token or a header instead. Ternary doesn't send to private or internal addresses.

If your endpoint requires a bearer token, also create or copy one of at least 16 characters.

Step 2: Create the Webhook

1. Open Admin in Ternary, select the Integrations tab and scroll to Webhooks. The list shows each webhook's Name, Type and Status.

2. Select Create Webhook, then choose the kind: Claude Routine, OpenAI Workspace Agent or Custom HTTPS.
3. Complete the form for that kind, as described below. Test Connection and Save become available once the required fields are filled.

To leave without saving, select Back to Webhooks.

Claude Routine

OpenAI Workspace Agent

Ternary stores only the agent ID from the URL, and shows the full URL again in Details.

Custom HTTPS

Step 3: Test the connection

1. Select Test Connection.
2. Ternary sends a test message with the headline Ternary webhook test to the endpoint.
3. Check the result in the form. Any 2xx response is a success. A Claude routine typically shows Response 200 OK, and an OpenAI Workspace Agent shows Response 202 OK.

If the test fails, the form shows the status code and a reason, such as 401 Unauthorized. Check the authentication details and try again., 404 Request rejected, Host not reachable, Timed out, TLS handshake failed or Endpoint blocked. See Troubleshooting.

4. Check the receiving tool. For a Claude routine, a new run appears in claude.ai. If you used the prompt from Automate budget follow-up with Ternary Webhooks, the routine replies Test received.

The test confirms that Ternary can reach your tool and that the token is accepted. It doesn't send a budget alert, and it doesn't change the webhook's status or failure count.

Step 4: Complete the configuration

1. Select Save.
2. For a Custom HTTPS Webhook, Ternary now shows a signing secret that starts with whsec_. Copy it straight away; it's shown only once. Your endpoint can use it to confirm that requests come from Ternary.

The Webhook now appears in the Webhooks list with the status Connected. Anyone with permission to set up notifications can select it under Add Subscribers › Webhooks in the alerts step of a budget.

What does Ternary send?

When a budget alert fires, Ternary sends one HTTPS POST request to each subscribed Webhook. The alert content is the same as the budget alert email, as plain text: the headline, a summary of spend or projected spend against the budget amount for the period, a link to the budget, and a footer.

Claude Routine

POST <Routine Endpoint>
Authorization: Bearer <API Token>
anthropic-version: 2023-06-01
Content-Type: application/json

{"text": "<budget alert text>"}

The routine receives the alert text as its input. A successful request returns 200 OK and starts a new session. See Trigger a routine through the API in Anthropic's documentation.

OpenAI Workspace Agent

POST https://api.chatgpt.com/v1/workspace_agents/<agent ID>/trigger
Authorization: Bearer <Access Token>
OpenAI-Beta: workspace_agent_runs=v1
Idempotency-Key: <delivery ID>
Content-Type: application/json

{"input": "<budget alert text>", "conversation_key": "<budget ID>"}

Because the conversation key is the budget ID, every alert for the same budget continues the same agent conversation.

Custom HTTPS

Ternary sends a JSON envelope with the event id, type (budget-alert), occurredAt, tenantID, workflowID and data (the alert's headline, summary and link). Each request includes content-type: application/json, user-agent: Ternary-Webhooks/1, and the signature headers webhook-id, webhook-timestamp and webhook-signature, followed by your bearer token and custom headers.

For the full field reference and signature verification samples, see Webhooks reference.

How do admins manage a Webhook?

Each Webhook in Admin › Integrations › Webhooks has an action menu (⋮) at the end of its row, with Details, Edit, Disable or Enable, and Delete. Use Search above the list to find a webhook by name.

A Webhook shows one of three statuses:

Edit a Webhook

1. Go to Admin › Integrations › Webhooks.
2. Open the Webhook's action menu (⋮) and select Edit.
3. Update the name or endpoint, then select Test Connection. If you changed the endpoint, enter the token again before testing; the form shows Enter the token to test changed settings. A name-only change tests the stored settings.
4. Select Save.

Budgets that already subscribe to the Webhook use the updated settings from the next alert onwards.

Disable or enable a Webhook

To pause deliveries without changing any budgets, open the Webhook's action menu and select Disable. The Webhook keeps its budget subscriptions but is skipped when alerts are sent. A disabled Webhook can't be added to more budgets.

To resume deliveries, select Enable. If Ternary disabled the Webhook after repeated failures, fix the cause first.

Rotate the token

Rotate the token if it may have been shared, if someone who had it leaves your team, or as part of your regular key rotation.

1. Generate a new token in the receiving tool.
   • Claude Routine: edit the routine and select Regenerate next to the API token. The old token stops working immediately.
   • OpenAI Workspace Agent: generate a new access token in the agent's API channel.
   • Custom HTTPS: create the new token in your tool.
2. In Ternary, edit the webhook and paste the new token into API Token, Access Token or Token.
3. Select Test Connection, then Save.

Rotate the signing secret (Custom HTTPS)

1. Edit the Webhook and select Regenerate next to the signing secret, then confirm.
2. Copy the new secret. It's shown only once.
3. Update the verification key in your endpoint at the same time. Requests signed with the new secret fail verification until you do.

Delete a Webhook

Ternary can't delete a Webhook while any budget subscribes to it; the message says how many budgets use it. Remove the Webhook from those budgets first. To stop deliveries without editing budgets, disable it instead.

1. Go to Admin › Integrations › Webhooks.
2. Open the Webhook's action menu (⋮) and select Delete.
3. In the Delete Webhook dialog, confirm. Deleting can't be undone.

Deleting the Webhook in Ternary doesn't delete the routine, agent or workflow in the receiving tool.

Troubleshooting