Send website form leads into Fieldproxy

Why a webhook, not an API key#

A form on a public website must never hold an API key. An automation with a webhook trigger gets its own URL instead. It needs no sign-in, can require a shared secret in the x-automation-secret header, and only does what its steps say, so the worst a stranger can do is submit a request.

1. Create the rule#

Create the automation from any MCP client (save_automation) or ask your Fieldproxy team. The steps read the posted fields as {{trigger.body.<field>}}.

{
  "name": "Website request to service request",
  "enabled": true,
  "trigger_type": "webhook",
  "trigger_config": { "secret": "<your-shared-secret>" },
  "action_spec": {
    "steps": [
      { "type": "create_record", "table": "service_requests",
        "values": {
          "contact_name": "{{trigger.body.name}}",
          "phone": "{{trigger.body.phone}}",
          "description": "{{trigger.body.issue}}",
          "status": "new"
        } }
    ]
  }
}

2. Post to it#

curl -X POST "https://<api-host>/automation/hooks/<workspace-id>/<rule-id>" \
  -H "Content-Type: application/json" \
  -H "x-automation-secret: <your-shared-secret>" \
  -d '{"name": "Dana Lee", "phone": "+15550100", "issue": "No cooling, unit 4B"}'

# => 202 {"accepted": true}   (the rule runs in the background)

The webhook answers 202 straight away and the rule runs in the background. The rule must be switched on.

From a form builder or Zapier-style tool#

Any tool that can send a JSON POST with a custom header works: point its webhook action at the URL, add the x-automation-secret header, and map the form fields to the names the rule reads.

Prefer a hosted form?#

Fieldproxy public forms are open forms anyone with the link can fill in, with no code on your side. See Public forms and links.

Questions#

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