Get your Fieldproxy data into accounting, BI or a warehouse
Pick the way out
- REST API:
POST /api/readwith an exact-match condition, for example every invoice with statusunpaid. Best for a system that polls. - Read-only SQL over MCP:
run_sqlfor any SELECT up to 500 rows,export_csvfor up to 10,000 rows as a CSV link. Best for analysis and one-off pulls. - The
db_syncautomation step: copies records to an external database in batches, on a schedule or as they change. Best for a warehouse. - Export from any screen to CSV or Excel in the web app. Best for people, not systems.
Poll for unpaid invoices
curl -X POST https://api-india-1.fieldproxy.ai/api/read \
-H "x-api-key: $FIELDPROXY_API_KEY" \
-H "content-type: application/json" \
-d '{"tableName":"invoices","condition":{"status":"unpaid"}}'// Node.js 18+ (built-in fetch)
const res = await fetch("https://api-india-1.fieldproxy.ai/api/read", {
method: "POST",
headers: { "x-api-key": process.env.FIELDPROXY_API_KEY, "content-type": "application/json" },
body: JSON.stringify({
"tableName": "invoices",
"condition": {
"status": "unpaid"
}
}),
})
const out = await res.json()
if (!res.ok) throw new Error(out.message)
console.log(out.rowCount, out.data)# Python 3 (pip install requests)
import os, requests
res = requests.post(
"https://api-india-1.fieldproxy.ai/api/read",
headers={"x-api-key": os.environ["FIELDPROXY_API_KEY"]},
json={
"tableName": "invoices",
"condition": {
"status": "unpaid"
}
},
timeout=30,
)
out = res.json()
res.raise_for_status()
print(out["rowCount"], out["data"])Ask for exactly what you need
run_sql({ "sql": "SELECT i.id, c.company_name, i.total, i.balance_due, i.due_date
FROM invoices i JOIN customers c ON c.id = i.customer_id
WHERE i.balance_due > 0 ORDER BY i.due_date LIMIT 500" })Push on change instead of polling
Pair a trigger with send_webhook or http_request to send each record as it changes. See Get a signed webhook when a job is completed.
Table and column names differ per workspace, because each one is set up around its own business. The names below (jobs, customers, invoices) are typical, not guaranteed. To see the real ones, connect any MCP client and call describe_schema, or ask your Fieldproxy administrator.
Questions
Can I export my data from Fieldproxy?
Yes, the data is yours. Read it with the REST API, query it with read-only SQL, export CSV or Excel from any screen, or sync it to your own database with the db_sync automation step.
Can Fieldproxy sync to a data warehouse or BI tool?
Yes. The db_sync automation step copies records to an external database in batches, and signed webhooks can push each change as it happens.
This is one way, not the only way
This guide shows one common way to do it. A Fieldproxy workspace can be reached from every side, and anything in it can be read, changed or automated:
- REST API: read, insert, update and delete on any table the key allows (REST API reference).
- MCP server: 170+ tools for Claude, ChatGPT, Copilot, Cursor and your own agents, including read-only SQL, proposed writes, automations and app building (MCP tools).
- Automations: 15 trigger types and about 50 step types, with webhooks in and signed webhooks and HTTP calls out (Webhooks and automations).
- Public forms, record links and customer portals for people outside the company (Public forms and links).
- Apps as JSON: new screens, fields, tables and workflows (Apps as JSON).
- Voice and text agents that work from the same data (Voice and text agents).
- Not listed here? Fieldproxy's team builds integrations with the other systems you use as part of setting up your workspace. Tell us what you need.
Checked against the Fieldproxy platform reference on October 18, 2026. Plain text for AI tools: /developers/guides/sync-to-warehouse.md
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