write binary file and read binary file and http request
Configured with Cron, Function, Function Item, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Files / media
- Web / API
- Messaging
- Transform
- Code
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 |
|---|---|---|---|
| On clicking 'execute' | Trigger | Manual Trigger | See node parameters |
| Write Binary File | Files / media | Write Binary File | See node parameters |
| Read Binary File | Files / media | Read Binary File | See node parameters |
| HTTP Request | Web / API | HTTP Request | See node parameters |
| Telegram | Messaging | Telegram | See node parameters |
| Binary to json | Transform | Move Binary Data | See node parameters |
| Json to binary | Transform | Move Binary Data | See node parameters |
| Set new update time | Code | Function Item | See node parameters |
| Split into baches | Code | Function | See node parameters |
| Cron | Trigger | Cron | See node parameters |
| Config | Transform | Edit Fields | See node parameters |
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
httpHeaderAuthtelegramApi
Workflow notes
write binary file and read binary file and http request
write binary file and read binary file and http request
Purpose and structure
This folder contains the write binary file and read binary file and http request workflow. Its executable nodes use cron, function, functionItem, httpRequest, manualTrigger, moveBinaryData, readBinaryFile, set, telegram, writeBinaryFile. 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', Cron
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/Telegram/0158_Telegram_Functionitem_Create_Scheduled.json MIT; preserve source notices.