Actions6
- Job Actions
- Tool Actions
Overview
This node interacts with the Workfloows API to retrieve the status of a specific job by its unique Job ID. It is useful for monitoring asynchronous or long-running tasks initiated in the Workfloows platform, allowing users to check progress, results, or errors related to those jobs.
Typical use cases include:
- Tracking the completion status of data processing or scraping jobs.
- Fetching results once a job has finished.
- Integrating job status checks into automated workflows to trigger subsequent actions based on job outcomes.
For example, after starting a web scraping job via the Workfloows API, you can use this node to periodically check if the job has completed and then process the scraped data.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier (UUID) of the job whose status you want to retrieve. |
| Simplify | Whether to return a simplified version of the response instead of the full raw data. |
- Simplify option returns a concise object containing key job details such as job ID, status, input parameters, and results if available, making it easier to work with in downstream nodes.
Output
The node outputs an array of JSON objects representing the job status information.
If Simplify is enabled (default), the output JSON includes:
id: The job's unique identifier.status: Current status of the job (e.g., pending, running, completed).input: The input parameters originally provided to the job.results: The results produced by the job, if available.
If Simplify is disabled, the output contains the full raw response from the Workfloows API, which may include additional metadata and nested structures.
No binary data is output by this node.
Dependencies
- Requires an active API key credential for the Workfloows API.
- The node makes authenticated HTTP requests to the Workfloows API endpoints.
- Network access to
https://api.workfloo.wsis necessary.
Troubleshooting
- Invalid Job ID: If the provided Job ID is incorrect or does not exist, the API will likely return an error or empty response. Verify the UUID format and ensure the job was created successfully.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly configured in n8n credentials.
- Network Issues: Connectivity problems to the Workfloows API endpoint will result in request timeouts or errors. Check network/firewall settings.
- Unexpected Response Format: If the API changes its response structure, the simplified output might miss some fields. In such cases, disable the Simplify option to inspect the full raw response.
Links and References
- Workfloows API Documentation (for detailed API usage and job management)
- n8n Documentation (for general guidance on using custom nodes and credentials)