OpenRuna
Sign in
← Workflows

0446_Code_Todoist_Create_Scheduled

13 nodes · todoist, filter, schedule

Engine
n8n
Nodes
13
Trigger
scheduled/triggered
Source file
0446_Code_Todoist_Create_Scheduled.json

Workflow flow

IntegrationsTodoistFilterScheduleCodeIF
100%
TRIGGER

Every day at 5:10am

Schedule

TRIGGER

Every day at 5am

Schedule

Get all tasks from template project

Todoist

Get all tasks from Inbox

Todoist

Parse task details

Code

If list not empty

IF

Keep tasks that match today

Filter

if it has daily label

IF

Delete task

Todoist

Create new task in Inbox

Todoist

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

Browse by integration

todoistfilterschedule
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

0446_Code_Todoist_Create_Scheduled (13-node n8n automation, todoist, filter, schedule) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

This n8n workflow, "0446_Code_Todoist_Create_Scheduled", wires together todoist, filter, schedule in 13 nodes. 13 nodes · todoist, filter, schedule 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 13-node flow from scratch.
  • Benchmark it against your current todoist integration to spot missing steps or redundant nodes.
  • Import "0446_Code_Todoist_Create_Scheduled" into n8n, reconnect credentials for todoist, filter, schedule, and run the same automation in your own workspace.
  • Use it as a starting template when wiring todoist, filter, schedule — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "0446_Code_Todoist_Create_Scheduled" exposes 13 configured nodes. Trigger type: scheduled/triggered. Integrations: todoist, filter, schedule. Reconnect the todoist 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

Ask Claude to turn the "0446_Code_Todoist_Create_Scheduled" JSON into a plain-English runbook, node by node. It can flag where todoist 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 todoist, filter, schedule. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0446_Code_Todoist_Create_Scheduled" — extract todoist IDs and secrets into environment variables without changing the 13-node structure.

Frequently asked questions

How do I import "0446_Code_Todoist_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 "0446_Code_Todoist_Create_Scheduled" use?
It uses: todoist, filter, schedule. The flow diagram above shows how each service connects across the 13 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 todoist and filter credentials in n8n after import.
What trigger type does "0446_Code_Todoist_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 "0446_Code_Todoist_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 todoist, filter, schedule.

Related resources