Actions4
- Graphic Actions
- Carousel Actions
- Job Actions
Overview
This node interacts with the Contentdrips API to manage jobs related to creating graphics and carousels. Specifically, the Job - Get Status operation retrieves the current status of a job by its ID. This is useful for workflows where you submit a job to generate content asynchronously and need to check if the job has completed, is still processing, or failed.
Common scenarios:
- After submitting a graphic or carousel creation job, use this node to poll the job status until it completes.
- Automate conditional logic based on whether the job succeeded or encountered errors.
- Integrate with other systems that require confirmation of content generation before proceeding.
Example:
You create a carousel using Contentdrips in one workflow step, then use this node with the Job - Get Status operation to periodically check if the carousel is ready before downloading or sharing it.
Properties
| Name | Meaning |
|---|---|
| Job ID | The ID of the job to check |
Output
The output JSON contains the status information of the specified job as returned by the Contentdrips API. This typically includes fields such as job state (e.g., pending, completed, failed), progress details, timestamps, and any error messages if applicable.
No binary data is output by this operation.
Example output structure (simplified):
{
"id": "job-id-string",
"status": "completed",
"progress": 100,
"result_url": "https://...",
"error": null
}
Dependencies
- Requires an active API key credential for the Contentdrips API.
- The node makes HTTP requests to
https://generate.contentdrips.com. - No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
- Invalid Job ID: If the provided Job ID does not exist or is malformed, the API may return an error. Verify the Job ID is correct and was obtained from a previous job submission.
- API Authentication Errors: Ensure the API key credential is valid and has proper permissions.
- Network Issues: Connectivity problems can cause request failures; check network access to the Contentdrips API endpoint.
- Job Not Found or Expired: Jobs may expire or be deleted after some time. If the status cannot be retrieved, confirm the job is still active.
If the node throws an error message containing "Unknown error occurred," it usually indicates an unexpected failure; enabling "Continue On Fail" can help handle such cases gracefully.
Links and References
- Contentdrips API Documentation (for detailed API endpoints and job status response format)
- n8n Documentation on Creating Custom Nodes