Which integrations does "Store the data received from the CocktailDB API in JSON" use?

It uses: manual, httpRequest, moveBinaryData, writeBinaryFile. The flow diagram above shows how each service connects across the 4 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.

What trigger type does "Store the data received from the CocktailDB API in JSON" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

← Workflows

Store the data received from the CocktailDB API in JSON

4 nodes · manual, httpRequest, moveBinaryData, writeBinaryFile

Engine: n8n
Nodes: 4
Trigger: scheduled/triggered
Source file: 1089_Manual_Writebinaryfile_Automation_Webhook.json

Workflow flow

IntegrationsManualHTTPMoveBinaryDataWriteBinaryFile

100%

TRIGGER

On clicking 'execute'

Manual

HTTP Request

HTTP

Move Binary Data

MoveBinaryData

Write Binary File

WriteBinaryFile

4 steps · flows top to bottom, branches left to right

Browse by integration

manual httpRequest moveBinaryData writeBinaryFile

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Store the data received from the CocktailDB API in JSON. 4 nodes across manual, httpRequest, moveBinaryData, writeBinaryFile, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Store the data received from the CocktailDB API in JSON" chains 4 nodes to move data between manual, httpRequest, moveBinaryData, writeBinaryFile. 4 nodes · manual, httpRequest, moveBinaryData, writeBinaryFile It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Fork it to add error handling, retries, or a notification step without designing the 4-node flow from scratch.
Benchmark it against your current manual integration to spot missing steps or redundant nodes.
Study how data moves from manual to httpRequest before building your own variant.
Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.

Example output

Imported into n8n, "Store the data received from the CocktailDB API in JSON" exposes 4 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, httpRequest, moveBinaryData, writeBinaryFile. Set your credentials on the manual node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Store the data received from the CocktailDB API in JSON" JSON into a plain-English runbook, node by node. It can flag where manual rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for manual, httpRequest, moveBinaryData, writeBinaryFile. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Store the data received from the CocktailDB API in JSON" — extract manual IDs and secrets into environment variables without changing the 4-node structure.

Frequently asked questions

How do I import "Store the data received from the CocktailDB API in JSON" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Store the data received from the CocktailDB API in JSON" use?: It uses: manual, httpRequest, moveBinaryData, writeBinaryFile. The flow diagram above shows how each service connects across the 4 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.
What trigger type does "Store the data received from the CocktailDB API in JSON" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Store the data received from the CocktailDB API in JSON" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, httpRequest, moveBinaryData, writeBinaryFile.