← All N8N workflows
Data & databasesGoogle DriveGoogle SheetsHTTP RequestIfManual Trigger

Image-to-3D

Configured with Google Drive, Google Sheets, HTTP Request, Schedule Trigger, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerWeb / APIGet statusHTTP RequestWaitWait 60 sec.WaitTriggerSchedule TriggerSchedule TriggerRoutingCompleted?IfData storeUpdate resultGoogle SheetsTransformSet dataEdit FieldsData storeGet new imageGoogle SheetsWeb / APICreate 3D ImageHTTP RequestWeb / APIGet Url 3D imageHTTP RequestWeb / APIGet File 3D imageHTTP RequestFiles / mediaUpload 3D ImageGoogle Drive

Node categories in this workflow

  • Trigger
  • Web / API
  • Wait
  • Routing
  • Data store
  • Transform
  • Files / media

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
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Get statusWeb / APIHTTP RequestSee node parameters
Wait 60 sec.WaitWaitSee node parameters
Schedule TriggerTriggerSchedule TriggerSee node parameters
Completed?RoutingIfSee node parameters
Update resultData storeGoogle Sheetsupdate
Set dataTransformEdit FieldsSee node parameters
Get new imageData storeGoogle SheetsSee node parameters
Create 3D ImageWeb / APIHTTP RequestPOST
Get Url 3D imageWeb / APIHTTP RequestSee node parameters
Get File 3D imageWeb / APIHTTP RequestSee node parameters
Upload 3D ImageFiles / mediaGoogle DriveSee node parameters

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

  • googleDriveOAuth2Api
  • googleSheetsOAuth2Api
  • httpHeaderAuth

Workflow notes

Image-to-3D

Image-to-3D

This workflow allows users to convert a 2D image into a 3D model by integrating multiple AI and web services. The process begins with a user uploading or providing an image URL, which is then sent to a generative AI model capable of interpreting the content and generating a 3D representation in .glb format. The model is then stored and a download link is returned to the user.

STEP 1 - GOOGLE SHEET

STEP 1 - GOOGLE SHEET

Create a Google Sheet like this.

Please insert:

  • in the "IMAGE MODEL" column the basic image of the model to dress

Leave the "3D RESULT" column unfilled. It will be inserted by the system once the image has been created

STEP 3 - MAIN FLOW

STEP 3 - MAIN FLOW

Start the workflow manually or periodically by hooking the "Schedule Trigger" node. It is recommended to set it at 5 minute intervals.

STEP 2 - GET API KEY (YOURAPIKEY)

STEP 2 - GET API KEY (YOURAPIKEY)

Create an account here and obtain API KEY. In the node "Create Image" set "Header Auth" and set:

  • Name: "Authorization"
  • Value: "Key YOURAPIKEY"
Sticky Note7

Set API Key created in Step 2

Image-to-3D

Image-to-3D

Purpose and structure

This folder contains the Image-to-3D workflow. Its executable nodes use googleDrive, googleSheets, httpRequest, if, manualTrigger, scheduleTrigger, set, wait. 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

When clicking ‘Test workflow’, Schedule Trigger

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/Wait/1763_Wait_Schedule_Automation_Webhook.json MIT; preserve source notices.

More in Data & databases