Agent setup guide
Content Creation Agent
Turns each brief into an SEO article, five social posts and a newsletter blurb, drafted in Notion for your editor.
What it does
Turns each brief into an SEO article, five social posts and a newsletter blurb, drafted in Notion for your editor.
- Receives each content brief from your form through a webhook: topic, audience, goal, keywords, platforms, length, target date and source notes.
- AI writes a draft package in your brand voice: an SEO article (title, meta title and description, slug, excerpt, body), posts for LinkedIn, X, Instagram, Facebook and TikTok, hashtags, a newsletter blurb and image ideas.
- It never invents statistics or quotes: missing facts are marked [SOURCE NEEDED] and every claim to check is listed.
- Saves the whole package as a page in your Notion content database and adds a row to your content calendar in Google Sheets.
- A second AI pass checks the draft like an editor (claims, SEO basics, platform length limits, call to action), scores it and posts the fixes, with the link to the Notion page, to your Slack content channel.
- Briefs too thin to write from are sent back to Slack with specific questions instead of a made-up draft.
What it needs
- A paid plan (agents run live on paid plans; included with Elite).
- An AI provider key (Settings → AI Providers).
- Notion, Google Sheets and Slack, connected in Settings → Integrations.
- A Notion database for drafts and a Google Sheet for the content calendar.
- A brief form or tool that can send submissions to a webhook URL.
What it doesn't do
- It doesn't publish anything: no WordPress, blog or social posting. A person edits and publishes the drafts.
- It doesn't create images; it suggests image ideas for a designer or image tool.
- It doesn't research the web or check facts; it lists the claims an editor must verify.
- It doesn't schedule posts in a social tool; the target date is recorded in your calendar sheet.
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 Elite and Enterprise plans; 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, Google Sheets and Slack.
- A form, app or system that can send each new item to a webhook URL (the agent starts from a webhook).
- About 20 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 that holds your content database (Settings → Integrations → Notion), and share the database with Fluxo Flow.
3. Connect Google Sheets
Connect the Google account that can edit your content calendar (Settings → Integrations → Google Sheets).
4. Connect Slack
Connect the Slack workspace your content team uses (Settings → Integrations → Slack).
5. Describe your brand and voice
Open “Write the article and social posts” and replace the placeholder with your brand, audience, tone, call to action and no-go topics. The drafts are only as on-brand as this description.
| Setting | What to enter | In step |
|---|---|---|
| Your brand, audience and voice | Replace the placeholder in the writer's instructions with who you are, who you write for, your tone (with words to use and avoid), your standard call to action and any topics or claims to stay away from. It starts as “[DESCRIBE YOUR BRAND, AUDIENCE AND VOICE HERE]” until you replace it. | “Write the article and social posts” |
6. Pick the Notion database
Open “Save the draft package to Notion” and pick your account and the content database.
| Setting | What to enter | In step |
|---|---|---|
| Notion account | The Notion workspace the drafts are saved to. Pick your connected Notion account. | “Save the draft package to Notion” |
| Notion content database | The database each draft becomes a page in (its title property is usually “Name”). Share it with Fluxo Flow in Notion first: ••• → Connections. | “Save the draft package to Notion” |
7. Pick the content calendar
Open “Add it to the content calendar sheet”, pick your Google account, paste the spreadsheet link and pick the tab.
| Setting | What to enter | In step |
|---|---|---|
| Google account (content calendar) | The Google account that can edit your content calendar sheet. Pick your connected Google Sheets account. | “Add it to the content calendar sheet” |
| Content calendar spreadsheet | Paste the link of the Google Sheet you plan content in. Columns: Added, Title, Type, Keyword, Target date, Requester, Words, Status. | “Add it to the content calendar sheet” |
| Calendar tab | The tab (sheet) inside the spreadsheet the rows are added to. | “Add it to the content calendar sheet” |
8. Pick the Slack channels
Open the two Slack steps and pick your account and a channel in each (they can be the same). Invite the app to private channels first (/invite @Fluxo Flow).
| Setting | What to enter | In step |
|---|---|---|
| Slack account (brief questions) | The Slack workspace questions about incomplete briefs are posted to. Pick your connected Slack account. | “Ask for the missing details in Slack” |
| Channel for brief questions | Where the people who send briefs will see the questions, e.g. #content-requests. | “Ask for the missing details in Slack” |
| Slack account (new drafts) | The Slack workspace new-draft notices are posted to. Pick your connected Slack account. | “Tell the content team in Slack” |
| Channel for new drafts | Where your editors hear about new drafts, e.g. #content. | “Tell the content team in Slack” |
9. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
10. Switch the trigger on
Open the trigger, switch the webhook on and point your brief form at its URL (send the secret in the x-fluxo-secret header).
How it works
The agent is a normal workflow with 12 steps (2 AI steps). You can open, edit and monitor it like any other workflow.
- New content brief — Starts when your form or app sends data to the agent's webhook URL. Your brief form (Typeform, Tally, Webflow, your intranet…) posts each brief to the workflow's webhook URL: topic, audience, goal, keywords, platforms and any source notes.
- Write the article and social posts — AI step (runs on your AI provider key). AI writes the article (title, SEO meta, slug, excerpt, body), five platform-specific social posts, hashtags, a newsletter blurb and image ideas from the brief and your brand voice, and lists every claim that needs a source.
- Brief clear enough? — Decision: picks the branch to follow. Briefs missing the facts the piece needs go back to the requester's team in Slack with the AI's questions; complete briefs become drafts.
- Ask for the missing details in Slack — Slack: Post a message. Branch: Needs more info. Posts the brief's topic, who sent it and the AI's questions to your content channel, so someone fills the gaps and resends the brief.
- Sent back for details — Kept in the run history. The run history keeps the brief and the questions asked.
- Save the draft package to Notion — Notion: Create a page in a database. Branch: Brief OK. Creates a page in your content database with the article, SEO fields, every social post, hashtags, the newsletter blurb, image ideas and the claims to check.
- Draft saved — Kept in the run history. The run history keeps the draft package.
- Add it to the content calendar sheet — Google Sheets: Add a row. Branch: Brief OK. Adds a row to your content calendar in Google Sheets: date added, title, type, primary keyword, target date, requester, word count and status “Draft in Notion”.
- Calendar updated — Kept in the run history. The run history keeps the calendar row that was added.
- Editorial check — AI step (runs on your AI provider key). Branch: Brief OK. A second AI pass checks the package like an editor: claims without sources, SEO basics, platform length limits and call to action, and scores it out of 100.
- Tell the content team in Slack — Slack: Post a message. Once the editorial check is done and the Notion page exists, posts the new draft's title, the editorial score, the fixes, the claims to check and the link to the Notion page to your content channel.
- Team notified — Kept in the run history. The run history keeps the editorial check.
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. Edit the sample to match the fields your own form or app sends.
Sample data fields
topic, audience, goal, keywords, platforms, length, publish_date, notes, requester_name, requester_email.
- 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, switch the webhook on and point your brief form at its URL (send the secret in the x-fluxo-secret header).
- The webhook is protected by a secret: send it in the header shown in the Activation panel (requests without it are refused with 403). Each request starts one run.
- 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
Does it publish to my blog or social accounts?
No. It writes drafts to Notion and your content calendar sheet. A person edits, schedules and publishes them.
Does it make images?
No. It suggests 2–3 image or graphic ideas your designer or image tool can use.
What should the brief contain?
At least a topic. Audience, goal, keywords, platforms, length, target date and source notes make the draft much better; the agent asks in Slack when facts are missing.
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).
- Nothing happens when your form sends data: check the webhook is switched on and the request carries the secret header (403 means it's missing or wrong).
- 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 .