AchiralAchiral

Docs · LLMs and developers

Version3.12.1

Receive signed events from external systems so important activity can be remembered.

Webhooks

Webhooks let external systems push events into Achiral memory without requiring a full app connector.

Create and manage webhook endpoints from the organization dashboard under Integrations > Webhooks.

When to use a webhook

Use a webhook when a system can send events directly to Achiral, especially for internal tools, operational workflows, alerts, custom apps, or products that are not yet available as first-class connectors.

Webhooks are best for event-shaped data: something happened, when it happened, who or what it affected, and the details Achiral should remember.

Create an endpoint

Select New endpoint in the Webhooks tab, then provide:

  • Endpoint name: a human-readable label for the source.
  • Event shape: a semantic preset such as Generic event, Activity update, Alert event, Incident event, or Document event.
  • Provider key: the stable provider identifier. Presets fill this automatically.
  • Memory event type: the type Achiral should assign to incoming events.
  • Require HMAC signature: recommended, and enabled by default.

After creation, Achiral shows the endpoint URL and, when HMAC is enabled, the HMAC secret. Add those values to the sending system.

Security

Keep webhook URLs and HMAC secrets private. Treat the HMAC secret like a credential.

When HMAC is required, the sending system must sign requests with the shared secret. Unsigned or incorrectly signed requests should be rejected before they enter organization memory.

Operations

Webhook endpoints can be paused, resumed, or archived from the Webhooks tab.

  • Active endpoints can receive events.
  • Paused endpoints remain configured but stop accepting new ingestion work.
  • Archived endpoints are retired and should no longer be used by sending systems.

Troubleshooting

If events are not appearing in memory:

  • Confirm the endpoint is active.
  • Confirm the sending system is using the current endpoint URL.
  • Check that the HMAC signature is present and generated with the correct secret.
  • Verify the sender is posting valid event payloads.