OpenRuna
Sign in
← Workflows

0819_Splitout_Schedule_Create_Scheduled

36 nodes · schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi

Engine
n8n
Nodes
36
Trigger
scheduled/triggered
Source file
0819_Splitout_Schedule_Create_Scheduled.json

Workflow flow

IntegrationsScheduleEmbeddingsOpenAiDocumentDefaultDataLoaderTextSplitterRecursiveCharacterTextSplitterVectorStoreSupabaseLmChatOpenAiAgentJiraSplitInBatchesRemoveDuplicatesSplit OutInformationExtractor+12 more
100%
TRIGGER

Schedule Trigger

Schedule

Embeddings OpenAI

@n8n/n8n-nodes-langchain.embeddingsOpenAi

Default Data Loader

@n8n/n8n-nodes-langchain.documentDefaultDataLoader

Recursive Character Text Splitter

@n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter

Supabase Vector Store

@n8n/n8n-nodes-langchain.vectorStoreSupabase

Embeddings OpenAI1

@n8n/n8n-nodes-langchain.embeddingsOpenAi

OpenAI Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenAi

TRIGGER

Schedule Trigger1

Schedule

OpenAI Chat Model1

@n8n/n8n-nodes-langchain.lmChatOpenAi

Get Unassigned Tickets more than 5 days

Jira

Last 50 Resolved

Jira

Remove Duplicates

RemoveDuplicates

Collect Fields

Set

Issues Similarity Database

@n8n/n8n-nodes-langchain.vectorStoreSupabase

Issues to Items

Split Out

Issue Ref

NoOp

Tally In-Progress Issues per User

Set

Sort By Most Capacity

Sort

If has Items?

IF

Find Similar Issues + Assignees

@n8n/n8n-nodes-langchain.agent

For Each User

SplitInBatches

Assign User to Ticket

Jira

Skip

NoOp

Check User Workflow

Jira

For Each Issue

SplitInBatches

Add Comment to Issue

Jira

To Structured Output

@n8n/n8n-nodes-langchain.informationExtractor

Count Assigned Open Issues per User

Summarize

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

Browse by integration

scheduleembeddingsOpenAidocumentDefaultDataLoadertextSplitterRecursiveCharacterTextSplittervectorStoreSupabaselmChatOpenAiagentjirasplitInBatchesremoveDuplicatessplitOutinformationExtractorsummarizesort
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: 0819_Splitout_Schedule_Create_Scheduled. 36 nodes across schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi, agent, jira, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "0819_Splitout_Schedule_Create_Scheduled" chains 36 nodes to move data between schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi, agent, jira. 36 nodes · schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi 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 36-node flow from scratch.
  • Benchmark it against your current schedule integration to spot missing steps or redundant nodes.
  • Study how data moves from schedule to embeddingsOpenAi before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the schedule stack.

Example output

Imported into n8n, "0819_Splitout_Schedule_Create_Scheduled" exposes 36 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi, agent, jira. Set your credentials on the schedule 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 "0819_Splitout_Schedule_Create_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, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi, agent, jira. Handy for onboarding teammates new to n8n.

Cursor

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

Frequently asked questions

How do I import "0819_Splitout_Schedule_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 "0819_Splitout_Schedule_Create_Scheduled" use?
It uses: schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi, agent, jira. The flow diagram above shows how each service connects across the 36 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 embeddingsOpenAi credentials in n8n after import.
What trigger type does "0819_Splitout_Schedule_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 "0819_Splitout_Schedule_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 schedule, embeddingsOpenAi, documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, vectorStoreSupabase, lmChatOpenAi, agent, jira.

Related resources