AI Image Generation and Google Drive Upload Automation using APImage - n8n Workflow

• Content creators needing fast, automated image generation.


• Marketing teams requiring instant storage of AI-generated assets.


• Developers seeking reliable n8n templates for integrating third-party AI services.


• Users looking to understand how to handle file binary data within an n8n workflow.

Creating high volumes of unique images manually is time-consuming. This powerful n8n workflow template solves this by providing a simple form interface to request AI-generated images and automatically saving them to your cloud storage.

By leveraging the specialized Form Trigger as the starting n8n trigger, users can quickly input their prompt and parameters. The n8n node configuration then handles the complex process of communicating with the APImage API, downloading the resulting image file, and securely uploading it to Google Drive. This ensures a seamless, hands-free automation experience. This specific n8n workflow demonstrates best practices for managing binary file handling in n8n.

This automation is initiated by a user-friendly form and proceeds through several critical steps using dedicated n8n nodes:

1. Start with an n8n Trigger: The Generate Image n8n node, configured as a Form Trigger, serves as the initial n8n trigger. Users submit their desired image description, dimensions (Square, Landscape, Portrait), and AI model (Basic, Premium).


2. Call the AI API: The collected data is passed to the APImage API n8n node (an HTTP Request node). This node constructs a POST request, authenticating using a Bearer token, and sends the prompt and parameters to APImage's image generation endpoint.


3. Retrieve Image URL: APImage responds with the URL of the newly created image.


4. Download the File: The Download Image n8n node (another HTTP Request node) dynamically fetches the image URL returned in the previous step. Crucially, this n8n node is configured to output the response as a file property, preparing it for cloud storage.


5. Upload to Google Drive: The final n8n node, Upload file (Google Drive), receives the binary image data and uploads it to the specified Google Drive folder, completing the n8n workflow execution.

To start using this n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON code and import it into your n8n instance via the 'Workflows' section.


2. Configure APImage Credentials: Double-click the APImage API n8n node. Update the Authorization header value, replacing YOURAPIKEY with your actual APImage API key (ensure the Bearer prefix remains).


3. Set Up Google Drive Credentials: Double-click the Upload file Google Drive n8n node. You will need to set up Google Drive credentials if you haven't already. Follow the standard n8n guide for OAuth setup.


4. Activate and Test: Activate the n8n workflow. Access the URL provided by the Generate Image n8n trigger node to submit your first test prompt. Ensure the generated image appears in your Google Drive folder.

This powerful n8n workflow utilizes four primary n8n nodes:

Generate Image (Form Trigger): The starting n8n trigger for the workflow. It presents a web form asking for the image prompt, dimensions (Square, Landscape, Portrait), and model (Basic/Premium).
APImage API (HTTP Request): This n8n node is responsible for communicating with the AI service.
Function: Sends a JSON payload containing the user's prompt and desired parameters to the APImage generation endpoint via a POST request.
Key Configuration: Uses an expression to build the JSON body based on the data from the n8n trigger ({{ $json['Describe the image you want'] }}). Requires a Bearer YOURAPIKEY in the Authorization header.
Download Image (HTTP Request): A critical n8n node for file handling.
Function: Downloads the actual image file from the URL provided by the APImage API response.
Key Configuration: The URL parameter uses the expression ={{ $json.images[0] }}. The response format is set to file, and the output property name is set to generatedimage.
Upload file (Google Drive): The final action n8n node.
Function: Takes the binary file output (generatedimage) from the previous n8n node and uploads it to the configured Google Drive location.
Key Configuration: Specifies the input data field name as generated_image to correctly reference the downloaded file.