← All N8N workflows
Automation & utilitiesCronFunctionFunction ItemGoogle DriveHTTP Request

move binary data and http request and get workflow list

Configured with Cron, Function, Function Item, Google Drive, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerOn clicking 'execute'Manual TriggerTransformMergeMergeTransformMove Binary DataMove Binary DataCodeMapFunctionWeb / APIGet WorkflowHTTP RequestWeb / APIGet Workflow ListHTTP RequestCodeFunctionItemFunction ItemFiles / mediaGoogle DriveGoogle DriveTriggerRun Daily at 2:30amCron

Node categories in this workflow

  • Trigger
  • Transform
  • Code
  • Web / API
  • 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
On clicking 'execute'TriggerManual TriggerSee node parameters
MergeTransformMergeSee node parameters
Move Binary DataTransformMove Binary DataSee node parameters
MapCodeFunctionSee node parameters
Get WorkflowWeb / APIHTTP RequestSee node parameters
Get Workflow ListWeb / APIHTTP RequestSee node parameters
FunctionItemCodeFunction ItemSee node parameters
Google DriveFiles / mediaGoogle DriveSee node parameters
Run Daily at 2:30amTriggerCronSee 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

  • googleApi
  • httpBasicAuth

Workflow notes

Get Workflow

Don't forget to add your credentials for your n8n instance in this Node. Use Basic Auth for this.

move binary data and http request and get workflow list

move binary data and http request and get workflow list

Purpose and structure

This folder contains the move binary data and http request and get workflow list workflow. Its executable nodes use cron, function, functionItem, googleDrive, httpRequest, manualTrigger, merge, moveBinaryData. 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 clicking 'execute', Run Daily at 2:30am

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/Functionitem/0068_Functionitem_Manual_Import_Scheduled.json MIT; preserve source notices.

More in Automation & utilities