n8n headshot generator: inspect the complete image lifecycle

Build the input and storage route first

The 23 June 2025 tutorial combines n8n, Cloudinary and Replicate to generate professional headshots. Its form accepts images, the workflow stores them and a later step calls the generation API. Begin with a test image you are authorised to use so you can inspect the whole route without introducing another person’s private material.

1. Follow the tool overview at 0:12 and form setup at 1:00 for the demonstrated fields and upload path.
2. Inspect the submission and confirm that the stored image corresponds to the intended test record.
3. Use the storage segment at 3:00 to review authentication and API-key handling, keeping credentials out of shared forms, screenshots and public files.

Inspect the generated headshot before emailing it

Replicate generation starts at 6:00 and Gmail delivery at 10:00. A technically successful generation does not guarantee an accurate likeness. The output should be checked for identity, facial details and suitability for its intended professional use before a delivery step makes it look finished.

1. Compare the generated face, hair, glasses and proportions with the source photo.
2. Inspect the crop, clothing and background at the size the user will actually see.
3. Check the email destination and the exact image being attached or linked so one submission cannot receive another record’s result.
4. Open the delivered image and compare it with the reviewed output rather than accepting the email-node status alone.

Verify cleanup and the real cost of the workflow

Cloudinary deletion appears at 12:00, followed by a SaaS discussion at 14:00. Deleting a stored asset is one data-management step, not independent proof of security compliance or deletion from every service. The title’s $0.04-per-image figure is historical and does not establish a current all-in operating price.

1. Identify the original upload, generated output and any other retained copies before deciding what cleanup should remove.
2. Check the actual deletion result and preserve only the records required for the intended service.
3. Track generation, storage and delivery usage separately when estimating a real deployment.
4. Use the original recording for the promised template’s retrieval route; the description supplies no direct workflow-download URL or complete generation prompt.

The takeaway

The useful service is a correctly matched portrait and delivery, with explicit retention decisions and checked cleanup rather than a low headline image price.