Mention & Reply Alerts

What it does

New Bluesky and Mastodon mentions sorted by AI: questions, complaints and partnership asks alerted in Slack, the rest in a daily digest.

• Every 15 minutes, reads your Bluesky notifications (mentions, replies, quotes) and your Mastodon mentions (which include replies to you).
• Skips anything it already handled (remembered for 7 days) and anything older than yesterday, worked out in code.
• AI sorts each new one: question, complaint, partnership, praise, spam or other, with a one-line summary and a suggested next step.
• Questions, complaints and partnership inquiries are posted to your Slack channel at once; every mention is logged to your Google Sheet.
• Once a day, yesterday's log is grouped and counted in code (never by the AI) and posted to Slack as a digest.

What it needs

• A paid plan (agents run live on paid plans).
• An AI provider key (Settings → AI Providers).
• Slack and Google Sheets, connected in Settings → Integrations.
• Bluesky, Mastodon or both, connected in Settings → Integrations (the steps for a network you don't connect are skipped).
• A mentions-log tab with the columns Date | Time | Network | From | Category | Priority | Text | Link | Suggestion.

What it doesn't do

• It doesn't reply, like or delete anything: your team acts on the alerts.
• It isn't instant: notifications are checked every 15 minutes.
• Bluesky and Mastodon only; it reads text, not images.
• It reads the newest 50 Bluesky notifications and 40 Mastodon mentions per run.

Availability and plans

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: Bluesky, Mastodon, Slack and Google Sheets.
• Nothing to send: the agent runs on a schedule.
• About 15 minutes.

• Bring your own AI key
• Bluesky (live)
• Mastodon (live)
• Slack (live)
• Google Sheets (live)

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.

• Connect your AI provider

2. Connect Bluesky, Mastodon or both

Connect the networks you use: Bluesky with your handle and an app password, Mastodon with your server and an access token with the read scope (Settings → Integrations). One is enough; the steps for a network you don't connect are skipped.

• Connecting Bluesky
• Connecting Mastodon

3. Connect Slack

Connect the Slack workspace your team uses (Settings → Integrations → Slack).

• Connecting Slack

4. Connect Google Sheets

Connect the Google account that can open your mentions log (Settings → Integrations → Google Sheets).

• Connecting Google Sheets

5. Pick your Bluesky and/or Mastodon accounts

Open “Read Bluesky notifications” and “Read Mastodon mentions” and pick your accounts. Leave a network empty if you don't use it: its steps are skipped.

6. Pick the Slack channels

Open the two “Alert the team in Slack” steps and “Post the daily digest”, pick the workspace and channels.

7. Pick the mentions log

Open the two “Log it” steps and “Read the mentions log” and pick the same spreadsheet and tab (columns Date | Time | Network | From | Category | Priority | Text | Link | Suggestion).

8. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

• Dry Run vs Run

9. Switch the trigger on

Open the trigger, set your time zone (the daily digest follows it) and switch the schedule on. It runs every 15 minutes.

How it works

The agent is a normal workflow with 38 steps (2 AI steps). You can open, edit and monitor it like any other workflow.

• Every 15 minutes — Runs on a schedule (cron */15 * * * *, UTC — change it in the trigger's settings). Checks your Bluesky and Mastodon notifications every 15 minutes. Set your time zone on the trigger: the daily digest goes out with the first run after midnight in that zone.
• Read Bluesky notifications — Bluesky: Get notifications. Reads the 50 newest Bluesky notifications (mentions, replies, quotes; likes and follows are skipped later). Skipped when Bluesky isn't connected.
• Only today's and yesterday's — Step. In code: keeps notifications from today and yesterday (your time zone), so the first run doesn't alert on old ones.
• Each Bluesky notification — Repeats the steps below for each item (up to 50 per run). One notification at a time (up to 50 per run).
• [For each item — “Each Bluesky notification”] Has text? — Step. In code: mentions, replies and quotes have post text; likes, reposts and follows don't, so they're skipped.
• [For each item — “Each Bluesky notification”] Mention, reply or quote? — Decision: picks the branch to follow. Only posts with text (mentions, replies, quotes) are sorted; likes, reposts and follows are skipped.
• [For each item — “Each Bluesky notification”] Not a mention — Kept in the run history. Branch: Other. Likes, reposts and follows aren't sorted.
• [For each item — “Each Bluesky notification”] Already handled? — Recalls what it remembered earlier (memory “mention-reply-alerts”). Branch: Mention / reply / quote. Remembers which Bluesky posts were already sorted (kept 7 days), so each one is alerted and logged once.
• [For each item — “Each Bluesky notification”] New? — Decision: picks the branch to follow. Already handled: skipped.
• [For each item — “Each Bluesky notification”] Already handled — Kept in the run history. Branch: Already handled. Sorted in an earlier run.
• [For each item — “Each Bluesky notification”] Sort the Bluesky post — AI step (runs on your AI provider key). Branch: New. AI sorts it (question, complaint, partnership, praise, spam, other), sets the priority and suggests a next step.
• [For each item — “Each Bluesky notification”] Important? — Decision: picks the branch to follow. High priority: alert the team now. Low: logged for tomorrow's digest.
• [For each item — “Each Bluesky notification”] Alert the team in Slack — Slack: Post a message. Branch: Important. Posts the mention, its category, who sent it and the suggested next step.
• [For each item — “Each Bluesky notification”] Log it — Google Sheets: Add a row. Branch: Low. Adds a row to your mentions log (Date | Time | Network | From | Category | Priority | Text | Link | Suggestion).
• [For each item — “Each Bluesky notification”] Remember it — Remembers it for later runs (memory “mention-reply-alerts”, kept 7 days). Marks this post as handled for 7 days.
• Read Mastodon mentions — Mastodon: Get notifications. Reads the 40 newest Mastodon mentions (Mastodon counts replies to you as mentions). Skipped when Mastodon isn't connected.
• Only today's and yesterday's — Step. In code: keeps mentions from today and yesterday (your time zone).
• Each Mastodon mention — Repeats the steps below for each item (up to 40 per run). One mention at a time (up to 40 per run).
• [For each item — “Each Mastodon mention”] Already handled? — Recalls what it remembered earlier (memory “mention-reply-alerts”). Remembers which Mastodon mentions were already sorted (kept 7 days).
• [For each item — “Each Mastodon mention”] New? — Decision: picks the branch to follow. Already handled: skipped.
• [For each item — “Each Mastodon mention”] Already handled — Kept in the run history. Branch: Already handled. Sorted in an earlier run.
• [For each item — “Each Mastodon mention”] Sort the Mastodon post — AI step (runs on your AI provider key). Branch: New. AI sorts it (question, complaint, partnership, praise, spam, other), sets the priority and suggests a next step.
• [For each item — “Each Mastodon mention”] Important? — Decision: picks the branch to follow. High priority: alert the team now. Low: logged for tomorrow's digest.
• [For each item — “Each Mastodon mention”] Alert the team in Slack — Slack: Post a message. Branch: Important. Posts the mention, its category, who sent it, the suggested next step and the link.
• [For each item — “Each Mastodon mention”] Log it — Google Sheets: Add a row. Branch: Low. Adds a row to your mentions log (Date | Time | Network | From | Category | Priority | Text | Link | Suggestion).
• [For each item — “Each Mastodon mention”] Remember it — Remembers it for later runs (memory “mention-reply-alerts”, kept 7 days). Marks this mention as handled for 7 days.
• When was the last digest? — Recalls what it remembered earlier (memory “mention-reply-alerts”). Reads the date of the last daily digest.
• Digest due today? — Step. In code: the digest goes out once a day, with the first run after midnight in your time zone.
• Send the digest? — Decision: picks the branch to follow. Once a day; otherwise this run ends here.
• No digest this run — Kept in the run history. Branch: Already sent. Today's digest already went out.
• Read the mentions log — Google Sheets: Read rows. Branch: Once a day. Reads your mentions log.
• Keep yesterday's rows — Step. In code: keeps the rows logged yesterday.
• Each of yesterday's rows — Repeats the steps below for each item (up to 200 per run). Goes through yesterday's rows so they can be counted (up to 200).
• [For each item — “Each of yesterday's rows”] Counted — Kept in the run history. Nothing is changed in the log.
• Count yesterday's mentions — Step. In code, not AI: yesterday's mentions grouped by category, with the important ones (already alerted) first.
• Post the daily digest — Slack: Post a message. Posts yesterday's mentions, grouped and counted in code, to your Slack channel.
• Remember today's digest — Remembers it for later runs (memory “mention-reply-alerts”, kept 30 days). Stores today's date so the digest goes out once a day.
• Digest sent — Kept in the run history. The run history keeps the digest.

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.
• For-each loops repeat only the first 3 items.
• Memory steps don't read or write stored memory: a recall finds nothing, and a save only shows what it would store.

Go live

• Open the trigger, set your time zone (the daily digest follows it) and switch the schedule on. It runs every 15 minutes.
• 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.

• Scheduled triggers
• Switching a trigger on (Activation)

Questions

How fast are the alerts?

Notifications are checked every 15 minutes, so an alert arrives within about a quarter of an hour of the post.

Which notifications count?

On Bluesky: mentions, replies to your posts and quotes (likes, reposts and follows are skipped). On Mastodon: mentions, which include replies to you.

Will it alert on old mentions when I switch it on?

No: it only looks at notifications from today and yesterday, and remembers each one it handled for 7 days.

Does it reply?

No. It alerts and suggests a next step; your team replies. For reply drafts, see the Social Reply Assistant.

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.
• Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
• 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.

• Debugging failed runs
• Error messages
• Get help