FieldproxyFieldproxy
Get Demo

Fieldproxy data model

Every Fieldproxy workspace has its own Postgres database. The field service objects are ordinary tables you can read with SQL, and you can add your own.

One database per workspace

Each workspace's data lives in its own Postgres database, not a shared table. Field service objects are ordinary business tables, and every workspace can add its own tables and columns, so names vary. Always start with describe_schema: it lists every table the connection may read with a one-line description, and with tables it returns full columns, types, foreign keys and notes, including which columns are writable.

explore, then query
describe_schema({ "tables": ["jobs", "customers"] })

run_sql({ "sql": "SELECT j.id, j.title, c.company_name, j.status
  FROM jobs j JOIN customers c ON c.id = j.customer_id
  WHERE j.status = 'completed' LIMIT 50" })

The core field service objects

Typical tables in a field service workspace (confirm the real names and columns with describe_schema):

ObjectWhat a row is
Customers and leadsA company or person you serve, with contacts and service locations.
Locations and sitesWhere the work happens: address and coordinates, used for routing, zones and GPS arrival.
Service requestsWork asked for but not yet a job: from a form, an email, a call or a text.
Jobs and work ordersA visit or piece of work: status, schedule, technician, priority, line items, checklist tasks, notes, photos and signatures.
Technicians and teamsWorkspace users (fp_users, by userid) and teams (fp_teams), used for assignment and access.
Quotes, estimates and proposalsPrices offered to a customer, with status, totals and validity; proposals add a customer link to accept.
Invoices and paymentsWhat is billed and collected, with balance due and due date; payments can come from Stripe links.
Service contracts and agreementsRecurring or covered work with start and end dates and covered services.
Assets and equipmentInstalled equipment at a site, with serials and service history.
Parts, stock and purchase ordersInventory on trucks and in warehouses, transfers and supplier orders.
CommunicationsSent emails and texts, and inbound threads from connected mailboxes.

Your own tables

With the build scope an AI can propose a new table (create_table: id, created_at and updated_at are added) or a new column (add_column). Builds only ever add: a table or column can be dropped through MCP only if it was created through MCP.

History, deletes and audit

  • Record history: who changed which field, from what to what (record_history, compare_record).
  • Deleted records go to a recycle bin and can be restored (list_deleted_records, restore_deleted_records).
  • Workspace activity: every data change and account action, filterable by source such as app, automation, api or ai (workspace_activity).

Getting data out

  • run_sql: one read-only SELECT, up to 500 rows.
  • export_csv: one SELECT saved as a CSV link, up to 10,000 rows.
  • Export from any screen to CSV or Excel in the web app.
  • The db_sync automation step copies records to an external database in batches.

Checked against the Fieldproxy platform reference on October 18, 2026.

Get your own custom field service management within a day. Tailored to your workflows.

We set up a workspace on your own data and connect your AI or your systems on the call.

Get Demo