--- title: "FastField Integration" description: "FastField is a mobile forms, inspection and dispatch platform from Merge Mobile. Agents publish form templates, take completed submissions apart field by field, dispatch work to crews and recall it, sync offline data tables and choice lists, and manage users and groups." url: https://flowrunner.ai/integrations/fastfield date_modified: 2026-09-04T19:20:34-07:00 --- # FastField [Forms](https://flowrunner.ai/integrations/category/documents-forms) FastField is a mobile forms, inspection and dispatch platform from Merge Mobile. Agents publish form templates, take completed submissions apart field by field, dispatch work to crews and recall it, sync offline data tables and choice lists, and manage users and groups. 3 triggers · 45 actions · Session · available [FastField website](https://www.fastfieldforms.com/) · [Platform Documentation](https://www.fastfieldforms.com/) · Capability data verified 2026-08-26 1. A work order is approved in the ERP, CRM or ticketing system 2. Agent reads the site, asset, crew and due date from the work order 3. Get Form confirms the inspection template and its field keys still match the mapping 4. Create Dispatch pushes the pre-populated form to the assigned crew member with the work order in Reference ID 5. Get Submission reads the returned document field key by field key once the crew submits 6. Failed checks, missing photographs and out of range readings are separated from clean passes 7. The supervisor reads the failed checks and decides repair, re-inspect, or escalate to the customer ## What This Integration Enables FastField is built for organizations whose forms are filled in a truck, a basement or a plant with no signal, which makes it a very different problem from a web form. The record is created hours before the office sees it, by a person the office cannot interrupt, on a device that syncs when it can. FlowRunner agents work both ends of that gap. They push work outward as dispatches carrying the work order number, the site and the asset, and they take completed submissions apart field key by field key so the answers land in the ERP, the maintenance log and the document store without anyone retyping them. The connector is honest about how FastField delivers. There is no webhook management API, so the triggers here poll, and the real time path is a FastField HTTP delivery action pointed at a FlowRunner inbound URL. That is also why [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) matters more here than in an office tool. When an agent replaces a choice list or removes a user, the consequence reaches a phone in the field on its next sync, and the person holding that phone cannot see the mistake coming. ### Without FlowRunner **Field work is invisible until email**: FastField notifies by email, so the office learns a job finished when someone reads an inbox **Answers get re-keyed**: A completed inspection is retyped into the ERP, the maintenance log and the customer report **Device lists drift**: Site, asset and product lists on phones fall behind the master list, and crews pick stale options ### With FlowRunner **Assignments are visible where work is tracked**: Dispatches are created from the system of record and mirrored into the tools the office already watches **Submissions become records**: The agent maps field keys onto columns once, then every inspection lands in the right systems **Master data is reconciled on a schedule**: Data tables and choice lists are compared against the source of truth, with replacements reviewed before they ship ## Use Case Scenarios ### The work order that dispatches itself and comes back as data An approved work order in [Airtable](https://flowrunner.ai/integrations/airtable) or [Acumatica](https://flowrunner.ai/integrations/acumatica) reaches the agent. It calls Get Form to read the current field keys for the inspection template, then Create Dispatch to send the pre-populated form to the assigned technician with the work order number in Reference ID. A [Slack](https://flowrunner.ai/integrations/slack) direct message tells the technician what is waiting, because FastField itself only sends email. When the completed submission arrives, Get Submission returns the whole document keyed by field, the agent opens a defect ticket in [Jira Issues](https://flowrunner.ai/integrations/jira-issues) for each failed check, and the media files are archived to [Amazon S3 / Cloud Storage](https://flowrunner.ai/integrations/s3) against the submission id. ### Offline data tables that match the master list every morning Crews pick customers, sites and assets from data tables cached on their devices. Overnight, the agent reads the current master list from [Google Sheets](https://flowrunner.ai/integrations/google-sheets) or the ERP, calls Get All Data Table Items to walk every page of the FastField table, and computes the difference. New rows go in with Create Data Table Item, changed rows are replaced with Update Data Table Item, and retired rows are removed. On New Data Table Item covers the other direction, firing when a crew adds a row from a device so the office system learns about a site nobody had recorded yet. ### A leaver whose work is still in the field An identity system reports a field technician's last day. The agent calls List User Dispatches for that user and finds outstanding assignments. It does not delete anything. It posts the list to the field operations manager, who decides which jobs get recalled with Recall Dispatch and which get re-issued to a named colleague with Create Dispatch. Only after the queue is empty does the agent run Remove Users From Group, Remove Forms From Library and Delete User. Deleting the user first would have left live assignments with no recipient and no trace of who was supposed to do them. ## Human-in-Loop Highlight Replace Lookup List and Replace Global List are the two operations on this connector that can quietly break every form in the field. They address a list by name rather than by identifier, they take a whole file, and the replacement is total: every row the file omits disappears from the list and from every form that reads it. FastField publishes no delete route and no separate create route for either list type, so the only correction is another full file, which crews see on their next sync. So the nightly sync agent builds the file, compares it against the live list, and stops: "Tonight's export of the branch list has 812 rows. The list currently live has 1,140. Replacing it removes 328 branches from every form that uses this list. Replace, or hold for a corrected export?" The field operations manager answers in Slack. The agent is better than a person at spotting the row count gap. Deciding whether a short export is a real retirement or a broken query is not its call. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 45 actions ### Connection 1 - **Verify Connection** Confirms the API key, username and password work together before a flow is built on them. Worth its own step, because every other action fails with the same message when any one of the three is wrong. ### Forms 5 - **List Forms** Lists the form templates on the account with their identifiers, names and versions. The starting point for mapping a template to a downstream record type. - **Get Form** Reads one template, including its pages, sections and fields. Call it before writing any mapping, because a submission is keyed by each field's own field key rather than by its label. - **Create Form** Publishes a new form template to the account. - **Update Form** Updates an existing template. Version changes reach devices on their next sync, so pair schema changes with a dispatch pause where crews are mid-job. - **Delete Form** Permanently removes a template. Submissions already collected against it survive, but the form stops being dispatchable and disappears from devices. ### Submissions 1 - **Get Submission** Reads one completed submission by identifier, returning device and timing metadata, workflow stage, and one property per form field keyed by field key. Media answers arrive as file names rather than inline content. The identifier comes from a delivered payload, a dispatch or a report, because FastField publishes no route that lists submissions. ### Dispatch 4 - **Create Dispatch** Assigns a form to a user with pre-populated values, a due date and a reference identifier. The action that turns a work order in another system into a job on a crew member's device. - **Recall Dispatch** Withdraws an outstanding assignment. Used when a job is canceled, rescheduled or reassigned, and the step to run before removing the user it belongs to. - **List User Dispatches** Lists one user's outstanding assignments. The reconciliation read behind a dashboard, an escalation check, or an offboarding sweep. - **Get User Dispatch** Reads one assignment in full, including what was pre-populated and when it is due. ### Data Tables 10 - **List Data Tables** Lists the offline data tables on the account with their names, last sync times and column configuration. - **Get Data Table** Reads one data table's definition, including the columns a row must be keyed against. - **Create Data Table** Creates a new data table for forms to read from. - **Update Data Table** Updates a data table's definition. - **List Data Table Items** Returns one page of rows and reports the total page count. Used when a flow only needs a slice. - **Get All Data Table Items** Walks every page of a table and returns the complete row set, with a truncation flag when it stops at its safety ceiling. The read behind a full reconciliation. - **Get Data Table Item** Reads a single row. Worth calling once before a bulk write, because FastField accepts a column's display name on write and reports rows back keyed by the column's internal identifier. - **Create Data Table Item** Adds a row to a data table. - **Update Data Table Item** Replaces a row rather than merging into it, so send the complete row. FastField takes the row identifier in the body on this route rather than in the path. - **Delete Data Table Item** Permanently removes a row. A device that is offline can still show a row that has already been deleted, so treat deletions as eventually consistent with what crews see. ### Users and Roles 7 - **List Users** Lists the account's users. The read behind an access audit or a joiner and leaver reconciliation. - **Get Current User** Reads the user the connection is authenticated as. - **Get User** Reads one user record. - **Create User** Creates a field user with roles and library access. The Roles and Libraries values are the complete set rather than an addition. - **Update User** Updates a user. Because roles and libraries are replaced rather than merged, read the user first when only one entry should change. - **Delete User** Permanently removes a user. Their submissions survive, but any dispatch still assigned to them is left with no recipient, so clear the queue first. - **List Roles** Lists the roles available for assignment. Used to resolve role values before a user write. ### User Groups 4 - **List User Groups** Lists the crew groups on the account and who belongs to them. - **Create User Group** Creates a group, typically to mirror a crew, a region or a shift from the system that already defines them. - **Add Users To Group** Adds users to a group. A membership change rather than a user change. - **Remove Users From Group** Removes users from a group. The user record and their submissions are untouched. ### Libraries 7 - **List Libraries** Lists the form libraries that control which forms a crew can open. - **Create Library** Creates a library, usually to match a job type or a customer program. - **Update Library** Updates a library's definition. - **Delete Library** Permanently removes a library. The forms inside it survive, but users whose access came only through it stop seeing them. - **List Library Forms** Lists the forms in a library. The read behind an audit of what a crew can actually open on their devices. - **Add Forms To Library** Adds forms to a library, granting access to everyone the library covers. - **Remove Forms From Library** Removes forms from a library. A membership change, not a deletion. ### Lists 4 - **List Lookup Lists** Lists the lookup lists available to forms, so a flow can confirm a name before replacing anything. - **Replace Lookup List** Replaces a lookup list wholesale from an XLSX or CSV file fetched from a URL. Addressed by list name, and total: rows the file omits vanish from every form that reads the list. The operation this page's human gate exists for. - **List Global Lists** Lists the account level global lists. - **Replace Global List** Replaces a global list wholesale from a file, with the same total semantics as a lookup list replacement and the same absence of an undo. ### Media 1 - **Upload Media** Uploads a media file to the account for use in forms and templates. ### Custom 1 - **Make API Call** Calls a FastField route this connector does not name. Present because FastField publishes no public API reference, so an account with routes or payload fields outside the attested set still has a path. ## Triggers 3 triggers ### Event Triggers 3 - **On New Form** Fires when a form template is added to the account, emitting the form with its identifier, name and version. Used to register a new template with the rest of the stack, for example by creating its destination table. The first polling cycle records what already exists and fires nothing, so switching the trigger on never replays the catalog. - **On New Data Table Item** Fires when a row is added to a chosen data table, emitting the row and its data object keyed by column. Because data tables are written by devices as well as by the API, this is the practical way to react to what crews capture offline once their device syncs. Each cycle reads the first page, so a table that gains more rows between cycles than one page holds can outrun it. - **On New User Dispatch** Fires when a new assignment appears for a chosen user, which is how a dashboard or a chat alert can mirror FastField work that the platform itself only announces by email. A dispatch that is completed or recalled leaves the list and is not re-emitted if it returns. ## Frequently Asked Questions ### What can FlowRunner do with FastField? FlowRunner agents can run Verify Connection, List Forms, and Get Form in FastField, plus 42 more actions. ### Does connecting FastField to FlowRunner require OAuth? No. FastField connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can FastField trigger a FlowRunner workflow automatically? Yes. FastField supports 3 triggers that can start a FlowRunner workflow automatically. **Work at FastField?** This integration exposes FastField to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/fastfield. Site index: https://flowrunner.ai/llms.txt