OpenRuna
Sign in
← Workflows

1428_Code_Schedule_Send_Scheduled

32 nodes · schedule, airtable, gmail, executeWorkflow, form, filter

Engine
n8n
Nodes
32
Trigger
scheduled/triggered
Source file
1428_Code_Schedule_Send_Scheduled.json

Workflow flow

IntegrationsScheduleAirtableGmailExecuteWorkflowFormFilterExecutionDataMemoryBufferWindowToolWikipediaAgentLmChatGroqOpenAI+8 more
100%
TRIGGER

Schedule Trigger

Schedule

TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

TRIGGER

Unsubscribe Form

Form

TRIGGER

Subscribe Form

Form

Window Buffer Memory

@n8n/n8n-nodes-langchain.memoryBufferWindow

Wikipedia

@n8n/n8n-nodes-langchain.toolWikipedia

Groq Chat Model

@n8n/n8n-nodes-langchain.lmChatGroq

Search daily

Airtable

Search weekly

Airtable

Search surprise

Airtable

Create Subscriber

Airtable

Update Subscriber

Airtable

Execution Data

ExecutionData

confirmation email1

Gmail

Should Send?

Code

Content Generation Agent

@n8n/n8n-nodes-langchain.agent

Should Send = True

Filter

Generate Image

@n8n/n8n-nodes-langchain.openAi

Create Event

Set

Resize Image

EditImage

Execute Workflow

ExecuteWorkflow

Set Email Vars

Set

Send Message

Gmail

Log Last Sent

Airtable

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

Browse by integration

Browse all integrations →

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: 1428_Code_Schedule_Send_Scheduled. 32 nodes across schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "1428_Code_Schedule_Send_Scheduled" chains 32 nodes to move data between schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow. 32 nodes · schedule, airtable, gmail, executeWorkflow, form, filter Execution begins at the scheduled/triggered trigger and flows through the 32 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Study how data moves from schedule to airtable before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the schedule stack.
  • Import "1428_Code_Schedule_Send_Scheduled" into n8n, reconnect credentials for schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow, and run the same automation in your own workspace.
  • Use it as a starting template when wiring schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "1428_Code_Schedule_Send_Scheduled" exposes 32 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow. Open each node after import to map credentials to your own schedule and airtable accounts. 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 "1428_Code_Schedule_Send_Scheduled" JSON into a plain-English runbook, node by node. It can flag where schedule 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 schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "1428_Code_Schedule_Send_Scheduled" — extract schedule IDs and secrets into environment variables without changing the 32-node structure.

Frequently asked questions

How do I import "1428_Code_Schedule_Send_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 "1428_Code_Schedule_Send_Scheduled" use?
It uses: schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow. The flow diagram above shows how each service connects across the 32 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 schedule and airtable credentials in n8n after import.
What trigger type does "1428_Code_Schedule_Send_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 "1428_Code_Schedule_Send_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 schedule, airtable, gmail, executeWorkflow, form, filter, executionData, memoryBufferWindow.

Related resources