Once Fluix is connected to your AI assistant, you can ask about your task reports, form submissions, and document statuses in simple language. This article collects prompts that work well, grouped by what you are trying to do.
These prompts work the same way in Claude, ChatGPT, Copilot, or any other assistant connected to the Fluix MCP server. Choose the guide for your assistant to connect to Fluix and run your first query:
How to use these prompts
Replace <report> with the name of one of your own task reports or datasets — for example, Site Safety Inspections or Vehicle Pre-Use Checks. You do not need report IDs or field names; the name is enough.
If you are not sure what you can access, start here:
“List my Fluix task reports.”
Your assistant reads only the data your own Fluix account can already see, in the single company you selected when you connected. Access is read-only, so none of these prompts change anything in Fluix.
Getting the overall picture
Use these when you want the shape of a whole report rather than one specific record.
- What does
<report>show? Summarize the key metrics. - What’s overdue or stuck in
<report>right now, and who owns it? - Give me the top 5
<assets/units>that keep failing, with what’s actually going wrong each time. - Prepare an operational dashboard for my manager based on
<report>. - Rank the findings in
<report>by severity, and flag anything found but never verified as fixed. - Which sites or forms in
<report>produce messy or inconsistent data? - Are our safety and quality numbers in
<report>trending better or worse over time?
Regular digests
Use these for a recurring catch-up, or when you need to summarize progress for someone else.
- Give me a
<daily/weekly/monthly>digest of<report>— what changed, what’s new, what needs attention. - Summarize my own pending work in
<report>— anything missing a signature or required field before someone flags it? - I need a simple summary for a customer confirming
<report>inspections were completed and passed — nothing internal.
Deciding what to work on
Use these to cut a large report down to a handful of items that actually need you.
- What needs my immediate attention in
<report>right now? - What’s overdue or stuck in
<report>, and how long has it been sitting? - What should I focus on today across
<report>? - Give me this week’s priority list for
<report>— just the things that actually need action.
Checking data quality
Use these before you rely on a report for a decision, an audit, or a customer.
- Check
<report>for missing data — are all required fields filled in? - Are all required photos attached in
<report>,and is anything missing a signature? - Can I trust the data in
<report>? Run an integrity check before I use it. - Are there any records in
<report>that contradict themselves — like something marked both “needs replacement” and “approved”? - Which records in
<report>are missing something they should already have, given how far along they are?
Getting better answers
- Name the report and a time range. “Overdue items in Site Safety Inspections from the last 30 days” returns a far more useful answer than “what’s overdue.”
- Open unfamiliar reports by asking about their structure. “Show the columns available in <
report>before pulling any rows” tells you what questions are worth asking. - Keep narrowing instead of starting over. Once your assistant has pulled a report, follow up: “now group that by site,” “now show only the failed ones.”
- Ask where a number came from. Your assistant can point back to the records behind a total — worth doing before you forward anything onward.
- Be specific in large reports. Big result sets are read page by page rather than all at once, so a narrower question is usually both faster and more accurate.
What your assistant can access
| Permission | What it allows |
| Documents | Read document statuses |
| Datasets | Read form-submission datasets |
Access is read-only. Your assistant cannot create, change, or delete anything in Fluix, cannot assign or complete tasks, and cannot see data outside the company you selected when connecting.
Note: Since answers are generated by the assistant rather than by Fluix, it is worth spot-checking anything you plan to act on or send to a customer, ask it to show the underlying records.
In case you have any additional questions, feel free to contact us at support@fluix.io. We will be happy to assist you!