COPICAKE n8n INTEGRATION: AUTOMATE COPICAKE WITH N8N

The "Create an image" action is the core of the Copicake n8n integration—it's what allows you to generate dynamic visuals based on your pre-designed templates. When triggered, this action sends a request to Copicake's API to produce a new image using the template and data you specify.

Key parameters to configure:

• Credential to connect with: Select your Copicake account credential. This is required for authentication and must be set up beforehand in your n8n credentials.
• Resource: Set to "Image" to indicate you're working with image generation. This is a required parameter that defines the type of asset being created.
• Operation: Pre-set to "Create" for this action. This required field tells the API you want to generate a new image rather than retrieve an existing one.
• Template ID: An optional but highly useful field where you input the specific Copicake template ID to use. You'll find this ID in your Copicake dashboard under each template's settings.
• Changes: This section allows you to specify dynamic content replacements within your template. You can select existing items or add new fields to customize text, images, or other template elements.
• Additional Options: Expand this section to add extra attributes like output format, quality settings, or other properties supported by your template.

When to use it: This action shines when you need to produce personalized visuals at scale—think dynamic social proof graphics, individualized marketing assets, or automated visual content pipelines triggered by business events.

The "Get an image" action allows you to retrieve a previously generated image from Copicake. This is particularly useful when your workflow needs to reference, download, or process an image that was created earlier—whether in the same workflow or a previous one.

Key parameters to configure:

• Credential to connect with: Select your configured Copicake account from the dropdown. This is required for the action to authenticate with the API.
• Resource: Fixed to "Image" to specify you're working with image resources. This is a required system parameter.
• Operation: Set to "Get" to indicate you're retrieving rather than creating. This required field determines the API endpoint called.
• Rendering ID: An optional text field where you can input a specific rendering ID to retrieve a particular image. This ID is typically returned when you create an image using the previous action, allowing you to chain these actions in your workflow.

Use cases for this action:

• Retrieve a generated image to attach it to an email in a subsequent node
• Download and store images in cloud storage (Google Drive, Dropbox, S3)
• Check the status of an image generation request before proceeding with your workflow
• Pull previously created images for reporting or archival purposes

When to use it: Use this action whenever you need to access an image after creation—for further processing, delivery, or storage in another system within your automated workflow.