Agent setup guide
Sermon → Small-Group Guide
Sunday's sermon becomes a summary, discussion questions, a prayer prompt, a newsletter blurb and social posts — approved by the pastor before leaders see it.
What it does
Sunday's sermon becomes a summary, discussion questions, a prayer prompt, a newsletter blurb and social posts — approved by the pastor before leaders see it.
- Starts when your form or website posts the sermon: title, series, passage, preacher, date and the transcript or notes.
- AI writes a summary, 5–7 discussion questions from observation to application, a prayer prompt, leader notes, a newsletter blurb and 3 social posts — using only what was preached.
- It lists any Scripture reference that wasn't in the transcript so the pastor can remove it.
- The pastor reviews and edits everything in Reviews before anyone sees it.
- The approved guide is saved to your Notion sermons database and posted to your group leaders' Slack channel with the Notion link.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Notion and Slack, connected in Settings → Integrations, and a Notion sermons database with the listed properties.
- A transcript or full notes as text, posted by your form or site (from your video or podcast host's transcript).
What it doesn't do
- It adds no theology, quotes or verse references that weren't preached, and the pastor approves every guide.
- It doesn't turn audio or video into text: send it a transcript or notes.
- It doesn't publish to social media or your newsletter tool: the blurb and posts are saved for you to use.
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 and Slack.
- A form, app or system that can send each new item to a webhook URL (the agent starts from a webhook).
- About 15 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 Notion and share your sermons database with the Fluxo Flow integration (Settings → Integrations → Notion).
3. Connect Slack
Connect the Slack workspace your group leaders use (Settings → Integrations → Slack).
4. Describe your church and groups
Open “Write the small-group guide” and replace the placeholder with your church, groups and tone.
| Setting | What to enter | In step |
|---|---|---|
| Your church, groups and tone | Replace the placeholder with your church's name, how your small groups meet, the tone you want, the Bible translation you quote and anything leaders asked you to avoid. It starts as “[DESCRIBE YOUR CHURCH, YOUR SMALL GROUPS (HOW LONG THEY MEET, WHO ATTENDS), THE TONE YOU WANT, BIBLE TRANSLATION YOU QUOTE, AND ANY WORDS OR TOPICS LEADERS ASKED YOU TO AVOID HERE]” until you replace it. | “Write the small-group guide” |
5. Pick the sermons database
Open “Save to your Notion sermons database” and pick your account and database.
| Setting | What to enter | In step |
|---|---|---|
| Notion account | The Notion workspace with your sermons database. Pick your connected Notion account. | “Save to your Notion sermons database” |
| Sermons database | The Notion database guides are saved to, with the properties Name (title), Series (text), Passage (text), Preacher (text), Date (date), Status (select). | “Save to your Notion sermons database” |
6. Pick the leaders' channel
Open “Send it to group leaders” and pick your account and channel.
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace your group leaders use. Pick your connected Slack account. | “Send it to group leaders” |
| Group leaders' channel | Where the weekly guide is posted, e.g. #group-leaders. | “Send it to group leaders” |
7. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
8. Switch the trigger on
Open the trigger, switch the webhook on and copy its URL and secret into the form or tool that sends your sermon notes.
How it works
The agent is a normal workflow with 7 steps (1 AI step, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.
- Sermon notes or transcript — Starts when your form or app sends data to the agent's webhook URL. Starts when your form or website posts the sermon: title, series, passage, preacher, date and the transcript or full notes.
- Write the small-group guide — AI step (runs on your AI provider key). AI writes a one-paragraph summary, 5–7 discussion questions from observation to application, a prayer prompt, a newsletter blurb and 3 social posts, using only what was preached.
- Pastor reviews the guide — A person approves or rejects it in Reviews (the run waits). The pastor reads the guide in Reviews, edits anything (wording, questions, theology) and approves before it reaches Notion and the group leaders.
- Not approved — Kept in the run history. Branch: Rejected. Nothing was saved or sent; the run history keeps the draft.
- Save to your Notion sermons database — Notion: Create a page in a database. Branch: Approved. Adds the approved guide to your Notion sermons database: summary, questions, prayer prompt, leader notes, blurb and social posts.
- Send it to group leaders — Slack: Post a message. Posts the approved guide (summary, questions, prayer prompt) with the Notion link to your group leaders' Slack channel.
- Guide shared — Kept in the run history. The run history keeps the approved guide and the Notion link.
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
sermon_title, series, passage, preacher, date, transcript.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
- Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.
Go live
- Open the trigger, switch the webhook on and copy its URL and secret into the form or tool that sends your sermon notes.
- 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
What should the form send?
A JSON POST with sermon_title, series, passage, preacher, date (YYYY-MM-DD) and transcript (the transcript or full notes as text). Your form or site posts it with the webhook's signature header. Use a transcript from your video or podcast host; the agent doesn't turn audio into text.
Will it add Bible verses or theology?
No. It's told to use only what was preached and lists any reference it used that wasn't in the transcript, so the pastor can remove it before approving.
What Notion database do I need?
A database with the properties Name (title), Series (text), Passage (text), Preacher (text), Date (date), Status (select), shared with the Fluxo Flow integration (••• → Connections).
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 run shows as paused: it's waiting for someone in Reviews to approve or reject it.
- 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 .