OpenRuna
Sign in
← Workflows

0387_Redis_Code_Create_Scheduled

23 nodes · manual, httpRequest, schedule, redis, microsoftTeams

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
0387_Redis_Code_Create_Scheduled.json

Workflow flow

IntegrationsManualHTTPScheduleRedisMicrosoftTeamsSetMergeCode
100%
TRIGGER

When clicking "Execute Workflow"

Manual

TRIGGER

Schedule Trigger

Schedule

Get Meraki Organizations

HTTP

Get Org Name & ID

Set

Get Uplink Loss and Latency

HTTP

Get Network IDs

HTTP

Sets Network Variables

Set

Combine latency to its respective Network

Merge

Makes Latency and Loss Filterable

Set

Average Latency & Loss over 5m

Code

Filters Problematic sites

Code

Check if Alert Exists

Redis

Create Response

Code

Merge

Merge

Message Techs

MicrosoftTeams

Log the Alert

Redis

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

Browse by integration

manualhttpRequestscheduleredismicrosoftTeams
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. 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: 0387_Redis_Code_Create_Scheduled. 23 nodes across manual, httpRequest, schedule, redis, microsoftTeams, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"0387_Redis_Code_Create_Scheduled" automates a manual-to-httpRequest flow in n8n across 23 nodes. 23 nodes · manual, httpRequest, schedule, redis, microsoftTeams A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. 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

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

Example output

Imported into n8n, "0387_Redis_Code_Create_Scheduled" exposes 23 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, httpRequest, schedule, redis, microsoftTeams. Reconnect the manual credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "0387_Redis_Code_Create_Scheduled" into Claude and ask it to explain each of the 23 nodes. Claude is good at suggesting credential mappings for manual, httpRequest, schedule, redis, microsoftTeams, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0387_Redis_Code_Create_Scheduled" to your accounts — which manual, httpRequest, schedule, redis, microsoftTeams credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 23 nodes.

Frequently asked questions

How do I import "0387_Redis_Code_Create_Scheduled" 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 "0387_Redis_Code_Create_Scheduled" use?
It uses: manual, httpRequest, schedule, redis, microsoftTeams. The flow diagram above shows how each service connects across the 23 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 "0387_Redis_Code_Create_Scheduled" 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 "0387_Redis_Code_Create_Scheduled" 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, schedule, redis, microsoftTeams.

Related resources