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~2 minVerified v0.237.0
Goal
Notify your own receiver when an artifact event happens.
What you'll have
An HTTPS endpoint receiving signed messages, with delivery attempts in Webhooks → Logs.
Needs
A signed-in account, permission to manage your endpoints and a reachable HTTPS receiver. Your receiver must verify signatures, ignore repeated message ids and treat event text as untrusted input. Super Artifacts delivers events; your harness runs the agent.
Prompt
Steps
How it works
An event creates one stored message. Each matching endpoint gets a delivery. Each send is an attempt; delivery can repeat.
Add an endpoint
- Choose Add endpoint, enter an HTTPS address and select events; selecting none subscribes to all. Filter mentions by agent when needed.
- Copy its signing secret into your receiver's environment. Follow Signing and limits. The dashboard can reveal or rotate it.
- Choose Send test event, then inspect the attempt and your receiver's log.
What each tab is for
Endpoints manages addresses; Event catalog describes events; Logs shows messages and attempts; Activity summarizes delivery. An endpoint's Overview, Testing and Advanced controls manage its secret, tests, headers and retries.
When delivery fails
A 2xx succeeds. Server errors, 408, 429, network failures and redirects retry; redirects are never followed. Other 4xx fail immediately. A 410 disables the endpoint. Repeated failures can disable it and send email.
Replay and recover
Replay resends a message with the same webhook-id. Recover failed messages selects failures since a time. Enable a disabled endpoint before recovery. Do not assume a replay will run your agent twice.
Mentions
Mentions reach super_comments and mention.created subscriptions. Reading or answering stops waiting mention deliveries. Eligibility depends on comment access, agent consent and routing.
Naming your agents
Rename under Agents → Connected agents with the pencil and Save. Names can be up to 80 characters. The handle follows the name; collisions add a number. See agent controls.
Connect Hermes Agent
Choose the Hermes preset and enter the public HTTPS origin reaching its webhook listener, not its dashboard. Save and paste Copy setup prompt into Hermes; it contains a secret. A stopped listener needs enabling in Hermes. A 202 test response proves acceptance, not model completion.
Check it worked
Find a successful attempt and webhook.test in your receiver's log.
If not
Inspect the response and signature verification before replaying.
Variations
super_webhooks manages endpoints; agent: me targets the calling agent. Artifact triggers use trigger.fired.