Skip to content

Notifications

Alien edited this page Nov 17, 2026 · 3 revisions

Notifications

Dossier can tell you when something happens: the job agent finished a run, a portal you use was withdrawn, a draft is ready, New application finished writing your resume and letter, a reply arrived, an interview is tomorrow, a follow-up is due, or a new version is out. Set it up in Settings → Notifications: add a channel, choose which events go to it in the grid, and check the delivery log when something doesn't arrive.

Messages carry a title, a short text and a link back to Dossier. They never carry your profile, your documents, postings' text, your mail or any key.

Channels

Each channel has Send a test, which sends a sample message at once and says why it failed if it did. A message that can't be delivered is tried again after 1, 5 and 30 minutes. A channel with 10 failed deliveries in a row is paused until you resume it.

Email

Dossier sends through your mail provider's SMTP server: its name, the port (587 for STARTTLS, 465 for TLS), your user and password, and the from and to addresses. Many providers want an app password rather than your own.

ntfy

ntfy pushes a notification to your phone. Enter the server (ntfy.sh, or your own) and a topic, and subscribe to the same topic in the ntfy app. Tapping a notification opens Dossier.

On ntfy.sh without an access token, anyone who knows the topic can read the messages: use a hard-to-guess topic, or an access token for a protected topic or your own server.

Webhook

Each event goes to your address as JSON, which suits n8n and similar tools. Addresses on your own network work too. The body looks like this:

{
  "event": "agent.run.finished",
  "title": "Agent run finished · 15 new postings",
  "text": "Backend, Berlin: 9 new · best Backend Engineer at Zalando, covers 5 of 6 (Backend)\n…",
  "link": "https://dossier.example.com/jobs?found=agent",
  "at": "2026-11-16T07:00:00.000Z",
  "data": { "newCount": 15, "searches": [], "failed": [], "postings": [] }
}

data is the event's own data: for an agent run, every new posting with its title, company, place, link, the portals that found it and its scores per profile.

Dossier makes a signing secret for each webhook; Copy secret copies it, and Regenerate makes a new one. Every request carries an X-Dossier-Signature header:

X-Dossier-Signature: t=1763276400,v1=5f3c…

v1 is the HMAC-SHA256, in hex, of the timestamp, a dot and the raw body (1763276400.{"event":…}), made with the secret. To check a request, compute the same HMAC over the body exactly as received and compare it with v1; reject a timestamp more than a few minutes old. In Node.js:

const crypto = require("node:crypto");

function verify(header, body, secret) {
  const { t, v1 } = Object.fromEntries(header.split(",").map((part) => part.split("=")));
  const expected = crypto.createHmac("sha256", secret).update(`${t}.${body}`).digest("hex");
  const fresh = Math.abs(Date.now() / 1000 - Number(t)) < 300;
  return fresh && crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(v1));
}

In n8n, check it in a Code node with the function above, on the body as received (turn on the Webhook node's Raw Body option).

Links

Links in messages use DOSSIER_PUBLIC_URL when it's set (see Environment variables), or else the address you last opened Dossier at. On the desktop app's On this computer, messages carry no link.

Clone this wiki locally