Fulcrum

Connect AI agents to Fulcrum, the mobile field data collection platform. Agents list forms and their field schemas, create, update, and manage geolocated records, and pull photo attachments captured in the field into downstream systems.

8 actions API key available

Fulcrum website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The hourly sweep runs List Records against the site inspection form for new submissions

Get Record pulls each new submission in full: coordinates, form values, photos, and the inspector who filed it

The agent evaluates the inspection's status field and flags anything marked critical or failed

Every record logs to the tracking sheet with its location and inspector, and the linked photos are pulled via List Photos

Critical findings post to the field operations channel with the record's coordinates and photo evidence

The operations manager reviews the finding and decides whether to dispatch a crew, schedule a follow-up, or reclassify

Update Record writes the decision back, setting the new status and assigning the follow-up owner

The assigned crew gets the record link, location, and everything the inspector captured on-site

What This Integration Enables

Field data has a property office data does not: it cannot be re-collected. The inspector was at that site, at those coordinates, at that hour, and when the crew drives away the record is the only witness. Fulcrum captures that witness well; this connector makes sure it goes somewhere. FlowRunner agents list forms and their field schemas, read and create geolocated records, write status changes back, and pull photo attachments with their capture metadata into downstream systems. - Sync inspections and surveys into spreadsheets, CRMs, and databases as they arrive - Create records from external systems so field crews start with pre-filled context - Update status and assignee as part of dispatch and follow-up workflows - Pull photo evidence with capture location and timestamp attached - Discover each form's field keys programmatically before any write The write path respects what the data is. Because Update Record replaces the full value set and Delete Record is permanent, FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates stand in front of both.

Without FlowRunner

Field data ages in the app Inspections sit in Fulcrum until someone exports, so critical findings wait on a habit

Office and field see different truth The tracking sheet, the CRM, and the mobile records disagree about status and ownership

Every record edit is a risk Updating one field by hand means retyping the rest, and deletions are forever

With FlowRunner

Submissions flow out within the hour Records sync to sheets, CRMs, and alert channels as they arrive from the field

Status changes round-trip Office decisions write back to the record the crew sees on their device

Destructive writes are gated Full-value updates are staged from current data and deletions wait for a person

Use Case Scenarios

Critical findings that never wait for an export

List Records sweeps the safety inspection form hourly. New submissions log to [Google Sheets](/integrations/google-sheets) with coordinates, status, and inspector. Records flagged critical alert the operations channel in [Slack](/integrations/slack) immediately, with photos from List Photos attached as evidence. The manager dispatches, and Update Record assigns the record to the responding crew with the status moved to in-progress. What used to surface at the Friday export surfaces before the inspector leaves the parking lot.

Work orders that arrive pre-filled

A service request lands in the CRM. The agent calls Get Form to read the work order form's field keys, then Create Record with the site's latitude and longitude, the customer's details in the matching form values, and the record assigned to the nearest technician. The tech opens Fulcrum to a job that already knows where it is and what it needs. On completion, the record flows back through Scenario 1's sweep, and the CRM in [HubSpot](/integrations/hubspot) gets the on-site contact captured in the field.

The evidence package

A client audit requires every inspection for one site, with photos. The agent filters List Records for the form, pulls each full record with Get Record, and matches photo access keys against List Photos to collect capture timestamps and locations. The package assembles into a dated archive with the geolocation trail intact, proof not just of what was found, but of where and when the finding was made. What took a coordinator two days of matching photos to reports by filename now runs while the auditor is still writing the request email.

Human-in-Loop Highlight

Delete Record permanently destroys a field submission, and unlike a CRM row, nothing can regenerate it: the inspector, the site conditions, and the timestamped photos existed once. A cleanup workflow that guesses wrong erases evidence a dispute or an audit may later demand. So deletions on this page are always presented, never assumed: "Record from the Westside Substation form, filed 2026-03-14 by inspector T. Okafor, status duplicate-suspect, matches record filed 11 minutes later at the same coordinates. Both attached with photos. Delete the earlier one?" The operations manager compares and confirms, and the deletion runs against the single confirmed ID. Update Record gets a related discipline for a different reason: Fulcrum replaces the entire form_values object on update, so agents always stage the write from Get Record's current values, and any update that changes more fields than the workflow intended stops for review instead of silently dropping what the inspector recorded.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Forms

List Forms Lists the organization's forms (apps) with pagination. Forms define the schema records follow; the discovery step for every workflow.
Get Form Retrieves a form's full element schema, exposing each field's key, data name, type, and label. The map required before creating or updating records.

Records

List Records Lists a form's records with pagination, each carrying coordinates, status, and form values keyed by field key. The sweep behind syncs and alerts.
Get Record Retrieves a single record in full: coordinates, status, geometry, created and updated metadata, and all form values. The read that grounds every write.
Create Record Creates a record with Form ID, latitude, longitude, and form values matching the form's field types, optionally with status and assignee. The step that sends pre-filled work to the field.
Update Record Updates a record by ID, replacing the full form values object, with optional status and assignee changes. Staged from current values because Fulcrum replaces rather than merges.
Delete Record Permanently deletes a record. Cannot be undone, which is why it waits behind this page's human gate.

Photos

List Photos Lists photo attachments, optionally filtered by form, each with its access key, parent record, and capture location and timestamp. The evidence layer of every field record.

Frequently Asked Questions

What can FlowRunner do with Fulcrum?

FlowRunner agents can run List Forms, Get Form, and List Records in Fulcrum, plus 5 more actions.

Does connecting Fulcrum to FlowRunner require OAuth?

No. Fulcrum connects to FlowRunner with an API key, no OAuth flow required.

Can Fulcrum trigger a FlowRunner workflow automatically?

Fulcrum doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Fulcrum

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us