Mitti (field inspections)
The Mitti integration (formerly SafetyCulture) links your field inspections to your pipelines: trigger processing when an inspection is completed, read it in a structured way, export its report, and turn a non-compliant item into an assigned action.
Nodes
| Node | Effect |
|---|---|
mitti_inspection_inbound (receiver) | Triggers a pipeline on inspections: periodic polling, or a signed real-time callback if you enable it |
mitti_inspection_search | Finds an inspection |
mitti_inspection_read | Returns an inspection in a stable form, with the count of failed items |
mitti_report_export | Produces the report (file or link) |
mitti_action_create | Turns a failed item into an assigned action |
Agent tools
- Read:
mitti.list_inspections,mitti.find_inspection(by customer or site),mitti.get_inspection,mitti.get_inspection_media,mitti.list_actions,mitti.list_assets,mitti.list_templates,mitti.export_report. - Write:
mitti.create_action,mitti.create_issue,mitti.start_inspection(starts an empty inspection),mitti.update_action_status.
No invented verdicts. An item's compliance comes from Mitti; when Mitti does not provide one, the verdict remains "unknown" — it is never inferred by an AI.
Connection (BYO)
- Settings → Services → Mitti (field inspections), Accounts tab.
- Enter a Mitti API token. A read-only token is enough for reading; writing and real-time require an administrator token (or "manage all data").
Limitations
- Creating inspection templates is not possible: Mitti does not expose this operation.