Browse the docs

Agent setup guide

Holiday & Awareness-Day Planner

Every month: the holidays and awareness days 2 to 6 weeks ahead that fit your niche, with Bluesky and Mastodon drafts in Notion. It never posts.

Available About 10 min to set up

What it does

Every month: the holidays and awareness days 2 to 6 weeks ahead that fit your niche, with Bluesky and Mastodon drafts in Notion. It never posts.

  • On the 15th of each month, works out in code the window 14 to 47 days ahead.
  • AI suggests the public holidays, awareness days and seasonal moments in that window that fit your industry, country and audience, plus your own dates, and marks the ones that move from year to year with what to check.
  • Drafts a Bluesky post (300 characters) and a Mastodon post (500, with hashtags) for each date.
  • Drops any suggested date outside the window, in code, and adds one page per date to your Notion content database for review.

What it needs

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Notion, connected in Settings → Integrations.
  • A Notion content database with a Date property, shared with Fluxo Flow.

What it doesn't do

  • It never posts: you review and post the drafts (or schedule them).
  • Dates come from the AI's general knowledge, not an official calendar: confirm each one before posting.
  • At most 10 dates a month.

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 content database (Settings → Integrations → Notion).

3. Describe your business

Open “Suggest dates and draft posts” and fill in your industry, country, audience and rules.

SettingWhat to enterIn step
Your industry or nicheYour industry or niche, e.g. independent bakery, dog grooming, accounting for freelancers. It starts as “[YOUR INDUSTRY OR NICHE, E.G. INDEPENDENT BAKERY]” until you replace it.“Suggest dates and draft posts”
Your countryThe country (and region, if it matters) your customers are in, for public holidays. It starts as “[YOUR COUNTRY (AND REGION, IF IT MATTERS)]” until you replace it.“Suggest dates and draft posts”
Your audienceWho your customers are, e.g. families and office workers nearby. It starts as “[WHO YOUR CUSTOMERS ARE, E.G. FAMILIES AND OFFICE WORKERS NEARBY]” until you replace it.“Suggest dates and draft posts”
Your tone, own dates and topics to avoidYour tone, your own dates (anniversary, events, launches) with their dates, observances or topics to avoid, and hashtags you use. It starts as “[YOUR TONE, YOUR OWN DATES (ANNIVERSARY, EVENTS, LAUNCHES) WITH THEIR DATES, OBSERVANCES OR TOPICS TO AVOID (E.G. RELIGIOUS OR POLITICAL ONES) AND HASHTAGS YOU USE]” until you replace it.“Suggest dates and draft posts”

4. Pick the content database

Open “Add it to your content database” and pick the account and database (with a Date property).

SettingWhat to enterIn step
Notion accountThe Notion workspace with your content database. Pick your connected Notion account.“Add it to your content database”
Content databaseThe Notion database for the drafts (it needs a Date property). Share it with Fluxo Flow (••• → Connections).“Add it to your content database”

5. Test it with Dry Run

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

6. Switch the trigger on

Open the trigger, set your time zone and switch the schedule on. It runs on the 15th of each month at 9:00.

How it works

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

  • On the 15th of every month — Runs on a schedule (cron 0 9 15 * *, UTC — change it in the trigger's settings). Runs at 9:00 on the 15th of each month and plans the dates 2 to 6 weeks ahead. Set your time zone on the trigger.
  • Work out the planning window — Step. In code: today's date and the window to plan (14 to 47 days from today, so next month is covered with time to prepare).
  • Suggest dates and draft posts — AI step (runs on your AI provider key). AI suggests the holidays and awareness days in the window that fit your niche, country and audience (plus your own dates) and drafts a Bluesky and a Mastodon post for each.
  • Keep dates in the window — Step. In code, not AI: drops any suggested date that isn't a real date between 14 and 47 days from today.
  • Each date — Repeats the steps below for each item (up to 10 per run). One Notion page per date (up to 10).
  • [For each item — “Each date”] Add it to your content database — Notion: Create a page in a database. Creates a page in your Notion content database with the date, why it fits, the idea, both drafts and what to verify.
  • Count the pages — Step. In code: how many dates were added, and which suggestions were dropped for being outside the window.
  • Planned — Kept in the run history. Review the drafts 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.
  • For-each loops repeat only the first 3 items.

Go live

  • Open the trigger, set your time zone and switch the schedule on. It runs on the 15th of each month 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

Are the dates always right?

The AI suggests dates from what it knows and marks the ones that move each year with what to check. Code drops anything outside the window, but confirm each date before you post: the page says so.

What does the Notion database need?

A title property (usually Name) and a date property called Date. Share the database with Fluxo Flow (••• → Connections).

Does it post for me?

No. It only drafts; post the ones you like yourself or with the Social Post Scheduler.

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 .