Skip to main content
Tavryn’s webhook system connects your procurement agent’s autonomous activity to the tools your team already uses. Whenever Tavryn detects waste, starts a negotiation, proposes a deal, requires your approval, or settles a payment, it fires an outbound webhook to the URL you configure. Separately, Circle’s inbound webhook integration keeps on-chain transaction status synchronized in real time so your dashboard always reflects the true state of every payment.

Configuring Your Outbound Webhook

1

Open Settings

Navigate to your business Settings page in the Tavryn dashboard.
2

Enter your webhook URL

Find the Notification Webhook field and paste your Slack Incoming Webhook URL, Discord webhook URL, or any custom HTTPS endpoint.
3

Test the connection

Click Test Webhook. Tavryn sends a sample payload to your endpoint. Confirm you receive it before saving.
4

Save

Click Save Settings. All future events for this business will POST to the configured URL.
You can also update your webhook URL programmatically via the API:

Events That Trigger Webhooks

Tavryn fires a webhook notification for each of the following agent events:

Outbound Webhook Payload Structure

Every outbound webhook is a POST request with a Content-Type: application/json body. The exact payload shape adapts to the platform (Slack, Discord, or generic HTTP) detected from the URL:
Webhooks include a link to the relevant page in the Tavryn dashboard whenever a direct action is available (such as an approval link or transaction view).

Webhook Delivery & Timeouts

Tavryn dispatches outbound webhooks asynchronously so that a slow or unavailable external endpoint never blocks the autonomous agent loop. If your endpoint returns a non-2xx response or times out, Tavryn logs a warning but continues normal operation. Retry logic is not currently applied — ensure your endpoint is reliably available.

Circle Inbound Webhooks

Tavryn also receives inbound webhooks from Circle to keep on-chain transaction status synchronized in your dashboard. These are sent by Circle whenever the state of a developer-controlled wallet transaction changes. Endpoint: POST /api/webhooks/circle

Subscription Confirmation Handshake

When you register this endpoint with Circle, Circle sends a SubscriptionConfirmation message. Tavryn automatically responds by GETting the SubscribeURL to complete the handshake — no manual action is required on your part.

Transaction Lifecycle Events

Circle fires webhooks for each state transition in a transaction’s lifecycle. Tavryn maps these states to the payment status shown in your dashboard: Example Circle transaction webhook payload:

Supported Platforms

Tavryn auto-detects the webhook platform from the URL and formats the payload accordingly:

Slack

Any URL containing slack.com — formats payload as { "text": "..." } using Slack’s Incoming Webhook schema.

Discord

Any URL containing discord.com — formats payload as { "content": "..." } using Discord’s webhook schema.

Custom HTTP

Any other HTTPS endpoint — sends the full payload including title, message, content, and text fields for maximum compatibility.