@pauldeng/node-red-contrib-bullmq 1.0.0

package/bull-queue.html

@@ -0,0 +1,530 @@
+<script type="text/html" data-template-name="bull-queue-server">
+  <div class="form-row">
+    <label for="node-config-input-name"><i class="fa fa-tasks"></i> Queue</label>
+    <input type="text" id="node-config-input-name" placeholder="basecasts">
+  </div>
+  <div class="form-row">
+    <label for="node-config-input-deployment"><i class="fa fa-server"></i> Deployment</label>
+    <select id="node-config-input-deployment" style="width: 70%;">
+      <option value="single">Standalone Redis</option>
+      <option value="cluster">Redis Cluster / AWS MemoryDB</option>
+      <option value="sentinel">Redis Sentinel</option>
+    </select>
+  </div>
+  <div class="form-row bull-single-row">
+    <label for="node-config-input-address"><i class="fa fa-link"></i> Host</label>
+    <input type="text" id="node-config-input-address" placeholder="localhost">
+  </div>
+  <div class="form-row bull-single-row">
+    <label for="node-config-input-port"><i class="fa fa-plug"></i> Port</label>
+    <input type="number" id="node-config-input-port" placeholder="6379">
+  </div>
+  <div class="form-row bull-cluster-row">
+    <label for="node-config-input-clusterNodes"><i class="fa fa-sitemap"></i> Cluster Nodes</label>
+    <textarea id="node-config-input-clusterNodes" rows="3" style="width: 70%;" placeholder="host-a:6379, host-b:6379"></textarea>
+  </div>
+  <div class="form-row bull-sentinel-row">
+    <label for="node-config-input-sentinels"><i class="fa fa-sitemap"></i> Sentinels</label>
+    <textarea id="node-config-input-sentinels" rows="3" style="width: 70%;" placeholder="sentinel-a:26379, sentinel-b:26379"></textarea>
+  </div>
+  <div class="form-row bull-sentinel-row">
+    <label for="node-config-input-sentinelMasterName"><i class="fa fa-tag"></i> Master</label>
+    <input type="text" id="node-config-input-sentinelMasterName" placeholder="mymaster">
+  </div>
+  <div class="form-row">
+    <label for="node-config-input-db"><i class="fa fa-database"></i> Database</label>
+    <input type="number" id="node-config-input-db" placeholder="0">
+  </div>
+  <div class="form-row">
+    <label for="node-config-input-username"><i class="fa fa-user"></i> Username</label>
+    <input type="text" id="node-config-input-username" placeholder="default">
+  </div>
+  <div class="form-row">
+    <label for="node-config-input-password"><i class="fa fa-lock"></i> Password</label>
+    <input type="password" id="node-config-input-password">
+  </div>
+  <div class="form-row bull-sentinel-row">
+    <label for="node-config-input-sentinelUsername"><i class="fa fa-user"></i> Sentinel User</label>
+    <input type="text" id="node-config-input-sentinelUsername">
+  </div>
+  <div class="form-row bull-sentinel-row">
+    <label for="node-config-input-sentinelPassword"><i class="fa fa-lock"></i> Sentinel Pass</label>
+    <input type="password" id="node-config-input-sentinelPassword">
+  </div>
+  <div class="form-row">
+    <label for="node-config-input-tls"><i class="fa fa-shield"></i> TLS</label>
+    <input type="checkbox" id="node-config-input-tls" style="display:inline-block; width:auto; vertical-align:top;">
+    <span>Use TLS for Redis data connections</span>
+  </div>
+  <div class="form-row bull-sentinel-row">
+    <label for="node-config-input-sentinelTls"><i class="fa fa-shield"></i> Sentinel TLS</label>
+    <input type="checkbox" id="node-config-input-sentinelTls" style="display:inline-block; width:auto; vertical-align:top;">
+    <span>Use TLS for Sentinel discovery</span>
+  </div>
+  <div class="form-row bull-tls-row">
+    <label for="node-config-input-tlsRejectUnauthorized"><i class="fa fa-check"></i> Verify TLS</label>
+    <input type="checkbox" id="node-config-input-tlsRejectUnauthorized" style="display:inline-block; width:auto; vertical-align:top;">
+    <span>Reject unauthorized certificates</span>
+  </div>
+  <div class="form-row bull-tls-row">
+    <label for="node-config-input-tlsServerName"><i class="fa fa-globe"></i> TLS Server Name</label>
+    <input type="text" id="node-config-input-tlsServerName" placeholder="redis.example.com">
+  </div>
+  <div class="form-row bull-tls-row">
+    <label for="node-config-input-tlsCa"><i class="fa fa-certificate"></i> CA</label>
+    <textarea id="node-config-input-tlsCa" rows="3" style="width: 70%;"></textarea>
+  </div>
+  <div class="form-row bull-tls-row">
+    <label for="node-config-input-tlsCert"><i class="fa fa-certificate"></i> Client Cert</label>
+    <textarea id="node-config-input-tlsCert" rows="3" style="width: 70%;"></textarea>
+  </div>
+  <div class="form-row bull-tls-row">
+    <label for="node-config-input-tlsKey"><i class="fa fa-key"></i> Client Key</label>
+    <textarea id="node-config-input-tlsKey" rows="3" style="width: 70%;"></textarea>
+  </div>
+  <div class="form-row">
+    <label for="node-config-input-prefix"><i class="fa fa-code"></i> Prefix</label>
+    <input type="text" id="node-config-input-prefix" placeholder="{bull}">
+  </div>
+</script>
+
+<script type="text/javascript">
+  (function() {
+    function updateBullQueueServerRows() {
+      var deployment = $("#node-config-input-deployment").val() || "single";
+      $(".bull-single-row").toggle(deployment === "single");
+      $(".bull-cluster-row").toggle(deployment === "cluster");
+      $(".bull-sentinel-row").toggle(deployment === "sentinel");
+      $(".bull-tls-row").toggle($("#node-config-input-tls").is(":checked"));
+    }
+
+    RED.nodes.registerType("bull-queue-server", {
+      category: "config",
+      defaults: {
+        name: { value: "", required: true },
+        deployment: { value: "single", required: true },
+        address: { value: "localhost" },
+        port: { value: 6379, validate: RED.validators.number() },
+        db: { value: "" },
+        clusterNodes: { value: "" },
+        sentinels: { value: "" },
+        sentinelMasterName: { value: "" },
+        username: { value: "" },
+        sentinelUsername: { value: "" },
+        tls: { value: false },
+        sentinelTls: { value: false },
+        tlsRejectUnauthorized: { value: true },
+        tlsServerName: { value: "" },
+        prefix: { value: "" }
+      },
+      credentials: {
+        password: { type: "password" },
+        sentinelPassword: { type: "password" },
+        tlsCa: { type: "password" },
+        tlsCert: { type: "password" },
+        tlsKey: { type: "password" }
+      },
+      label: function() {
+        return this.name || this.address + ":" + this.port;
+      },
+      oneditprepare: function() {
+        $("#node-config-input-deployment").on("change", updateBullQueueServerRows);
+        $("#node-config-input-tls").on("change", updateBullQueueServerRows);
+        updateBullQueueServerRows();
+      }
+    });
+  })();
+</script>
+
+<script type="text/html" data-help-name="bull-queue-server">
+  <p>Configures the BullMQ queue name and Redis connection shared by the BullMQ nodes.</p>
+  <p>API reference: <a href="https://api.docs.bullmq.io/classes/v5.Queue.html" target="_blank" rel="noopener noreferrer">Queue</a> and <a href="https://api.docs.bullmq.io/interfaces/v5.QueueOptions.html" target="_blank" rel="noopener noreferrer">QueueOptions</a>.</p>
+
+  <h3>Options</h3>
+  <ul>
+    <li><b>Queue</b>: BullMQ queue name. All producer, worker, event, and flow nodes that select this config use this queue name unless a BullMQ flow child specifies another <code>queueName</code>.</li>
+    <li><b>Deployment</b>: Redis topology. Use <code>Standalone Redis</code> for one Redis endpoint, <code>Redis Cluster / AWS MemoryDB</code> for cluster-compatible endpoints, or <code>Redis Sentinel</code> for Sentinel discovery.</li>
+    <li><b>Host</b>: Standalone Redis host name or IP address.</li>
+    <li><b>Port</b>: Standalone Redis port. The default Redis port is <code>6379</code>.</li>
+    <li><b>Cluster Nodes</b>: Comma or newline separated cluster seed nodes such as <code>redis-a:6379, redis-b:6379</code>. AWS MemoryDB cluster configuration endpoints are entered here.</li>
+    <li><b>Sentinels</b>: Comma or newline separated Sentinel endpoints such as <code>sentinel-a:26379, sentinel-b:26379</code>.</li>
+    <li><b>Master</b>: Sentinel master name, for example <code>mymaster</code>.</li>
+    <li><b>Database</b>: Redis database number for standalone or Sentinel data connections. Cluster and MemoryDB deployments use Redis database <code>0</code>.</li>
+    <li><b>Username</b>: Redis ACL username for data connections. Leave empty for Redis servers that only use a password.</li>
+    <li><b>Password</b>: Redis password for data connections. Stored as a Node-RED credential.</li>
+    <li><b>Sentinel User</b>: Redis ACL username for Sentinel discovery connections when Sentinels require separate credentials.</li>
+    <li><b>Sentinel Pass</b>: Password for Sentinel discovery connections. Stored as a Node-RED credential.</li>
+    <li><b>TLS</b>: Enables TLS for Redis data connections. Use this for AWS MemoryDB and any Redis deployment that requires encrypted data connections.</li>
+    <li><b>Sentinel TLS</b>: Enables TLS for Sentinel discovery connections.</li>
+    <li><b>Verify TLS</b>: Rejects certificates that cannot be verified. Keep enabled in production unless you intentionally use a private test certificate.</li>
+    <li><b>TLS Server Name</b>: Optional server name used for certificate validation when it differs from the host value.</li>
+    <li><b>CA</b>: PEM certificate authority text for validating private Redis certificates. Stored as a Node-RED credential.</li>
+    <li><b>Client Cert</b>: PEM client certificate for mutual TLS deployments. Stored as a Node-RED credential.</li>
+    <li><b>Client Key</b>: PEM client private key for mutual TLS deployments. Stored as a Node-RED credential.</li>
+    <li><b>Prefix</b>: BullMQ key prefix. For Redis Cluster and MemoryDB, use a hash tag such as <code>{bull}</code> so BullMQ keys stay in one hash slot for atomic operations.</li>
+  </ul>
+
+  <h3>Example</h3>
+  <p>For local Redis, set <b>Queue</b> to <code>email-jobs</code>, <b>Deployment</b> to <code>Standalone Redis</code>, <b>Host</b> to <code>localhost</code>, and <b>Port</b> to <code>6379</code>.</p>
+  <p>For AWS MemoryDB, set <b>Deployment</b> to <code>Redis Cluster / AWS MemoryDB</code>, enter the cluster endpoint in <b>Cluster Nodes</b>, enable <b>TLS</b>, keep <b>Verify TLS</b> enabled, and use <code>{bull}</code> as <b>Prefix</b>.</p>
+  <p>Redis should use <code>maxmemory-policy=noeviction</code>. Bull v4 Redis queue data is not automatically migrated to BullMQ.</p>
+</script>
+
+<script type="text/html" data-template-name="bull cmd">
+  <div class="form-row">
+    <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
+    <input type="text" id="node-input-name">
+  </div>
+  <div class="form-row">
+    <label for="node-input-queue"><i class="fa fa-tasks"></i> Queue</label>
+    <input type="text" id="node-input-queue">
+  </div>
+</script>
+
+<script type="text/html" data-help-name="bull cmd">
+  <p>Executes BullMQ producer and queue-administration commands from an input message.</p>
+  <p>API reference: <a href="https://api.docs.bullmq.io/classes/v5.Queue.html" target="_blank" rel="noopener noreferrer">Queue</a>, <a href="https://api.docs.bullmq.io/classes/v5.Queue.html#add" target="_blank" rel="noopener noreferrer">Queue.add</a>, <a href="https://api.docs.bullmq.io/types/v5.JobsOptions.html" target="_blank" rel="noopener noreferrer">JobsOptions</a>, <a href="https://api.docs.bullmq.io/types/v5.DeduplicationOptions.html" target="_blank" rel="noopener noreferrer">DeduplicationOptions</a>, <a href="https://api.docs.bullmq.io/classes/v5.Queue.html#setglobalratelimit" target="_blank" rel="noopener noreferrer">Queue.setGlobalRateLimit</a>, and <a href="https://api.docs.bullmq.io/classes/v5.Queue.html#upsertjobscheduler" target="_blank" rel="noopener noreferrer">Queue.upsertJobScheduler</a>.</p>
+
+  <h3>Options</h3>
+  <ul>
+    <li><b>Name</b>: Optional label shown in the Node-RED workspace.</li>
+    <li><b>Queue</b>: Queue config node used to create the BullMQ <code>Queue</code>.</li>
+  </ul>
+
+  <h3>Input message</h3>
+  <ul>
+    <li><code>msg.cmd</code>: Command name. Defaults to <code>add</code>. Common commands include <code>add</code>, <code>addBulk</code>, <code>getJob</code>, <code>getJobs</code>, <code>removeJob</code>, <code>retryJob</code>, <code>getDelayed</code>, <code>promoteJob</code>, <code>getPrioritized</code>, <code>changePriority</code>, <code>setGlobalRateLimit</code>, <code>removeGlobalRateLimit</code>, <code>upsertJobScheduler</code>, and <code>removeJobScheduler</code>.</li>
+    <li><code>msg.payload</code>: Job data for <code>add</code> when <code>msg.jobData</code> is not set. For some commands it carries command parameters, such as <code>{ "max": 2, "duration": 1000 }</code> for <code>setGlobalRateLimit</code>.</li>
+    <li><code>msg.jobName</code>: BullMQ job name for <code>add</code>. Defaults to <code>default</code>.</li>
+    <li><code>msg.jobData</code>: Full job data object for <code>add</code>. When set, it takes precedence over <code>msg.payload</code>.</li>
+    <li><code>msg.jobopts</code>: BullMQ job options for <code>add</code>, including <code>delay</code>, <code>priority</code>, <code>deduplication</code>, <code>attempts</code>, <code>backoff</code>, <code>removeOnComplete</code>, and <code>repeat</code>.</li>
+  </ul>
+
+  <h3>Examples</h3>
+  <p>Add a delayed, prioritized job:</p>
+  <pre>msg.cmd = "add";
+msg.jobName = "email";
+msg.payload = { to: "user@example.com" };
+msg.jobopts = {
+  delay: 10000,
+  priority: 1,
+  removeOnComplete: true
+};
+return msg;</pre>
+  <p>Add one job per deduplication id:</p>
+  <pre>msg.cmd = "add";
+msg.jobName = "report";
+msg.payload = { customerId: "customer-42" };
+msg.jobopts = {
+  deduplication: { id: "customer-42-report" }
+};
+return msg;</pre>
+  <p>Set a global rate limit of two jobs per second:</p>
+  <pre>msg.cmd = "setGlobalRateLimit";
+msg.payload = { max: 2, duration: 1000 };
+return msg;</pre>
+  <p>Add or update a scheduler every minute:</p>
+  <pre>msg.cmd = "add";
+msg.jobName = "heartbeat";
+msg.payload = "scheduled heartbeat";
+msg.jobopts = {
+  jobId: "heartbeat-every-minute",
+  repeat: { pattern: "*/1 * * * *" }
+};
+return msg;</pre>
+  <p>Legacy <code>msg.jobopts.repeat.cron</code> is translated to a BullMQ Job Scheduler. Legacy repeat lookup and removal commands use exact scheduler ids.</p>
+</script>
+
+<script type="text/javascript">
+  RED.nodes.registerType("bull cmd", {
+    color: "#ffffff",
+    category: "function",
+    defaults: {
+      name: { value: "" },
+      queue: { type: "bull-queue-server", required: true }
+    },
+    inputs: 1,
+    outputs: 1,
+    align: "right",
+    icon: "bull_icon.png",
+    label: function() {
+      return this.name || "bull cmd";
+    }
+  });
+</script>
+
+<script type="text/html" data-template-name="bull run">
+  <div class="form-row">
+    <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
+    <input type="text" id="node-input-name">
+  </div>
+  <div class="form-row">
+    <label for="node-input-queue"><i class="fa fa-tasks"></i> Queue</label>
+    <input type="text" id="node-input-queue">
+  </div>
+  <div class="form-row">
+    <label for="node-input-completionMode"><i class="fa fa-check-circle"></i> Completion</label>
+    <select id="node-input-completionMode" style="width: 70%;">
+      <option value="immediate">Immediate</option>
+      <option value="manual">Manual acknowledgement</option>
+    </select>
+  </div>
+  <div class="form-row">
+    <label for="node-input-ackTimeout"><i class="fa fa-clock-o"></i> Ack Timeout</label>
+    <input type="number" id="node-input-ackTimeout" placeholder="300000">
+  </div>
+  <div class="form-row">
+    <label for="node-input-concurrency"><i class="fa fa-random"></i> Concurrency</label>
+    <input type="number" id="node-input-concurrency" placeholder="1">
+  </div>
+  <div class="form-row">
+    <label for="node-input-limiterMax"><i class="fa fa-tachometer"></i> Limiter Max</label>
+    <input type="number" id="node-input-limiterMax">
+  </div>
+  <div class="form-row">
+    <label for="node-input-limiterDuration"><i class="fa fa-hourglass-half"></i> Limiter Duration</label>
+    <input type="number" id="node-input-limiterDuration">
+  </div>
+</script>
+
+<script type="text/html" data-help-name="bull run">
+  <p>Creates a BullMQ Worker for the configured queue and emits each job as a Node-RED message.</p>
+  <p>API reference: <a href="https://api.docs.bullmq.io/classes/v5.Worker.html" target="_blank" rel="noopener noreferrer">Worker</a> and <a href="https://api.docs.bullmq.io/interfaces/v5.WorkerOptions.html" target="_blank" rel="noopener noreferrer">WorkerOptions</a>.</p>
+
+  <h3>Options</h3>
+  <ul>
+    <li><b>Name</b>: Optional label shown in the Node-RED workspace.</li>
+    <li><b>Queue</b>: Queue config node used by the worker.</li>
+    <li><b>Completion</b>: <code>Immediate</code> completes the BullMQ job after the message is emitted. <code>Manual acknowledgement</code> keeps the job active until a downstream <code>bull job</code> node completes, fails, or updates it.</li>
+    <li><b>Ack Timeout</b>: Maximum time in milliseconds to wait for manual acknowledgement before the node fails the active job. Set to <code>0</code> to wait indefinitely.</li>
+    <li><b>Concurrency</b>: Number of jobs this worker can process at the same time.</li>
+    <li><b>Limiter Max</b>: Optional worker-side rate limit count.</li>
+    <li><b>Limiter Duration</b>: Optional worker-side rate limit window in milliseconds. Set with <b>Limiter Max</b>.</li>
+  </ul>
+
+  <h3>Output message</h3>
+  <ul>
+    <li><code>msg.payload</code>: <code>job.data.payload</code> when present, otherwise the full BullMQ job data.</li>
+    <li><code>msg.job</code>: Serialized job metadata, including id, name, queue name, state-related timestamps, progress, attempts, and options.</li>
+    <li><code>msg.bull</code>: Queue and acknowledgement context used by downstream <code>bull job</code> nodes.</li>
+  </ul>
+
+  <h3>Example</h3>
+  <p>For fire-and-forget processing, use <b>Completion</b> <code>Immediate</code> and wire the output to your processing flow.</p>
+  <p>For a flow that must decide success or failure, use <b>Completion</b> <code>Manual acknowledgement</code>, wire the output to processing nodes, then wire into <code>bull job</code> with <b>Action</b> <code>complete</code> or <code>fail</code>.</p>
+</script>
+
+<script type="text/javascript">
+  RED.nodes.registerType("bull run", {
+    color: "#ffffff",
+    category: "function",
+    defaults: {
+      name: { value: "" },
+      queue: { type: "bull-queue-server", required: true },
+      completionMode: { value: "immediate" },
+      ackTimeout: { value: 300000, validate: RED.validators.number() },
+      concurrency: { value: 1, validate: RED.validators.number() },
+      limiterMax: { value: "" },
+      limiterDuration: { value: "" }
+    },
+    inputs: 0,
+    outputs: 1,
+    align: "left",
+    icon: "bull_icon.png",
+    label: function() {
+      return this.name || "bull run";
+    }
+  });
+</script>
+
+<script type="text/html" data-template-name="bull job">
+  <div class="form-row">
+    <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
+    <input type="text" id="node-input-name">
+  </div>
+  <div class="form-row">
+    <label for="node-input-action"><i class="fa fa-check"></i> Action</label>
+    <select id="node-input-action" style="width: 70%;">
+      <option value="complete">Complete</option>
+      <option value="fail">Fail</option>
+      <option value="failUnrecoverable">Fail unrecoverable</option>
+      <option value="progress">Progress</option>
+      <option value="rateLimit">Rate limit</option>
+      <option value="removeDeduplicationKey">Remove deduplication key</option>
+      <option value="getChildrenValues">Get children values</option>
+      <option value="getFailedChildrenValues">Get failed children values</option>
+      <option value="removeUnprocessedChildren">Remove unprocessed children</option>
+    </select>
+  </div>
+</script>
+
+<script type="text/html" data-help-name="bull job">
+  <p>Acts on an active job emitted by a manual-mode <code>bull run</code> node.</p>
+  <p>API reference: <a href="https://api.docs.bullmq.io/classes/v5.Job.html" target="_blank" rel="noopener noreferrer">Job</a> and <a href="https://api.docs.bullmq.io/classes/v5.UnrecoverableError.html" target="_blank" rel="noopener noreferrer">UnrecoverableError</a>.</p>
+
+  <h3>Options</h3>
+  <ul>
+    <li><b>Name</b>: Optional label shown in the Node-RED workspace.</li>
+    <li><b>Action</b>: Default job action. It can be overridden per message with <code>msg.cmd</code>.</li>
+  </ul>
+
+  <h3>Actions</h3>
+  <ul>
+    <li><code>complete</code>: Completes the active job. Use <code>msg.payload</code> as the return value.</li>
+    <li><code>fail</code>: Fails the active job. Use <code>msg.error</code> or <code>msg.payload</code> to describe the error.</li>
+    <li><code>failUnrecoverable</code>: Fails the active job with a BullMQ unrecoverable error so retry attempts are not used.</li>
+    <li><code>progress</code>: Updates job progress from <code>msg.progress</code> or <code>msg.payload</code>.</li>
+    <li><code>rateLimit</code>: Applies a worker rate limit delay. Use <code>msg.duration</code> as milliseconds.</li>
+    <li><code>removeDeduplicationKey</code>: Removes the active job deduplication key.</li>
+    <li><code>getChildrenValues</code>: Reads completed child return values for a flow parent job.</li>
+    <li><code>getFailedChildrenValues</code>: Reads failed child values for a flow parent job.</li>
+    <li><code>removeUnprocessedChildren</code>: Removes children that have not yet been processed.</li>
+  </ul>
+
+  <h3>Example</h3>
+  <p>Update progress, then complete a manual job:</p>
+  <pre>msg.cmd = "progress";
+msg.progress = 50;
+return msg;</pre>
+  <p>Wire that message into another <code>bull job</code> node with <b>Action</b> <code>complete</code>, or set:</p>
+  <pre>msg.cmd = "complete";
+msg.payload = { ok: true };
+return msg;</pre>
+  <p>The node uses the opaque <code>msg.bull.ackId</code> from <code>bull run</code> and does not expose BullMQ lock tokens.</p>
+</script>
+
+<script type="text/javascript">
+  RED.nodes.registerType("bull job", {
+    color: "#ffffff",
+    category: "function",
+    defaults: {
+      name: { value: "" },
+      action: { value: "complete" }
+    },
+    inputs: 1,
+    outputs: 1,
+    align: "right",
+    icon: "bull_icon.png",
+    label: function() {
+      return this.name || "bull job";
+    }
+  });
+</script>
+
+<script type="text/html" data-template-name="bull events">
+  <div class="form-row">
+    <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
+    <input type="text" id="node-input-name">
+  </div>
+  <div class="form-row">
+    <label for="node-input-queue"><i class="fa fa-tasks"></i> Queue</label>
+    <input type="text" id="node-input-queue">
+  </div>
+  <div class="form-row">
+    <label for="node-input-events"><i class="fa fa-bell"></i> Events</label>
+    <textarea id="node-input-events" rows="4" style="width: 70%;" placeholder="completed, failed, progress"></textarea>
+  </div>
+</script>
+
+<script type="text/html" data-help-name="bull events">
+  <p>Subscribes to BullMQ QueueEvents and emits global queue events as Node-RED messages.</p>
+  <p>API reference: <a href="https://api.docs.bullmq.io/classes/v5.QueueEvents.html" target="_blank" rel="noopener noreferrer">QueueEvents</a>.</p>
+
+  <h3>Options</h3>
+  <ul>
+    <li><b>Name</b>: Optional label shown in the Node-RED workspace.</li>
+    <li><b>Queue</b>: Queue config node whose global events will be observed.</li>
+    <li><b>Events</b>: Comma or newline separated event names. Leave empty to subscribe to the default set. Useful events include <code>completed</code>, <code>failed</code>, <code>progress</code>, <code>delayed</code>, <code>deduplicated</code>, <code>duplicated</code>, <code>waiting</code>, and <code>active</code>.</li>
+  </ul>
+
+  <h3>Output message</h3>
+  <ul>
+    <li><code>msg.topic</code>: Event name.</li>
+    <li><code>msg.payload</code>: BullMQ event payload.</li>
+    <li><code>msg.bull</code>: Queue, event name, and event id metadata.</li>
+  </ul>
+
+  <h3>Example</h3>
+  <p>Set <b>Events</b> to <code>completed, failed, delayed, deduplicated, progress</code> and wire the node to a debug node to inspect queue activity.</p>
+</script>
+
+<script type="text/javascript">
+  RED.nodes.registerType("bull events", {
+    color: "#ffffff",
+    category: "function",
+    defaults: {
+      name: { value: "" },
+      queue: { type: "bull-queue-server", required: true },
+      events: { value: "" }
+    },
+    inputs: 0,
+    outputs: 1,
+    align: "left",
+    icon: "bull_icon.png",
+    label: function() {
+      return this.name || "bull events";
+    }
+  });
+</script>
+
+<script type="text/html" data-template-name="bull flow">
+  <div class="form-row">
+    <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
+    <input type="text" id="node-input-name">
+  </div>
+  <div class="form-row">
+    <label for="node-input-queue"><i class="fa fa-tasks"></i> Queue</label>
+    <input type="text" id="node-input-queue">
+  </div>
+</script>
+
+<script type="text/html" data-help-name="bull flow">
+  <p>Adds atomic BullMQ parent and child job trees with <code>FlowProducer</code>.</p>
+  <p>API reference: <a href="https://api.docs.bullmq.io/classes/v5.FlowProducer.html" target="_blank" rel="noopener noreferrer">FlowProducer</a> and <a href="https://api.docs.bullmq.io/types/v5.FlowJob.html" target="_blank" rel="noopener noreferrer">FlowJob</a>.</p>
+
+  <h3>Options</h3>
+  <ul>
+    <li><b>Name</b>: Optional label shown in the Node-RED workspace.</li>
+    <li><b>Queue</b>: Queue config node used by the FlowProducer connection. Each flow job still supplies its own <code>queueName</code>.</li>
+  </ul>
+
+  <h3>Input message</h3>
+  <ul>
+    <li><code>msg.payload</code>: BullMQ flow tree. The root object contains <code>name</code>, <code>queueName</code>, <code>data</code>, optional <code>opts</code>, and optional <code>children</code>.</li>
+    <li><code>msg.flowopts</code>: Optional FlowProducer options applied to the add call.</li>
+  </ul>
+
+  <h3>Example</h3>
+  <pre>msg.payload = {
+  name: "parent-report",
+  queueName: "reports",
+  data: { payload: "parent" },
+  children: [
+    {
+      name: "child-report",
+      queueName: "reports",
+      data: { payload: "child" }
+    }
+  ]
+};
+return msg;</pre>
+  <p>The child jobs are processed before the parent job. A parent can read child results with a manual-mode <code>bull run</code> and a <code>bull job</code> action such as <code>getChildrenValues</code>.</p>
+</script>
+
+<script type="text/javascript">
+  RED.nodes.registerType("bull flow", {
+    color: "#ffffff",
+    category: "function",
+    defaults: {
+      name: { value: "" },
+      queue: { type: "bull-queue-server", required: true }
+    },
+    inputs: 1,
+    outputs: 1,
+    align: "right",
+    icon: "bull_icon.png",
+    label: function() {
+      return this.name || "bull flow";
+    }
+  });
+</script>