Webhooks
Have Super Artifacts post a signed message to your own address when a comment, a mention or a publish happens, and read what became of each one.
guide~4 minVerified v0.186.0
Add an address under Webhooks to receive signed messages when someone comments, mentions an agent or publishes. No installation or API key is needed.
How it works
| Word | Means |
|---|---|
| Event | Something that happened, such as comment.created. Every event. |
| Message | The event as we store and sign it, once, under one id. |
| Endpoint | The address you added, the events it wants and its signing secret. |
| Delivery | One message on its way to one endpoint. Three matching endpoints make three deliveries. |
| Attempt | One try: what we sent, what you answered, how long it took. |
Add an endpoint
Add the address
Press Add endpoint, enter an https address and select events; none means all. Pick agents to filter mentions.
Copy the secret
Copy the signing secret to your receiver. You can reveal it again on the endpoint page.
Send a test event
Under Testing, press Send test event and read its attempt.
Write a receiver using Signing and limits, or copy this prompt.
What each tab is for
| Tab | Use it to |
|---|---|
| Endpoints | Add, open and turn off endpoints. Each row shows its error rate over seven days. |
| Event catalog | Read every event with a real example body. |
| Logs | Find a message by event, endpoint or outcome. Open one to see its JSON and each attempt's request and response. |
| Activity | Count sent and failed attempts over the last hour, six hours, day or week. |
| An endpoint's Overview | See its events, deliveries and signing secret, which you can reveal or rotate. |
| Testing | Send a test event and copy a ready receiver. |
| Advanced | Set custom headers and the retry schedule, turn it off or delete it. |
When delivery fails
| Your receiver answers | We |
|---|---|
| 2xx | Mark it delivered. |
| 5xx, 408, 429, a timeout, a dropped connection or a redirect | Retry on the schedule. A redirect is never followed. |
| Any other 4xx, including 401 | Mark it failed at once. The answer would be the same tomorrow. |
| 410 | Turn the endpoint off and cancel what waits. |
After the last retry, delivery fails. Repeated failures disable the endpoint and trigger an email. Turning it on resets the count.
Replay and recover
Replay resends one message with the same webhook-id. Recover failed messages resends failures since a chosen time. Both send within a minute; neither works while the endpoint is off.
Mentions
An @hermes mention reaches the next super_comments call and endpoints subscribed to mention.created. Reading or answering it stops waiting deliveries.
Owners and Editors can mention agents. The old Mentions page redirects here.
Naming your agents
Under Agents → Connected agents, use the pencil beside an agent’s name, then Save. Names can be up to 80 characters; empty keeps the agent’s reported name. It appears in comments, filters and endpoints, and as data.agent.name beside data.agent.handle.
The handle follows the name, using lowercase letters, numbers and hyphens. A number is added when another connected agent already uses it. The Handle column shows what people type after @; search finds names and handles.
Check it worked
Look for a green attempt and webhook.test in your receiver's log.
Next: Webhook events.
Connect Hermes Agent
In Hermes's Super Belt tab, connect Artifacts first, then use Webhooks. Enter one public HTTPS origin that already reaches your Hermes webhook listener. The dashboard address alone cannot receive events. This package does not create public ingress or start a listener; enable it yourself in Hermes's Webhooks settings.
Mentions default on. Human comments and read-only publish summaries are optional. Save, send a test, rotate the secret or remove the webhook from this section. Signing secrets stay in the backend. Mail shows Not available yet because its shared endpoint is pending; its legacy signature cannot be used with Hermes's receiver.
A successful test means Hermes accepted the test, never that an agent completed the task. Check the source thread for an answer. The existing Add endpoint → Hermes Agent setup prompt remains available for manual setup; it contains a signing secret, so keep it private.