SafetyCulture
FormsAutomate SafetyCulture (formerly iAuditor) inspection workflows. Agents search and retrieve inspections, export them to PDF, browse templates, raise and track corrective actions when audits fail, and look up users.
What This Integration Enables
An inspection platform succeeds when audits get completed; a safety program succeeds when failures get acted on. The distance between those two is where incidents live, and it is exactly the distance this connector closes. FlowRunner agents sweep SafetyCulture for newly modified inspections, pull full audit data, export board-ready PDFs, raise corrective actions when audits fail, and chase those actions until they close. - Pull newly modified inspections incrementally and post them to a warehouse or spreadsheet - Route failed audit items to the responsible team with responses and media - Export inspections to PDF for email, archive, or client delivery - Raise corrective actions with priority, assignee, asset link, and due date - Track action status and escalate what goes overdue - Look up users to resolve the right assignee or auditor The incremental Modified After cursor deserves a mention on its own: it means sweeps scale to accounts with years of audit history without re-reading everything, so the fifteen-minute cadence stays fifteen minutes as the organization grows. The judgment call in this loop is not whether to act on a failure, it is how urgently, and that is a call about physical risk. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step puts that decision with the safety manager, every time.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The failed-audit fire line
Search Inspections runs every fifteen minutes with the incremental Modified After cursor. Get Inspection expands each new audit, and failed responses post to [Slack](/integrations/slack) with the item text, score impact, and photo references, while [Gmail](/integrations/gmail) alerts the site manager directly. The safety manager triages, and Create Action raises the corrective task with their chosen priority and due date. For incidents that need formal tracking, the same failure opens an incident in [ServiceNow](/integrations/servicenow) with the audit ID linked.
The compliance archive that builds itself
Every completed inspection gets Export Inspection PDF, and the base64 document uploads to [Google Drive](/integrations/google-drive) under the site and month. A row appends to [Google Sheets](/integrations/google-sheets) with audit ID, template, score, and PDF size, so the compliance register and the evidence archive never drift apart. When a client or regulator asks for six months of records for one site, the answer is a folder link, not a week of exports.
The corrective-action chase
Daily, Search Actions pulls everything open and overdue. Each overdue action escalates to its assignee with the linked inspection context, and repeat offenders roll up into the weekly operations digest. Search Users resolves assignee names and emails so escalations reach people, not IDs. Search Templates and Get Template feed the quarterly review, showing which inspection templates generate the most failures and where the checklist itself needs work.
Human-in-Loop Highlight
Create Action assigns real work about real hazards, and its priority field is a severity judgment an agent should not make alone. Auto-raising every failure as critical trains sites to ignore critical; auto-raising a genuine gas-leak finding as low priority is the more dangerous failure, a misclassification that costs exactly what safety programs exist to prevent. So on this page the agent prepares the decision and a person makes it: "Inspection at the Harborview site failed item 'Emergency stop accessible and unobstructed' with a photo showing pallets against the panel. Auditor: J. Mercer, 08:40 today. Raise corrective action: what priority, who owns it, by when?" The safety manager answers in one message, Create Action fires with those exact values, and the daily chase in Search Actions takes it from there. The agent never buries a failure and never inflates one; it guarantees a qualified human sees every failure while the site conditions in the photo still exist.
Agent Capabilities
8 actionsInspections
3- Search Inspections Searches the organization's inspections with template and modified-time filters, returning lightweight records with audit_id and timestamps plus a total count. The Modified After filter is the incremental cursor behind scheduled sweeps.
- Get Inspection Retrieves a completed inspection in full: the item tree with responses, scores, media references, header data, and metadata. The expansion step that makes failure routing possible.
- Export Inspection PDF Exports an inspection as a base64-encoded PDF with its byte size, generated on demand from current data. The step that feeds archives, emails, and client deliveries.
Templates
2- Search Templates Searches inspection templates with modified-time filtering, returning template IDs and names. Used to scope sweeps and feed template-quality reviews.
- Get Template Retrieves a template's full structure: pages, sections, and question items with response types and logic. The reference for interpreting audit responses correctly.
Corrective Actions
2- Search Actions Searches corrective actions with status filtering and paging, returning title, priority, status, assignees, due date, and linked asset or inspection. The tracking step behind the daily chase.
- Create Action Creates a corrective action with title, description, priority, status, asset link, and due date. Raised with human-set severity, per this page's gate.
Users
1- Search Users Searches organization members with status filtering, returning ID, name, email, and status. The resolution step for assignees and escalation targets.
Frequently Asked Questions
What can FlowRunner do with SafetyCulture?
FlowRunner agents can run Search Inspections, Get Inspection, and Export Inspection PDF in SafetyCulture, plus 5 more actions.
Does connecting SafetyCulture to FlowRunner require OAuth?
No. SafetyCulture connects to FlowRunner with an API key, no OAuth flow required.
Can SafetyCulture trigger a FlowRunner workflow automatically?
SafetyCulture doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SafetyCulture
$100 in credits. No card required. Connect in minutes.