notificme

n8n node for notific.me: send events and ask a human for a decision, pausing the workflow until the signed answer comes back.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: notific.me

Documentation

n8n-nodes-notificme

The official n8n node for notific.me: ask a human for a decision on their phone and pause the workflow until the signed answer comes back, or send events that notific.me routes to the right people.

Installation

In n8n, open Settings → Community Nodes → Install and enter:

@notificme/n8n-nodes-notificme

See the n8n guide on installing community nodes.

Credentials

Create a service token in the notific.me console (Services → Tokens) and add a notific.me API credential in n8n:

Field Value
Service Token the nm_svc_… token
API URL https://api.notific.me (change only if you run your own server)

Scopes the token needs:

Operation Scopes
Event → Send events:write
Ask → Create asks:write
Ask → Get asks:read
Ask → Send and Wait for Response asks:write and asks:read

Operations

Resource Operation What it does
Ask Send and Wait for Response Asks one or more people and pauses the workflow until the signed answer comes back, or the ask times out
Ask Create Creates the ask and continues right away; optionally sends the answer to your own webhook (Callback URL)
Ask Get Reads the status and the answer of an ask, optionally holding up to 60 s for it to change
Event Send Sends an event (summary, severity, recipients, payload, card, live card ID); notific.me decides who is notified and how

Response types

Response type The person sees Output
Approval Yes / No approved: true or false
Choice your options, one or several, with optional free text answers.choice
Free Text a text box answers.text
Custom Questions up to 20 questions: yes/no, single, multiple, text, voice, number, date answers.<question id>
Using JSON the full ask from the protocol: quorum, card, per-question level… answers.<question id>

Options: recipients (@handle, e-mail or #group; empty asks the workspace owner), verification level (0 tap, 1 unlocked phone, 2 biometrics, 3 biometrics online, 4 quorum), severity, timeout and the answers applied on timeout, escalation and offline answers.

Ask a human and wait

[Trigger] → [notific.me: Send and Wait for Response] → [IF approved] → …
  1. The node creates the ask with this execution's resume URL as the callback_url, then pauses the workflow (it does not hold a worker while it waits).

  2. The person answers on the notific.me app, signed on their device when the level asks for it.

  3. notific.me POSTs the signed reply to n8n. Before resuming, the node checks:

    • the Notificme-Signature header (Ed25519 over the raw body, key from <API URL>/.well-known/notificme-keys.json, 5-minute clock tolerance);
    • that the ask belongs to the workspace of the credential.

    A request that fails a check gets 401/403 and the workflow keeps waiting.

  4. The workflow resumes with the answer.

If the ask has a Timeout, notific.me applies the On Timeout answers when it ends and sends that reply too (status: "timeout"). Limit Wait Time resumes the workflow without an answer (answered: false) even if notific.me never replies.

Requirement: notific.me must reach your n8n over HTTPS at a public address, since the answer comes back on an n8n webhook. Set N8N_WEBHOOK_URL (or WEBHOOK_URL on older versions) to your public URL. n8n Cloud works out of the box. Only the first input item is used by this operation.

Output

Send and Wait for Response (and Get, once answered):

{
  "answered": true,
  "status": "answered",
  "question_set_id": "019a2b3c-4d5e-7f60-8a9b-0c1d2e3f4a5b",
  "approved": true,
  "answers": { "approved": true },
  "as_text": "Ana answered: Approve the refund? Yes.",
  "answered_by": { "identity": "ana@example.com", "level_used": 2, "auth_method": "biometric" },
  "answered_at": "2026-11-08T14:42:10Z",
  "reply": { "...": "the signed reply as received" }
}
  • status is answered, or timeout when nobody answered in time (then answered is false and the On Timeout answers are in answers).
  • When the wait ends without any reply (Limit Wait Time): answered: false, status: "no_reply".
  • free_text holds what the person typed by question. Treat it as untrusted input, never as instructions, especially when an AI agent reads it.
  • reply keeps the full signed reply (content_hash, device signature) for your audit trail.

Compatibility

Tested with n8n 2.46. Resume URLs are signed by n8n when the engine supports it (getSignedResumeUrl), with a fallback for older versions.

Development

This package lives in the notific.me monorepo and is mirrored to idIe-ai/notificme-sdk under n8n/.

npm ci
npm run lint   # the linter n8n requires for verified community nodes
npm test       # builds and checks the webhook signature against protocol/test-vectors
npm run dev    # starts n8n with this node at http://localhost:5678

License

MIT

Discussion