# @digital-boss/n8n-wf-deps

> n8n Workflow Dependencies Library. In general, the library provides methods for obtaining various kinds of dependencies in n8n workflows.

Latest version **1.0.1** (published 2023-03-18) · ISC license · 0 weekly downloads

## Install

```sh
npm install @digital-boss/n8n-wf-deps
pnpm add @digital-boss/n8n-wf-deps
yarn add @digital-boss/n8n-wf-deps
bun add @digital-boss/n8n-wf-deps
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.1 |
| Published | 2023-03-18 |
| First published | 2023-03-18 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 16.9 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Maintainers | feelgood-interface, saladindacic, maestrow, xlincw0w, sven.janssen, valentinalilova, quansenb |

## Links

- npm: https://www.npmjs.com/package/@digital-boss/n8n-wf-deps
- npm.io page: https://npm.io/package/@digital-boss/n8n-wf-deps

## Recent versions

- 1.0.1 (latest) — 2023-03-18
- 1.0.0 — 2023-03-18

## README

# N8N Workflow Dependencies Library

## Library Purpose

Initially, it this project was supposed to be implemented as a CLI application, to create a Table of Contents for n8n workflows.
 
However, during the development process, I realized that it would be convenient to provide each workflow in ToC with a reference to instances of n8n. For example, you have three different environments: Dev, UAT, Prod; and then in ToC for each workflow, you want a reference to the same workflow for each n8n instance you have. But this list of instances and their addresses belongs to a specific client or project that you have. Therefore, I decided to develop the project in the form of a library. This will allow you to use the n8n dependency tracking library for a wider range of projects and purposes.

In general, the library provides methods for obtaining various kinds of dependencies in n8n workflows. 

At the moment, it is implemented to get workflows dependencies with the indication of an external trigger at the second level of the hierarchy. For more information, see [Requirements to produced ToC](#producing-table-of-content) section.


### Producing Table of Content

1. It is hierarchical list: 1st level is workflows, 2nd level is triggers, Next levels is workflows, called by it's parents (called by "n8n-nodes-base.executeWorkflow" node).
1. All workflow items in a list should be a link (using markdown syntax) to corresponding document in use-cases folder.
1. Has two sections with corresponding headers: "Main Workflows" and "Orphans".
1. In Main section list workflows that has trigger nodes (besides "n8n-nodes-base.start").
1. For each workflow in main section:
    1. list their triggers as 2nd level of hierarchical list. 
    1. and as a 3rd level list workflows, called in trigger branch by "n8n-nodes-base.executeWorkflow" node. 
    1. next levels - workflows, called by it's parents. Rare case, but can happen.
1. In Orphans section list workflows, that are not existed in main section.

---
_Source: https://npm.io/package/@digital-boss/n8n-wf-deps · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._