Update a job's status in Fieldproxy and trigger automations

Update one job#

An administrator creates a key in the web app under Settings, Security, API keys: give it a name, an expiry, only the operations this guide needs, and optionally only the tables it touches. Keep it in an environment variable, FIELDPROXY_API_KEY. Your API base is your workspace's regional host, for example https://api-india-1.fieldproxy.ai (India) or https://api-us-east-1.fieldproxy.ai (US East). This guide needs the Update operation.

condition picks the rows, data is one object of the columns to set. Match on the id (or your own reference) to change exactly one job.

curl -X POST https://api-india-1.fieldproxy.ai/api/update \
  -H "x-api-key: $FIELDPROXY_API_KEY" \
  -H "content-type: application/json" \
  -d '{"tableName":"jobs","condition":{"id":1042},"data":{"status":"completed"}}'

// Node.js 18+ (built-in fetch)
const res = await fetch("https://api-india-1.fieldproxy.ai/api/update", {
  method: "POST",
  headers: { "x-api-key": process.env.FIELDPROXY_API_KEY, "content-type": "application/json" },
  body: JSON.stringify({
    "tableName": "jobs",
    "condition": {
      "id": 1042
    },
    "data": {
      "status": "completed"
    }
  }),
})
const out = await res.json()
if (!res.ok) throw new Error(out.message)
console.log(out.rowCount)

# Python 3 (pip install requests)
import os, requests

res = requests.post(
    "https://api-india-1.fieldproxy.ai/api/update",
    headers={"x-api-key": os.environ["FIELDPROXY_API_KEY"]},
    json={
      "tableName": "jobs",
      "condition": {
        "id": 1042
      },
      "data": {
        "status": "completed"
      }
    },
    timeout=30,
)
out = res.json()
res.raise_for_status()
print(out["rowCount"])

{
  "message": "Update successful",
  "rowCount": 1,
  "table": "jobs",
  "tenant": "<workspace-id>"
}

Automations fire on the change#

Each changed row fires the workspace's automations: entity_event rules, and for /api/update also status_transition and field_threshold rules. So moving a job to completed can raise the invoice, ask for a review or tell another system, with no extra call from you.

{
  "name": "Tell our ERP when a job is completed",
  "enabled": true,
  "trigger_type": "status_transition",
  "trigger_config": { "table": "jobs", "field": "status", "to": "completed" },
  "action_spec": {
    "steps": [
      { "type": "send_webhook",
        "url": "https://erp.example.com/hooks/fieldproxy",
        "secret": "{{secrets.ERP_WEBHOOK_KEY}}",
        "body": { "event": "job.completed", "job_id": "{{trigger.row.id}}" } }
    ]
  }
}

Good to know#

• One call can change many rows: {"status": "open"} as the condition updates every open row (a test call updated 1,000). Match on an id when you mean one.
• A condition that matches nothing returns 200 with rowCount 0, not an error. Check rowCount.
• An unknown column or a constraint violation returns 500 with Update failed and the database error.

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#

Checked against the Fieldproxy platform reference on October 18, 2026. Plain text for AI tools: /developers/guides/update-job-status.md