Agent setup guide
Daily Site Log
Each foreman's daily report becomes a clean Notion log — and delays or safety issues go straight to the PM in Slack.
What it does
Each foreman's daily report becomes a clean Notion log — and delays or safety issues go straight to the PM in Slack.
- Starts from each new row your foremen's daily-report form adds to its Google Sheet.
- AI structures the report into a consistent log — crew, work completed, delays (cause and time lost), deliveries, weather, inspections, safety and tomorrow's plan — copying the foreman's facts exactly and marking blanks as not reported.
- Adds the day's log as an entry in your Notion daily-log database.
- Posts any delay over your threshold, and any injury, near miss or unsafe condition, to your PMs' Slack channel.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Google Sheets, Notion and Slack, connected in Settings → Integrations.
- A daily-report form (e.g. Google Forms) that writes to a Google Sheet, and a Notion daily-log database.
What it doesn't do
- It organises what the foreman reports and adds nothing of its own (no weather lookups, no estimates of time lost).
- It isn't an OSHA or incident report: serious incidents follow your own process.
- It doesn't handle photos or attachments from the form, only the text answers.
- Rows already in the sheet before activation aren't processed.
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: Google Sheets, Notion and Slack.
- The app it watches, connected in Settings → Integrations (the agent starts from an app event).
- 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 Google Sheets
Connect the Google account that can open your daily-report sheet (Settings → Integrations → Google Sheets).
3. Connect Notion
Connect Notion and share your daily-log database with Fluxo Flow (Settings → Integrations → Notion).
4. Connect Slack
Connect the Slack workspace your PMs use (Settings → Integrations → Slack).
5. Pick the daily-report sheet
Open the trigger, pick your Google account, paste the spreadsheet link and the tab reports are added to.
| Setting | What to enter | In step |
|---|---|---|
| Google account (daily reports) | The Google account that can open your daily-report response sheet. Pick your connected Google Sheets account. | “New daily report from the foreman” |
| Daily-report spreadsheet | Paste the link of the spreadsheet your foremen's form writes to. | “New daily report from the foreman” |
| Daily-report tab | The tab reports are added to, e.g. “Form Responses 1”. | “New daily report from the foreman” |
6. List your projects, PMs and alert rules
Open “Structure the daily log” and replace the placeholder with your projects, PMs and what to alert on.
| Setting | What to enter | In step |
|---|---|---|
| Your projects, PMs and alert rules | Replace the placeholder with your company name, each project with its PM, what delay is worth alerting (e.g. half a day or more, or anything that risks an inspection) and anything else you treat as a safety issue. It starts as “[DESCRIBE YOUR COMPANY, YOUR PROJECTS AND THEIR PMS, WHAT COUNTS AS A DELAY WORTH ALERTING AND WHAT COUNTS AS A SAFETY ISSUE HERE]” until you replace it. | “Structure the daily log” |
7. Pick the Notion daily-log database
Open “Add the log to Notion” and pick your account and database.
| Setting | What to enter | In step |
|---|---|---|
| Notion workspace | The Notion workspace with your daily-log database. Pick your connected Notion account. | “Add the log to Notion” |
| Daily-log database | The database each day's log becomes an entry in (title property “Name”). Share it with Fluxo Flow first: ••• → Connections. | “Add the log to Notion” |
8. Pick the PMs' Slack channel
Open “Alert the PM in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace your PMs use. Pick your connected Slack account. | “Alert the PM in Slack” |
| PMs' channel | Where delays and safety issues are posted, e.g. #pm-alerts. | “Alert the PM 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 and click “Activate app trigger”. New reports are picked up on your plan's schedule interval; rows already in the sheet aren't processed.
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.
- New daily report from the foreman — Starts on “New row” in Google Sheets (an app event). Starts a run for each row your foremen's daily-report form adds to its Google Sheet, checked on your plan's schedule interval.
- Structure the daily log — AI step (runs on your AI provider key). AI turns the foreman's answers into a clean daily log: crew count, work done, delays, deliveries, weather, inspections, safety notes and tomorrow's plan — and flags delays or safety issues for the PM.
- Add the log to Notion — Notion: Create a page in a database. Creates the day's entry in your Notion daily-log database with the structured log.
- Logged — Kept in the run history. The run history keeps the structured log and the Notion link.
- Delay or safety issue? — Decision: picks the branch to follow. Delays over your threshold and any safety issue are posted to the PM's channel; routine days aren't.
- Alert the PM in Slack — Slack: Post a message. Branch: Delay or safety. Posts the delay or safety issue, exactly as the foreman reported it, to your project managers' channel.
- PM alerted — Kept in the run history. The run history keeps the alert that was posted.
- Routine day — Kept in the run history. Branch: Routine day. No delay over your threshold and no safety issue: no alert.
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. The sample has the same shape as a real event from the app.
Sample data fields
sheet, row, row_number.
- 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 and click “Activate app trigger”. New reports are picked up on your plan's schedule interval; rows already in the sheet aren't processed.
- Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
- 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 form should foremen use?
Any form that writes to Google Sheets (Google Forms is free and works on phones): project, date, crew on site, work completed, delays, deliveries, weather, inspections or visitors, safety notes and tomorrow's plan.
Is this our incident report?
No. It organises what the foreman reports and alerts the PM. Injuries and incidents follow your own incident and OSHA reporting process.
Does it check the weather itself?
No. It logs the weather the foreman reports.
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).
- No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
- 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 .