OpenRuna
Sign in
← Workflows

1658_Splitout_Schedule_Monitor_Scheduled

19 nodes · splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch

Engine
n8n
Nodes
19
Trigger
scheduled/triggered
Source file
1658_Splitout_Schedule_Monitor_Scheduled.json

Workflow flow

IntegrationsSplit OutLmChatOpenAiInformationExtractorSplitInBatchesAirtableSwitchGraphqlScheduleRemoveDuplicatesSlack@n8n/n8n-nodes-langchain.lmChatOpenAiSet+1 more
100%

OpenAI Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenAi

TRIGGER

Airtable Trigger

Airtable

TRIGGER

Schedule Trigger

Schedule

Sentiment Transition

Switch

Fetch Active Linear Issues

Graphql

Issues to List

Split Out

Deduplicate Notifications

RemoveDuplicates

Sentiment over Issue Comments

@n8n/n8n-nodes-langchain.informationExtractor

Report Issue Negative Transition

Slack

Combine Sentiment Analysis

Set

Copy of Issue

Set

Get Existing Sentiment

Airtable

Update Row

Airtable

For Each Issue...

SplitInBatches

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

Browse by integration

splitOutlmChatOpenAiinformationExtractorsplitInBatchesairtableswitchgraphqlscheduleremoveDuplicatesslack
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

1658_Splitout_Schedule_Monitor_Scheduled (19-node n8n automation, splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "1658_Splitout_Schedule_Monitor_Scheduled" chains 19 nodes to move data between splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule. 19 nodes · splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch 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

  • Study how data moves from splitOut to lmChatOpenAi before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the splitOut stack.
  • Import "1658_Splitout_Schedule_Monitor_Scheduled" into n8n, reconnect credentials for splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule, and run the same automation in your own workspace.
  • Use it as a starting template when wiring splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "1658_Splitout_Schedule_Monitor_Scheduled" exposes 19 configured nodes. Trigger type: scheduled/triggered. Integrations: splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule. Open each node after import to map credentials to your own splitOut and lmChatOpenAi 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 "1658_Splitout_Schedule_Monitor_Scheduled" JSON into a plain-English runbook, node by node. It can flag where splitOut 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 splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "1658_Splitout_Schedule_Monitor_Scheduled" — extract splitOut IDs and secrets into environment variables without changing the 19-node structure.

Frequently asked questions

How do I import "1658_Splitout_Schedule_Monitor_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 "1658_Splitout_Schedule_Monitor_Scheduled" use?
It uses: splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule. The flow diagram above shows how each service connects across the 19 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 splitOut and lmChatOpenAi credentials in n8n after import.
What trigger type does "1658_Splitout_Schedule_Monitor_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 "1658_Splitout_Schedule_Monitor_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 splitOut, lmChatOpenAi, informationExtractor, splitInBatches, airtable, switch, graphql, schedule.

Related resources