Skip to main content

Understand the internal update worker

Who this is for​

This guide is for an authorised operator or developer of the existing internal update worker. n8n is not the person's alert editor, a personal identity provider or an accepted customer connector. A service worker cannot impersonate users, inspect their private alert criteria or subscribe them because an organisation pays.

Start here​

  1. Use Alerts for personal topics, exclusions, timing, timezone, quiet hours and an offered verified destination. Each person confirms their own choices in Abe.
  2. For operational work, obtain the separately authorised workflow and credential handling procedure from support. Keep the worker credential in its protected server credential store, never in a workflow property, exported file, browser, chat or screenshot. Do not use a staff account as worker authority.
  3. Read the recorded cadence before requesting a change: source materialisation is daily at 06:00 Australia/Brisbane, following the existing source collection; due deliveries are checked separately each minute. This is recorded operational evidence, not a fresh live schedule check by this guide. Collection time does not determine the person's chosen send time.
  4. The repository export is an inactive manual draft for recovery and local checks. It is not evidence that this copy is deployed. No new schedule or customer workflow editor is established here. The operator must read back the authorised current workflow and retention settings before a separately approved change.
  5. Keep worker outputs bounded to operational results. Patient data, subscription criteria, relevance explanations and full evidence bodies do not belong in worker logs or externally disclosed messages. A fetched job is not a delivery receipt.

Before selling customer-credential processing or a workflow editor, obtain written terms for that use. Existing internal automation does not establish an OEM agreement or current fee quote. This guide authorises no live workflow change.

What success looks like​

The authorised worker performs its defined collection or due-job task and stores only genuine permitted outcomes. Current internal dispatch is limited to the existing supported in-app and self-email path; the new Telegram/Notion attempt and reconciliation adapters are not proved by the inactive export. No new external acceptance counters or dashboard are promised.

For an approved future external adapter, accepted requires a real provider receipt; unknown stays held for reconciliation, and failed requires a definitive failure. Neither a queue claim nor an HTTP response proves the intended recipient read anything. See Owner.

If it does not work​

Do not blindly replay an uncertain send. Ask support to check the exact approved destination, existing attempt and worker time without private criteria or credentials. A source failure cannot be repaired by marking material current. A timezone or pause mismatch should be checked against the person's current choices before dispatch. Missing consent, revoked authority or source rights means no send.

Stop or change your choices​

A person pauses or archives their subscription through the existing Alerts controls. An operator stops the affected worker through the separately authorised operational procedure and verifies its state; do not invent a new stop button or schedule. Disconnect the affected application independently. Do not claim an already accepted message was recalled or a paused preference deleted.