Formspark Webhook MCP Server

Formspark Webhook

Each stored delivery is one Formspark form submission — a flat JSON object POSTed when someone submits the connected form. Top-level keys mirror the HTML input name attributes from that form; there is no standard envelope, event type, or Formspark-assigned submission id in the webhook body. Tools read what already landed; there is no pull API and no way to submit, edit, or delete form responses from here.

Payload shape

Typical contact-style submissions look like:

Field semantics depend entirely on how the form was built upstream:

• Text fields — plain strings (email, name, phone, website, description, etc.).
• Radio groups — one string value under the shared field name; only the checked choice is sent.
• Checkboxes — each checkbox uses its own name; checked boxes send their value, unchecked boxes omit the key entirely.
• Select / multi-select — string or array depending on whether the form author used indexed names or AJAX array submission.
• Arrays — keys like ingredients[0] / ingredients[1] in HTML, or nested arrays when submitted via AJAX.
• Objects — dot-path keys such as car.manufacturer and car.color, or nested objects in AJAX payloads.
• Hidden metadata — any hidden input name the form author added (version tags, page ids, campaign codes).
• Formtrack UTM fields — when enabled on the form, expect keys such as utm_source, utm_medium, utm_campaign, utm_term, utm_content, ref, referrer, or custom tracking params.
• File fields — URL strings to third-party storage (Uploadcare and similar), not embedded binary. Native <input type="file"> is not forwarded as file bytes.
• Internal redirect keys — _redirect, _error, or _append may appear when the form author included them; they control upstream redirect behavior, not submission content.

First moves

1. Latest report — default for “what form submission arrived last”; read all keys in export.json.
2. Recent reports — list when comparing lead volume, spotting duplicate emails, or scanning submissions over time.
3. One report by id — after listing, when the user points at a specific stored delivery.

Response shape

• export.json — parsed submission body (preferred for field-level questions).
• export.text — raw body when JSON is large or non-object.
• source.captured_at — when the POST landed here; Formspark does not add a standard submission timestamp to the webhook JSON — use this unless the form includes its own date field.

Operational order

1. Start with the latest report — do not guess a report id.
2. If captured_at is older than expected, say so — submissions arrive only when someone submits the form upstream.
3. List recent reports only for history, duplicate suspicion, or explicit compare-by-date asks.
4. Read ## This connection in the skill supplement for form-specific field names (email vs work_email, message vs description, etc.).

Gotchas

• Read-only — cannot submit test entries, mark spam, or change Formspark form settings from here.
• Schema varies per form — field names and nesting differ by HTML; inspect the latest JSON instead of assuming a fixed lead schema.
• Missing keys mean unchecked or empty — absent checkbox keys are normal; do not treat them as data loss.
• No upstream retries — Formspark sends once with a short timeout and does not retry failed deliveries; a missing submission may never arrive.
• Unsigned payloads — the JSON is not cryptographically signed; treat unexpected shapes or junk fields as possible noise unless they match the form you expect.
• One submission per delivery — each POST is one person's form submit, not a batched export.