← All N8N workflows
Automation & utilitiesExtract From FileHTTP RequestManual TriggerEdit Fields

http request and binarytopropery extract from file

Configured with Extract From File, HTTP Request. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking "Testworkflow"Manual TriggerTransformCompose messageEdit FieldsWeb / APISend messageHTTP RequestWeb / APIGet imageHTTP RequestTransformMessage settingsEdit FieldsTransformConvert image to base64Extract From File

Node categories in this workflow

  • Trigger
  • Transform
  • Web / API

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
Compose messageTransformEdit FieldsSee node parameters
Send messageWeb / APIHTTP RequestPOST
Get imageWeb / APIHTTP RequestSee node parameters
Message settingsTransformEdit FieldsSee node parameters
Convert image to base64TransformExtract From FilebinaryToPropery

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

Workflow notes

Sticky Note

Gets a random image from the internet. Replace this with your image (should be called 'data')

Sticky Note1

We use an HTTP node rather than the Gmail node. Add your Gmail creds here

Sticky Note2

To use the image in the body of the email, insert

Try me out

Try me out

  1. Make sure you add your Gmail credential in the last node
  2. Update the sender and recipient in the 'Message settings' node
  3. Click 'test workflow'
http request and binarytopropery extract from file

http request and binarytopropery extract from file

Purpose and structure

This folder contains the http request and binarytopropery extract from file workflow. Its executable nodes use extractFromFile, httpRequest, manualTrigger, set. 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"

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/Manual/0501_Manual_Extractfromfile_Send_Webhook.json MIT; preserve source notices.

More in Automation & utilities