http request and get photo for testing purposes
Configured with HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Transform
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Upload photo | Web / API | HTTP Request | PUT |
| Set config (sensitive data) | Transform | Edit Fields | See node parameters |
| Get photo (for testing purposes) | Web / API | HTTP Request | See node parameters |
| Set destination | Transform | Edit Fields | See node parameters |
| Authentication | Web / API | HTTP Request | POST |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Prerequisites
Prerequisites
- Create an application user
- Ensure the following permissions are set:
- Sites.ReadWrite.All - for SharePoint site access
- Files.ReadWrite.All - for file upload operations
Authentication
Authentication
For a succesful authentication it is required to provide:
- TENANT_ID
- CLIENT_ID
- CLIENT_SECRET
Attention!
For demonstration purposes and template restrictions we store these values in a 'Set' node but in production environment please ensure safety of such data via utilizing credentials, secure vault or any other safe way of storing such information.
Set destination
Set destination
In this step we will set the destination. The destination is made of two parameters:
- TARGET_FOLDER
- FILE_NAME
Example
Let's say this is our desired file location:
https://contoso.sharepoint.com/uploads/pictures from n8n/example.jpg
Thus we will set the following:
- TARGET_FOLDER =
/uploads/pictures from n8n - FILE_NAME =
example.jpg
Authentication
Get an access token for graph API
http request and get photo for testing purposes
http request and get photo for testing purposes
Purpose and structure
This folder contains the http request and get photo for testing purposes workflow. Its executable nodes use 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/0886_Manual_Stickynote_Import_Webhook.json MIT; preserve source notices.