Field forms & inspections
Fulcrum
Mobile data collection, checklists, service inspections and verified evidence.
A direct, read-only Rooutiq API adapter is implemented. Authorize your provider account and verify the first read; this is not a live connection until then.
Workspace authority and approved access scope are determined after sign-in.
A successful permitted read, current source health, and recorded evidence must be checked in the workspace.
SETUP / APPROVAL / VERIFICATION
From discovery to a verified connection
Native connector available — A direct, read-only Rooutiq API adapter is implemented. Authorize your provider account and verify the first read; this is not a live connection until then. These are the steps to review, not completed tasks or a live connection status.
- Requires review
Authorize the native API adapter
The provider-specific adapter is built. Review the required account permissions and authorize a real provider read; a native adapter is not a pre-connected customer account.
- Requires review
Confirm workspace authority
A workspace owner or authorized administrator reviews the requested system, account ownership and permitted scope before connection.
- Requires review
Approve provider access
Where supported, an authorized person completes the provider-specific authorization or approved import. Never enter provider passwords into a catalog page.
- Requires review
Verify the connection and evidence
Only a successful permitted read, source-health check and recorded approval can establish that this workspace has usable connected data. A saved system alone is not enough.
Public catalog data cannot attest to your workspace permissions, vendor approval, connection health or record freshness. Confirm actual status after signing in.
Connection options
Native Rooutiq read-only Fulcrum field-inspection records adapter. Uses customer-issued X-ApiToken to read minimal organization record IDs, status and update time; location, submitted field values, photos, personnel and private details are discarded. Fulcrum Developer Pack access is required.
Prerequisites to check
- Customer grants access using the provider's supported credentials
- Fulcrum Developer Pack and read-only X-ApiToken; no form field values retained
- Rooutiq verifies a real provider record read
- Source data remains non-authoritative until separately approved
Common uses for this category
Category-level uses, not a promise that this provider exposes every field or capability.
Operational integration blueprint
How Fulcrum could drive accountable conversations
This is a proposed integration design for discovery and implementation review, not a claim that Fulcrum exposes every object, that a tenant is authorized, or that Rooutiq has activated these triggers.
Records to inspect
Form submission, inspection checklist, version, failed item and photo evidence
Proposed operational exception
Failed inspection requires immediate owner; reinspection missing or disputed
Cross-system identity
Form/template version, site/asset, submission ID
Proposed participants
Inspector, site supervisor, maintenance lead
Verification and release checklist
- Authorize exact tenant, account, least-privilege scopes and data access
- Prove a successful authenticated read of real tenant records and IDs
- Prove repeat sync, stale-data handling, retry recovery and duplicate suppression
- Map cross-system identifiers with human-reviewed confidence
- Test authorized members, permission revocation and cross-workspace denial
- Approve source authority and verify canonical event-to-conversation staging before enabling conversation creation
Default: no event ingestion beyond explicitly authorized scopes; no AI execution, external invitations, source authority or programmatic conversations without their respective approval and verified release gates.