Redis + BullMQ dashboard

briq_run({
  recipe: "redis-bullmq",
  params: {
    "queues": [
      "default"
    ],
    "size": "nano"
  },
  wait: true
})

curl -X POST https://api.briq.cloud/v1/briqs \
  -H "Authorization: Bearer $BRIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "recipe": "redis-bullmq",
    "params": {
      "queues": [
        "default"
      ],
      "size": "nano"
    },
    "wait": true
  }'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "REDIS_URL": "…" }, … }

# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
  -H "Authorization: Bearer $BRIQ_API_KEY"

When to use it

• Your app runs BullMQ (or Bull) workers and you want the queues and a way to see them.
• The agent is building or debugging a job pipeline and needs to see waiting, active, failed and completed jobs.

Workers connect to REDIS_URL; Bull Board (bullboard) lists each queue once a worker touches it.

Tips

• An empty board means nothing has been enqueued yet. queues only echoes the names back in the outputs.
• Show the board: briq_run({ recipe: "redis-bullmq", expose: "private" }), or briq_expose port 3000 of bullboard with mode: "private".
• Without the UI: briq_exec on redis with redis-cli llen bull:emails:wait.
• The prefix is bull. For another one, run the Bull Board image yourself.
• No volume: Redis saves to its disk when it stops, so queues usually survive a stop; keep nothing there you cannot rebuild.