← All N8N workflows
Messaging & emailConvert To FileExtract From FileFormForm TriggerGmail

split out and http request and receive form events

Configured with Convert To File, Extract From File, Form, Form Trigger, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TransformSplit OutSplit OutWeb / APIImagen 3.0HTTP RequestTransformVariablesEdit FieldsWeb / APIDownload ImageHTTP RequestTriggerOn form submissionForm TriggerRoutingForm ValidationIfIntegrationRetry FormFormWeb / APIUpload to CloudinaryHTTP RequestTransformConvert to File1Convert To FileTransformGenerate HTMLHtmlTransformConvert to FileConvert To FileIntegrationForm EndingFormRoutingHas Email?IfMessagingSend Results to EmailGmailTransformImage to Base64Extract From FileWeb / APIGemini 2.0HTTP Request

Node categories in this workflow

  • Transform
  • Web / API
  • Trigger
  • Routing
  • Integration
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Split OutTransformSplit OutSee node parameters
Imagen 3.0Web / APIHTTP RequestPOST
VariablesTransformEdit FieldsSee node parameters
Download ImageWeb / APIHTTP RequestSee node parameters
On form submissionTriggerForm TriggerSee node parameters
Form ValidationRoutingIfSee node parameters
Retry FormIntegrationFormSee node parameters
Upload to CloudinaryWeb / APIHTTP RequestPOST
Convert to File1TransformConvert To FiletoText
Generate HTMLTransformHtmlSee node parameters
Convert to FileTransformConvert To FiletoBinary
Form EndingIntegrationFormcompletion
Has Email?RoutingIfSee node parameters
Send Results to EmailMessagingGmailSee node parameters
Image to Base64TransformExtract From FilebinaryToPropery
Gemini 2.0Web / APIHTTP RequestPOST

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • gmailOAuth2
  • googlePalmApi
  • httpQueryAuth

Workflow notes

1. Ask for Source Style and Target Image

1. Ask for Source Style and Target Image

Learn more about the Form Trigger

We'll use a form interface for this template which allows the users to specify an image whose style we'll use as reference and a prompt to generate the target image. Form validation loop can be achieved by combining another form node with the IF node.

2. Visual Style Description using Gemini 2.0

2. Visual Style Description using Gemini 2.0

Read more about Gemini Image Understanding

The trick to copying the style of an image is to get a multimodal LLM to describe it in detail. Using Gemini's image understanding capabilities, it can do a pretty good job to provide the comprehensive description we need.

3. Image Generation using Imagen 3.0

3. Image Generation using Imagen 3.0

Read more about Imagen Image Generation

To generate the image, we'll be using Google's Imagen 3.0 model. We'll combine the visual style description generated in the previous Gemini model with the user's target image prompt and pass this to Imagen to do its magic! The result is something very close to style transfer which produces quite convincing and impressive results.

4. Render Results to HTML Page

4. Render Results to HTML Page

Learn more about the HTML node

Finally for presentation, we'll render the generated images as a webpage for easier viewing using the HTML node. This page can then be sent to the user's email if provided and downloaded as a file once we land on the form ending node.

Try It Out!

Try It Out!

This n8n template allows you to use AI to generate logos or images which mimic visual styles of other logos or images. The model used to generate the images is Google's Imagen 3.0.

With this template, users will be able to automate design and marketing tasks such as creating variants of existing designs, remixing existing assets to validate different styles and explore a range of designs which would have been otherwise too expensive and time-consming previously.

How it works

  • A form trigger is used to capture the source image to reference styles from and a prompt for the target image to generate.
  • The source image is passed to Gemini 2.0 to be analysed and its visual style and tone extracted as a detailed description.
  • This visual style description is then combined with the user's initial target image prompt. This final prompt is given to Imagen 3.0 to generate the images.
  • A quick webpage is put together with the generated images to present back to the user.
  • If the user provided an email address, a copy of this HTML page will be sent.

How to use

  • Ensure the workflow is live to share the form publicly.
  • The source image must be accessible to your n8n instance - either a public image of the internet or within your network.

Requirements

  • Gemini for LLM and Imagen model.
  • Cloudinary for image CDN.
  • Gmail for email sending.

Customising this workflow

  • Feel free to swap any of these out for tools and services you prefer.
  • Want to fully automate? Switch the form trigger for a webhook trigger!

Need Help?

Join the Discord or ask in the Forum!

Happy Hacking!

split out and http request and receive form events

split out and http request and receive form events

Purpose and structure

This folder contains the split out and http request and receive form events workflow. Its executable nodes use convertToFile, extractFromFile, form, formTrigger, gmail, html, httpRequest, if, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

On form submission

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/0919_Splitout_Extractfromfile_Create_Webhook.json MIT; preserve source notices.

More in Messaging & email