Receive Hades notifications in your system (webhook)

A webhook is Hades notifying your system (ERP, CRM, spreadsheet, automation) at the moment something happens, so your system does not have to keep asking. It is part of the Oracle plan and up, and the owner or a manager sets it up, in Integrations.

The notifications that exist

• Meeting analysis ready — right after each meeting: summary, pains, objections, next steps.
• Meeting outcome logged — when the rep says whether it closed, moved forward, went to follow-up or was lost.
• New contact — a lead from a campaign, a form, a meeting or created by hand.
• Deal changed stage — every stage change in the pipeline, made by a person or by Hades.
• Deal won — when a deal enters Won.
• Proposal generated — when a proposal is born from a meeting.
• Customer replied to the follow-up — when the customer replies on WhatsApp and the sequence stops by itself.

A test meeting never triggers a notification, and the conversation transcript never goes in a notification (only the summary and the analysis).

Add the endpoint

1. Click your photo (or your initials) at the bottom of the left menu and choose Integrations. Scroll to the Webhook section.
2. In Endpoint that receives the notifications, paste your system's address. It must start with https:// (internal-network addresses and addresses with a user and password are not accepted).
3. In Which notifications to send, leave ticked only the ones your system will use.
4. Click Add endpoint.
5. The secret shows up, and it is not shown again. Click Copy, save it in your system and click I've saved it. It is how your system checks that a notification really came from Hades.
6. Click Send test. Within 1 minute the test notification reaches your endpoint, and your system's response shows up in Latest deliveries.

What your system receives

Each notification is a POST with JSON to your endpoint. The body always carries id, tipo (for example reuniao.analisada), versao, criado_em, workspace_id and dados (the contact, meeting, deal or proposal). Change notifications also carry mudanca, with the before and after (the stage it left and the one it went to, for example). The headers that matter:

• X-Hades-Evento — the notification id. It is the same on every attempt: if your system already processed it, answer 200 and ignore it.
• X-Hades-Tipo — the type of the notification.
• X-Hades-Assinatura — the proof that it came from Hades, in the format t=...,v1=....

To check the signature, compute the HMAC SHA-256 of the text t.body (the t from the header, a dot and the raw body, before any JSON.parse) using your secret, and compare it with v1. Reject it if t is older than 5 minutes. Example in Node:

const crypto = require("crypto");

function veioDoHades(cabecalho, corpo, segredo) {
  const p = Object.fromEntries(cabecalho.split(",").map((x) => x.split("=")));
  if (Math.abs(Date.now() / 1000 - Number(p.t)) > 300) return false;
  const esperado = crypto.createHmac("sha256", segredo).update(p.t + "." + corpo).digest("hex");
  return crypto.timingSafeEqual(Buffer.from(esperado), Buffer.from(p.v1 || ""));
}

What happens if your system does not answer

• Answer 2xx within 10 seconds. Hades does not follow redirects.
• A 5xx, 408 or 429 error, or no answer: Hades tries again after 1 min, 5 min, 30 min, 2 h, 6 h and 24 h. After the last one the notification is marked as exhausted.
• Any other 4xx error: the notification is marked refused and is not repeated.
• If the endpoint fails for 3 days in a row, Hades turns the endpoint off and tells the owner in the bell. The row shows Off: failed for 3 days; after fixing your system, click Turn on again.
• While there are failures, the row shows Failing since the date they started.

Changing the endpoint later

• Edit notifications — changes which notifications arrive (click Save notifications).
• Turn off and Turn on again — pauses and resumes without losing the secret. Turning off is always possible, even if the company changes plans.
• Generate new secret — the old secret stops working immediately; your system needs to receive the new one.
• Delete — deletes the endpoint and its delivery history.
• Add another endpoint — one system per endpoint, each with its own secret and its own notifications.

Prefer to fetch the data when you want instead of receiving notifications? See create an API key. If a notification does not arrive, start with Latest deliveries: that is where the answer your system gave to each attempt is.