Contentdrips icon

Contentdrips

Create carousels and static graphics using the Contentdrips API
Join our community

Actions6

Overview

This node integrates with the Contentdrips API to create and manage graphic content such as static graphics and carousels. It supports asynchronous job processing, allowing users to start a job for generating content and then check the status or retrieve the result once completed.

Common scenarios include:

  • Automatically generating branded social media graphics or carousel posts based on templates.
  • Polling for job completion to integrate generated content into workflows without manual intervention.
  • Handling both simple one-step synchronous generation and multi-step asynchronous job management.

Practical example:

  • A marketing automation workflow that triggers creation of a promotional carousel post using a predefined template, waits for the job to complete, and then uses the resulting image URL in subsequent steps.

Properties

Name Meaning
Job ID The unique identifier of the job to check the status of or retrieve the result from.

(Note: Only the "Job ID" property is relevant for the "Check Job Status" operation.)

Output

The node outputs JSON data representing the current status or the result of a job:

  • For Check Job Status operation, the output JSON contains the job's status details, including fields like status (e.g., "completed", "failed", "error") and potentially an error message if the job failed.
  • For Get Job Result operation, the output JSON contains the final rendered content or related metadata returned by the API.

The node does not output binary data directly; instead, it provides JSON responses from the Contentdrips API.

Dependencies

  • Requires an API key credential for authenticating requests to the Contentdrips API.
  • Uses internal helper function contentdripsApiRequest to make HTTP requests to the API endpoints.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Job Timeout Error: If a job does not complete within the specified timeout period (default 10 minutes), the node throws a timeout error. To resolve, increase the maximum wait time or verify the job is being processed correctly on the server side.
  • Invalid Job ID: Providing an incorrect or non-existent Job ID will cause the API request to fail. Ensure the Job ID is correct and corresponds to a previously started job.
  • API Request Errors: Network issues or invalid credentials can cause errors when calling the API. Verify API keys and network connectivity.
  • Error Polling Job Status: If polling encounters unexpected errors, the node surfaces these with descriptive messages. Check API availability and input parameters.
  • Unknown Operation: If an unsupported operation value is provided, the node throws an error indicating the operation is unknown.

Links and References

Discussion