Actions6
Overview
The node interacts with the Contentdrips API to create and manage graphic content such as static graphics and carousels. It supports starting rendering jobs, checking their status, and retrieving completed job results. This is useful for automating graphic generation workflows where designs are created dynamically based on templates and content updates.
Specifically, the Get Job Result operation retrieves the final output of a previously submitted rendering job once it has completed. This allows users to fetch generated graphics or carousel data after asynchronous processing.
Practical examples:
- After submitting a graphic generation job, use this operation to retrieve the finished image or PDF.
- In an automation workflow, poll for job completion and then get the result to send it via email or upload it elsewhere.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier of the job whose result you want to retrieve. |
Output
The output JSON contains the result data of the completed job fetched from the Contentdrips API endpoint /job/{jobId}/result. This typically includes the generated graphic or carousel content metadata and URLs to the rendered files.
If the job produces binary data (e.g., images or PDFs), the node returns references or URLs to these files rather than raw binary data directly.
Example output structure (simplified):
{
"job_id": "15bf4a39-876a-4780-aaa9-4be6fe2c61b4",
"status": "completed",
"result_url": "https://contentdrips.com/output/abc123.png",
"metadata": {
"format": "png",
"size": "1024x768"
}
}
Dependencies
- Requires an API key credential for authenticating requests to the Contentdrips API.
- The node uses HTTP requests to Contentdrips endpoints to check job status and retrieve results.
- No additional environment variables are needed beyond the configured API authentication.
Troubleshooting
- Job not found or invalid Job ID: Ensure the Job ID provided is correct and corresponds to a job that was actually started.
- Job not completed yet: If you try to get the result before the job finishes, the API may return an error or incomplete data. Use the "Check Job Status" operation first to confirm completion.
- Timeouts or network errors: Network issues can cause failures in fetching job results. Verify connectivity and API key validity.
- Invalid JSON input (for other operations): When providing JSON content updates or carousel data, ensure the JSON is well-formed to avoid parsing errors.
Common error messages:
Job failed: <message>— Indicates the job processing failed; check the message for details.Job timeout: Job <id> did not complete within <time> minutes— The job took too long; consider increasing wait time or checking job parameters.