Monitor Bluesky keyword posts with Apify and data tables
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on a schedule (every hour) (plus 1 other trigger). Along the way it connects Apify (community).
How it runs
Trigger: On a schedule (every hour) (plus 1 other trigger).
- Start Bluesky Monitoring (Apify): run task (actor tasks)
- Check for Dataset Availability (If): checks a condition and branches into true / false
- Retrieve Monitoring Data (Apify): get items (datasets)
- Handle Missing Dataset Report (Code): runs custom JavaScript code
- Process Dataset Records (Code): runs custom JavaScript code
- Verify Dataset Records (If): checks a condition and branches into true / false
- Upsert New Posts (Data table): create or update (row)
- Generate Ingestion Report (Code): runs custom JavaScript code
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Start Bluesky Monitoring, Retrieve Monitoring Data).
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Apify
@apify/n8n-nodes-apify.apify - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Data table
n8n-nodes-base.dataTable
From the author
Quick overview This workflow runs an Apify Bluesky monitoring Task on a schedule, fetches the resulting dataset of matched posts, normalizes each record, and upserts it into an n8n Data Table to prevent duplicates across runs. How it works 1. Runs manually or…