Overview
The BullMQ Respond node is designed to respond to jobs managed by a BullMQ queue system. It allows users to mark jobs as completed and provide the result data back to the queue. This node is useful in workflows where asynchronous job processing is involved, and you want to programmatically send responses or results back to the job queue after some processing.
Common scenarios include:
- Completing background tasks that were queued and returning their results.
- Integrating with job queues to handle task completion notifications.
- Using n8n workflows to process jobs from BullMQ and respond with processed data.
For example, after processing a job fetched from a BullMQ Trigger node, this node can be used to send the processed output back to the job queue, marking the job as completed.
Properties
| Name | Meaning |
|---|---|
| Data Source | Choose the source of the response data: - Previous Node: Use data from the previous node. - Input: Use data provided directly as input. |
| Job Data | When "Data Source" is set to "Input", define the data assignments to respond with. |
| Use Current Job's Data | Boolean flag indicating whether to use the current job's data for responding. (Currently not supported; must be false.) |
| Queue Name | The name of the BullMQ queue containing the job to respond to. |
| Job ID | The identifier of the job to respond to. |
| Lock Token | The lock token associated with the job, required if the job is locked (usually obtained from a BullMQ Trigger node). |
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains a json field representing the responded job's full JSON representation as returned by BullMQ. This includes all job details such as id, data, status, timestamps, and logs.
No binary data is output by this node.
Dependencies
- Requires a Redis connection credential to connect to the BullMQ queue backend.
- Uses BullMQ library functions to interact with the queue and jobs.
- The node expects the user to provide valid queue name, job ID, and lock token when not using current job data.
Troubleshooting
Error: "Queue Name, Job ID and Lock Token must be provided!"
This occurs if any of these required parameters are missing when "Use Current Job's Data" is disabled. Ensure all three are correctly set.Error:
Job with ID "<id>" does not exist!
Indicates the specified job ID was not found in the given queue. Verify the job ID and queue name are correct and that the job still exists.Error: "Using current job data is not yet supported."
The option to use current job data is not implemented. You must disable this option and provide job details manually.Connection issues may arise if the Redis credentials are incorrect or the Redis server is unreachable.
Links and References
- BullMQ Documentation – Official documentation for BullMQ queue management.
- Redis – In-memory data structure store used by BullMQ.
- n8n Documentation – For general guidance on creating and using nodes in n8n.