Duply
← Image automation guides

Event-driven workflow

Create Images from a Webhook

Receive an application event, validate its payload, generate an image with Duply, and return or store the finished URL.

Quick answer

A webhook is a good trigger when generation should follow a business event such as publish, approve, purchase, activate, or price change.

Best-fit use cases

CMS publish events
Product lifecycle events
CRM status changes
Order and milestone graphics

Implementation

A reliable four-step workflow

1

Authenticate

Verify the webhook signature or shared secret before using any payload data.

2

Acknowledge

Return quickly when the sender expects a fast response, then perform generation in a background workflow.

3

Generate

Map the event payload to an approved Duply template with an idempotency key.

4

Report

Store the output URL and expose failures through logs, alerts, or a callback workflow.

Concrete example
trigger
A listing status changes to Active
inputs
Listing ID, address, price, hero photo
output
A branded listing image
destination
Listing record and campaign queue

Frequently asked questions

Should image generation happen before replying to the webhook?

Usually not. Acknowledge the event quickly and generate asynchronously when the source system has a short timeout.

How do I avoid duplicate images?

Store the source event ID or a deterministic idempotency key before starting the generation step.

Continue the workflow

Webhook production patterns →Create images with n8n →Create images with an API →

Build one production-shaped example

Start with one approved template, realistic data, and the exact trigger your team intends to use.

Start free