OpenRuna
Sign in
← Workflows

Create Threads on Bluesky

20 nodes · httpRequest, schedule, splitInBatches, wait

Engine
n8n
Nodes
20
Trigger
scheduled/triggered
Source file
1135_Wait_Code_Create_Webhook.json

Workflow flow

IntegrationsHTTPScheduleSplitInBatchesWaitSetCode
100%
TRIGGER

Run Daily at 9 AM

Schedule

Set Bluesky Credentials

Set

Create Bluesky Session

HTTP

Create Post Text

Code

Create Initial Post

HTTP

Create Reply Text

Code

Create Reply

HTTP

Create Sibling Text

Code

Create Sibling

HTTP

Create Sibling Array

Code

Loop Posts

SplitInBatches

Create Sibling Text (Loop)

Code

Create Post

HTTP

Wait

Wait

14 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

Create Threads on Bluesky is a free n8n workflow on OpenRuna — 20 nodes connecting httpRequest, schedule, splitInBatches, wait. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "Create Threads on Bluesky" chains 20 nodes to move data between httpRequest, schedule, splitInBatches, wait. 20 nodes · httpRequest, schedule, splitInBatches, wait It starts from a scheduled/triggered trigger and routes data through every node in order. 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

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

Example output

Imported into n8n, "Create Threads on Bluesky" exposes 20 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, schedule, splitInBatches, wait. Reconnect the httpRequest 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 "Create Threads on Bluesky" JSON into a plain-English runbook, node by node. It can flag where httpRequest 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 httpRequest, schedule, splitInBatches, wait. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Create Threads on Bluesky" — extract httpRequest IDs and secrets into environment variables without changing the 20-node structure.

Frequently asked questions

How do I import "Create Threads on Bluesky" 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 "Create Threads on Bluesky" use?
It uses: httpRequest, schedule, splitInBatches, wait. The flow diagram above shows how each service connects across the 20 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 httpRequest and schedule credentials in n8n after import.
What trigger type does "Create Threads on Bluesky" 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 "Create Threads on Bluesky" 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 httpRequest, schedule, splitInBatches, wait.

Related resources