Use Runliant to find out when an n8n workflow fails or silently stops running. The node reports only the run status and the optional result count, duration, or failure label that you choose to send. It does not read or send your workflow's business data.

1. In Runliant, create a task.
2. Copy the receiving URL and connection password shown by Runliant.
3. In n8n, create a Runliant API credential. This is the connection saved by n8n.
4. Paste the receiving URL into Receiving URL.
5. Paste only the connection password into Connection Password. Do not add Bearer.
6. Use Test credential. A successful test means n8n can reach the Runliant task.

The connection password is stored in n8n's credential vault and is not written into workflow JSON.

Add Report Result to Runliant after the part of the workflow you want to monitor. Choose one result:

• Workflow Started
• Workflow Finished Successfully
• Workflow Failed

The n8n execution ID is used automatically so Runliant can match start and finish signals from the same run. After the first real workflow execution, Runliant shows whether the connection succeeded.

This package follows the official @n8n/node-cli structure.

• npm run lint checks n8n publishing rules.
• npm run build creates the publishable dist directory.
• npm run dev starts a local n8n development instance.

Public npm publication still requires a dedicated public GitHub repository, an npm publisher account, and the official provenance-enabled GitHub Actions release workflow.