Best-fit use cases
Implementation
A reliable four-step workflow
Trigger
Start from a webhook, schedule, database event, form, or supported application node.
Normalize
Map the incoming record to stable template field names and reject missing required values.
Generate
Call the Duply image API through an authenticated HTTP Request node.
Deliver
Write the image URL back to the source record or pass it to storage, review, or publishing.
- trigger
- A CMS webhook announces a published article
- inputs
- Title, section, author, hero image
- output
- A branded article card
- destination
- CMS metadata and social queue
Frequently asked questions
Does Duply need a dedicated n8n node?
No. An authenticated HTTP Request node can call the Duply API and map fields from any previous n8n step.
How should retries work?
Retry temporary network failures, but route validation errors such as missing fields or unreachable image URLs to a review branch.
Continue the workflow
Build one production-shaped example
Start with one approved template, realistic data, and the exact trigger your team intends to use.
Start free