Agent setup guide
Competitor Social Watch
Every Friday: what up to three competitors posted on their own Bluesky accounts and which posts got engagement, as a digest in Notion.
What it does
Every Friday: what up to three competitors posted on their own Bluesky accounts and which posts got engagement, as a digest in Notion.
- Every Friday, reads the 30 newest posts of up to three competitors' own Bluesky accounts from Bluesky's public API (no sign-in).
- Keeps each competitor's own posts from the last 7 days in code, leaving out their replies and reposts. Dates are worked out in code, never by the AI: days until or since each date, the window and business days are computed in your workflow's time zone, and records outside the window are skipped before the AI sees them.
- Works out each post's engagement (likes + reposts + replies + quotes) in code.
- AI writes a digest per competitor (what they posted about, their most engaging post and why it may have worked), the patterns across them and ideas to try in your own way.
- Saves the digest as a page in your Notion database.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Notion, connected in Settings → Integrations, with a database shared with Fluxo Flow.
- Your competitors' public Bluesky handles.
What it doesn't do
- It reads competitors' own posts, not mentions of them (for mentions in the news, see the Brand & Competitor Mention Monitor).
- Bluesky only, up to three accounts and their 30 newest posts each.
- No reach, follower or sales numbers: only what their public posts show.
- It never likes, follows, replies or posts.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.
Before you start
- A paid plan: agents run live, and the Free plan only runs Dry Runs.
- An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
- These apps, connected in Settings → Integrations: Notion.
- Nothing to send: the agent runs on a schedule.
- About 10 minutes.
Set it up step by step
Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.
1. Connect your AI provider
The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
2. Connect Notion
Connect the Notion workspace with your digest database (Settings → Integrations → Notion).
3. Your competitors' handles
Open the three “Read competitor …'s posts” steps and replace the placeholders in the addresses with their Bluesky handles.
| Setting | What to enter | In step |
|---|---|---|
| Competitor 1's Bluesky handle | In the address, replace COMPETITOR_1_HANDLE with the competitor's Bluesky handle, e.g. rivalbakery.bsky.social. It starts as “COMPETITOR_1_HANDLE” until you replace it. | “Read competitor 1's posts” |
| Competitor 2's Bluesky handle | In the address, replace COMPETITOR_2_HANDLE with the competitor's Bluesky handle, e.g. rivalbakery.bsky.social. Watching fewer than three? Enter one of the others again; each account is listed once. It starts as “COMPETITOR_2_HANDLE” until you replace it. | “Read competitor 2's posts” |
| Competitor 3's Bluesky handle | In the address, replace COMPETITOR_3_HANDLE with the competitor's Bluesky handle, e.g. rivalbakery.bsky.social. Watching fewer than three? Enter one of the others again; each account is listed once. It starts as “COMPETITOR_3_HANDLE” until you replace it. | “Read competitor 3's posts” |
4. Describe your business
Open “Write the weekly digest” and replace the placeholder.
| Setting | What to enter | In step |
|---|---|---|
| Your business and competitors | Replace the placeholder with your business, what you sell, and who each competitor is and what you want to learn. It starts as “[YOUR BUSINESS, WHAT YOU SELL, AND FOR EACH COMPETITOR HANDLE BELOW: WHO THEY ARE AND WHAT YOU WANT TO LEARN FROM WATCHING THEM]” until you replace it. | “Write the weekly digest” |
5. Pick the digest database
Open “Save the digest in Notion” and pick the account and database.
| Setting | What to enter | In step |
|---|---|---|
| Notion account | The Notion workspace with your digest database. Pick your connected Notion account. | “Save the digest in Notion” |
| Digest database | The Notion database for the weekly digests (a title property is enough). Share it with Fluxo Flow (••• → Connections). | “Save the digest in Notion” |
6. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
7. Switch the trigger on
Open the trigger, set your time zone and switch the schedule on. It runs every Friday at 9:00.
How it works
The agent is a normal workflow with 13 steps (1 AI step). You can open, edit and monitor it like any other workflow.
- Fridays at 9:00 — Runs on a schedule (cron 0 9 * * 5, UTC — change it in the trigger's settings). Runs every Friday morning and covers your competitors' posts of the last 7 days. Set your time zone on the trigger.
- Read competitor 1's posts — Calls a web address (HTTP request). Reads competitor 1's 30 newest Bluesky posts (their own account, replies left out) from Bluesky's public API, with like, repost, reply and quote counts.
- Competitor 1: last 7 days — Step. In code, not AI: keeps the account's own posts from the last 7 days (today included, in your time zone); reposts of other people's posts are left out.
- Competitor 1: engagement per post — Step. In code, not AI: each post's engagement (likes + reposts + replies + quotes).
- Read competitor 2's posts — Calls a web address (HTTP request). Reads competitor 2's 30 newest Bluesky posts (their own account, replies left out) from Bluesky's public API, with like, repost, reply and quote counts.
- Competitor 2: last 7 days — Step. In code, not AI: keeps the account's own posts from the last 7 days (today included, in your time zone); reposts of other people's posts are left out.
- Competitor 2: engagement per post — Step. In code, not AI: each post's engagement (likes + reposts + replies + quotes).
- Read competitor 3's posts — Calls a web address (HTTP request). Reads competitor 3's 30 newest Bluesky posts (their own account, replies left out) from Bluesky's public API, with like, repost, reply and quote counts.
- Competitor 3: last 7 days — Step. In code, not AI: keeps the account's own posts from the last 7 days (today included, in your time zone); reposts of other people's posts are left out.
- Competitor 3: engagement per post — Step. In code, not AI: each post's engagement (likes + reposts + replies + quotes).
- Write the weekly digest — AI step (runs on your AI provider key). AI reads each competitor's posts of the week (engagement counted in code) and writes what they posted about, which posts got the most engagement, and what you could learn from it.
- Save the digest in Notion — Notion: Create a page in a database. Creates a page in your Notion database with this week's competitor digest.
- Digest saved — Kept in the run history. Read it in Notion; nothing was posted.
Test it with Dry Run
Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
Go live
- Open the trigger, set your time zone and switch the schedule on. It runs every Friday at 9:00.
- Scheduled runs start only once the schedule is activated, and can't repeat faster than your plan's minimum interval.
- The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
- When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.
Questions
How is this different from the Brand & Competitor Mention Monitor?
That agent reads news and alert feeds for mentions of you and your competitors. This one reads the competitors' own Bluesky accounts: what they posted and what got engagement.
Can it watch Instagram, TikTok or Mastodon accounts?
Not today: it reads public Bluesky accounts, which need no sign-in.
Does it need their permission?
It reads only public posts that anyone can see on Bluesky, and never interacts with them.
Troubleshooting
- “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
- A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
- An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
- It didn't run at the expected time: the schedule must be activated, and its time is in the trigger's timezone.
- A step failed: open the run in History and check that step in the Trace tab for the error and what it received.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .