Custom Webhooks Integration Guide

Complete guide to integrate MyFormConnect with Custom Webhooks

Setup time: 15-30 minutes

Difficulty: Intermediate

Compatible versions: Any HTTPS endpoint

Receive form submission data at your own HTTP endpoint in real time. MyFormConnect sends a POST request to your server whenever a qualifying event fires — you control what happens next. Use this for custom CRM integrations, database writes, notifications, or any bespoke business logic.

Prerequisites

A MyFormConnect account — sign up here
A publicly accessible HTTPS endpoint that accepts POST application/json
Developer Options enabled on your MyFormConnect team — go to Developer Options → Webhooks
Basic familiarity with HTTP and JSON

Integration Methods

Register Endpoint

5 minutes Easy

Deploy a public HTTPS endpoint

Your endpoint must be reachable from the internet and must accept POST requests with a Content-Type: application/json body. It must return a 2xx HTTP response to acknowledge receipt.

Deploy your endpoint on any platform — Node.js, Python, Ruby, PHP, Go, or a serverless function (AWS Lambda, Vercel Function, Cloudflare Worker, etc.)
Confirm the URL uses https:// — HTTP endpoints are not accepted
Make sure the endpoint responds within ~10 seconds; return 200 OK immediately and process work asynchronously if needed
Test locally with a tool like ngrok before deploying to production

Important Note

MyFormConnect retries failed deliveries up to 5 times with exponential back-off (15 seconds, 1 minute, 5 minutes, 15 minutes, 1 hour). If your endpoint is slow or returns a non-2xx status, you will receive retries.

Add the endpoint in MyFormConnect

In your MyFormConnect dashboard, go to Developer Options → Webhooks
Click Add New Endpoint
Enter a Name — e.g. My CRM handler
Paste your endpoint URL in the URL field
Click Save

Important Note

Keep endpoint URLs private. Anyone with the URL can POST data to your server — validate the payload on your side.

Select event types

Choose which events will trigger your endpoint.

Open the endpoint you just saved
In the Event Types field, select one or both:
form_response.created — fires on every submission, irrespective of spam status
lead.created — fires only after spam detection, when a Lead record is created (clean submission with name + email)
Click Save

Important Note

Subscribing to both event types will send two separate webhook calls per qualifying submission — one when the response is stored, and one when the lead is created. Only do this if you need both.

Submit a test and inspect delivery

Trigger a real submission to verify your endpoint receives data correctly.

Submit a test entry through your form on your website
In MyFormConnect, go to Developer Options → Webhooks → [your endpoint] and check Delivery Attempts
A successful delivery shows HTTP 200 and the request/response body
A failed delivery shows the error code — check your server logs to debug

Sample Payloads

Reference only Easy

Both examples below show a Contact Us form submission (name, email, message fields). The envelope structure is the same for all events; only event_type, subject_type, and data differ.

form_response.created — Contact Us form

Fired immediately when the form is submitted. Includes the raw form fields inside data.submitted_data. Fires irrespective of spam status — spam submissions are included.

{
  "event_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "event_type": "form_response.created",
  "subject_id": 1042,
  "subject_type": "FormResponse",
  "data": {
    "id": 1042,
    "form_id": 87,
    "name": "Jane Doe",
    "email": "[email protected]",
    "company_name": null,
    "company_domain": null,
    "submitted_data": {
      "name": "Jane Doe",
      "email": "[email protected]",
      "message": "I'd like to learn more about your services."
    },
    "created_at": "2026-06-13T10:30:00.000Z",
    "updated_at": "2026-06-13T10:30:00.000Z"
  }
}

Important Note

Keys inside data.submitted_data match the name attributes of your HTML form inputs. If your form has a field <input name="company">, it appears as submitted_data.company.

lead.created — Contact Us form

Fired only after spam detection passes and a Lead record is created. Requires the submission to contain both a name and an email address. The raw message body is not present on the lead object.

{
  "event_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "event_type": "lead.created",
  "subject_id": 521,
  "subject_type": "Lead",
  "data": {
    "id": 521,
    "team_id": 3,
    "email": "[email protected]",
    "phone_number": null,
    "source": "Website",
    "status": "New",
    "assigned_to": null,
    "converted_at": null,
    "first_contacted_at": null,
    "last_activity_at": null,
    "name": "Jane Doe",
    "industry": null,
    "location": null,
    "notes": null,
    "created_at": "2026-06-13T10:30:05.000Z",
    "updated_at": "2026-06-13T10:30:05.000Z"
  }
}

Important Note

The message body a visitor typed is not on the lead object. If you need the message, also subscribe to form_response.created and correlate by email/timestamp, or read it directly from the MyFormConnect dashboard.

Handler Examples

15-20 minutes Intermediate

Minimal server-side handler examples. Both respond 200 immediately and log the payload — replace the log statement with your actual business logic.

Node.js (Express)

A minimal Express endpoint that parses the JSON envelope and reads form fields.

const express = require('express');
const app = express();

app.use(express.json());

app.post('/webhooks/mfc', (req, res) => {
  // Acknowledge receipt immediately
  res.status(200).json({ received: true });

  const { event_type, event_id, data } = req.body;

  if (event_type === 'form_response.created') {
    const { email, name, submitted_data } = data;
    const message = submitted_data?.message ?? '';
    console.log(`New submission from ${name} <${email}>: ${message}`);
    // TODO: insert into your database, forward to CRM, etc.
  }

  if (event_type === 'lead.created') {
    const { email, name, phone_number, status } = data;
    console.log(`New lead: ${name} <${email}> — status: ${status}`);
    // TODO: create contact in CRM
  }
});

app.listen(3000, () => console.log('Webhook server listening on port 3000'));

Important Note

Always call res.status(200).json(...) before doing any slow work. If your handler times out before responding, MyFormConnect treats the delivery as failed and retries.

Python (Flask)

A minimal Flask endpoint doing the same thing.

from flask import Flask, request, jsonify

app = Flask(__name__)

@app.route('/webhooks/mfc', methods=['POST'])
def mfc_webhook():
    payload = request.get_json()
    event_type = payload.get('event_type')
    data = payload.get('data', {})

    if event_type == 'form_response.created':
        name = data.get('name')
        email = data.get('email')
        message = data.get('submitted_data', {}).get('message', '')
        print(f'New submission from {name} <{email}>: {message}')
        # TODO: your logic here

    elif event_type == 'lead.created':
        name = data.get('name')
        email = data.get('email')
        print(f'New lead: {name} <{email}>')
        # TODO: your logic here

    return jsonify({'received': True}), 200

if __name__ == '__main__':
    app.run(port=3000)

Important Note

For production use, run Flask behind a WSGI server (Gunicorn, uWSGI) and deploy behind a reverse proxy (Nginx, Caddy). The dev server is not suitable for production.

Idempotency tip

Each webhook delivery includes a unique event_id. Store processed event IDs to avoid handling the same event twice if retries occur.

On receipt, check if event_id already exists in your processed-events log
If it does, return 200 immediately (acknowledge but skip processing)
If it does not, process the event and persist the event_id
This prevents duplicate CRM entries or double emails if MyFormConnect retries a delivery

Important Note

MyFormConnect retries up to 5 times with exponential back-off. Idempotency handling is especially important for operations like sending notification emails or charging customers.

Troubleshooting

Still having issues?

Can't find the answer you're looking for? Our support team is here to help with your integration.

Contact Support

Related Integrations

References & Official Documentation

Next Steps

Configure MyFormConnect

Set up your timezone
Configure lead notifications
Set up advanced spam detection
Add team members to your account

Advanced Features

Use our custom form templates
Try AI Insights for Leads
Integrate with your CRM
Set up automated workflows

Need Help?

Our support team is here to help you with your integration.

Contact Support

Prerequisites

A MyFormConnect account — sign up here
A publicly accessible HTTPS endpoint that accepts POST application/json
Developer Options enabled on your MyFormConnect team — go to Developer Options → Webhooks
Basic familiarity with HTTP and JSON

Integration Methods

Register Endpoint

5 minutes Easy

Deploy a public HTTPS endpoint

Your endpoint must be reachable from the internet and must accept POST requests with a Content-Type: application/json body. It must return a 2xx HTTP response to acknowledge receipt.

Deploy your endpoint on any platform — Node.js, Python, Ruby, PHP, Go, or a serverless function (AWS Lambda, Vercel Function, Cloudflare Worker, etc.)
Confirm the URL uses https:// — HTTP endpoints are not accepted
Make sure the endpoint responds within ~10 seconds; return 200 OK immediately and process work asynchronously if needed
Test locally with a tool like ngrok before deploying to production

Important Note

Add the endpoint in MyFormConnect

In your MyFormConnect dashboard, go to Developer Options → Webhooks
Click Add New Endpoint
Enter a Name — e.g. My CRM handler
Paste your endpoint URL in the URL field
Click Save

Important Note

Keep endpoint URLs private. Anyone with the URL can POST data to your server — validate the payload on your side.

Select event types

Choose which events will trigger your endpoint.

Open the endpoint you just saved
In the Event Types field, select one or both:
form_response.created — fires on every submission, irrespective of spam status
lead.created — fires only after spam detection, when a Lead record is created (clean submission with name + email)
Click Save

Important Note

Subscribing to both event types will send two separate webhook calls per qualifying submission — one when the response is stored, and one when the lead is created. Only do this if you need both.

Submit a test and inspect delivery

Trigger a real submission to verify your endpoint receives data correctly.

Submit a test entry through your form on your website
In MyFormConnect, go to Developer Options → Webhooks → [your endpoint] and check Delivery Attempts
A successful delivery shows HTTP 200 and the request/response body
A failed delivery shows the error code — check your server logs to debug

Sample Payloads

Reference only Easy

Both examples below show a Contact Us form submission (name, email, message fields). The envelope structure is the same for all events; only event_type, subject_type, and data differ.

form_response.created — Contact Us form

Fired immediately when the form is submitted. Includes the raw form fields inside data.submitted_data. Fires irrespective of spam status — spam submissions are included.

{
  "event_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "event_type": "form_response.created",
  "subject_id": 1042,
  "subject_type": "FormResponse",
  "data": {
    "id": 1042,
    "form_id": 87,
    "name": "Jane Doe",
    "email": "[email protected]",
    "company_name": null,
    "company_domain": null,
    "submitted_data": {
      "name": "Jane Doe",
      "email": "[email protected]",
      "message": "I'd like to learn more about your services."
    },
    "created_at": "2026-06-13T10:30:00.000Z",
    "updated_at": "2026-06-13T10:30:00.000Z"
  }
}

Important Note

Keys inside data.submitted_data match the name attributes of your HTML form inputs. If your form has a field <input name="company">, it appears as submitted_data.company.

lead.created — Contact Us form

Fired only after spam detection passes and a Lead record is created. Requires the submission to contain both a name and an email address. The raw message body is not present on the lead object.

{
  "event_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "event_type": "lead.created",
  "subject_id": 521,
  "subject_type": "Lead",
  "data": {
    "id": 521,
    "team_id": 3,
    "email": "[email protected]",
    "phone_number": null,
    "source": "Website",
    "status": "New",
    "assigned_to": null,
    "converted_at": null,
    "first_contacted_at": null,
    "last_activity_at": null,
    "name": "Jane Doe",
    "industry": null,
    "location": null,
    "notes": null,
    "created_at": "2026-06-13T10:30:05.000Z",
    "updated_at": "2026-06-13T10:30:05.000Z"
  }
}

Important Note

Handler Examples

15-20 minutes Intermediate

Minimal server-side handler examples. Both respond 200 immediately and log the payload — replace the log statement with your actual business logic.

Node.js (Express)

A minimal Express endpoint that parses the JSON envelope and reads form fields.

const express = require('express');
const app = express();

app.use(express.json());

app.post('/webhooks/mfc', (req, res) => {
  // Acknowledge receipt immediately
  res.status(200).json({ received: true });

  const { event_type, event_id, data } = req.body;

  if (event_type === 'form_response.created') {
    const { email, name, submitted_data } = data;
    const message = submitted_data?.message ?? '';
    console.log(`New submission from ${name} <${email}>: ${message}`);
    // TODO: insert into your database, forward to CRM, etc.
  }

  if (event_type === 'lead.created') {
    const { email, name, phone_number, status } = data;
    console.log(`New lead: ${name} <${email}> — status: ${status}`);
    // TODO: create contact in CRM
  }
});

app.listen(3000, () => console.log('Webhook server listening on port 3000'));

Important Note

Always call res.status(200).json(...) before doing any slow work. If your handler times out before responding, MyFormConnect treats the delivery as failed and retries.

Python (Flask)

A minimal Flask endpoint doing the same thing.

from flask import Flask, request, jsonify

app = Flask(__name__)

@app.route('/webhooks/mfc', methods=['POST'])
def mfc_webhook():
    payload = request.get_json()
    event_type = payload.get('event_type')
    data = payload.get('data', {})

    if event_type == 'form_response.created':
        name = data.get('name')
        email = data.get('email')
        message = data.get('submitted_data', {}).get('message', '')
        print(f'New submission from {name} <{email}>: {message}')
        # TODO: your logic here

    elif event_type == 'lead.created':
        name = data.get('name')
        email = data.get('email')
        print(f'New lead: {name} <{email}>')
        # TODO: your logic here

    return jsonify({'received': True}), 200

if __name__ == '__main__':
    app.run(port=3000)

Important Note

For production use, run Flask behind a WSGI server (Gunicorn, uWSGI) and deploy behind a reverse proxy (Nginx, Caddy). The dev server is not suitable for production.

Idempotency tip

Each webhook delivery includes a unique event_id. Store processed event IDs to avoid handling the same event twice if retries occur.

On receipt, check if event_id already exists in your processed-events log
If it does, return 200 immediately (acknowledge but skip processing)
If it does not, process the event and persist the event_id
This prevents duplicate CRM entries or double emails if MyFormConnect retries a delivery

Important Note

MyFormConnect retries up to 5 times with exponential back-off. Idempotency handling is especially important for operations like sending notification emails or charging customers.

Troubleshooting

Still having issues?

Can't find the answer you're looking for? Our support team is here to help with your integration.

Contact Support

References & Official Documentation

Next Steps

Configure MyFormConnect

Set up your timezone
Configure lead notifications
Set up advanced spam detection
Add team members to your account

Advanced Features

Use our custom form templates
Try AI Insights for Leads
Integrate with your CRM
Set up automated workflows

Custom Webhooks Integration Guide

Prerequisites

Integration Methods

Register Endpoint

Deploy a public HTTPS endpoint

Important Note

Add the endpoint in MyFormConnect

Important Note

Select event types

Important Note

Submit a test and inspect delivery

Sample Payloads

form_response.created — Contact Us form

Important Note

lead.created — Contact Us form

Important Note

Handler Examples

Node.js (Express)

Important Note

Python (Flask)

Important Note

Idempotency tip

Important Note

Troubleshooting

Still having issues?

Related Integrations

References & Official Documentation

Next Steps

Configure MyFormConnect

Advanced Features

Need Help?

Custom Webhooks Integration Guide

Prerequisites

Integration Methods

Register Endpoint

Deploy a public HTTPS endpoint

Important Note

Add the endpoint in MyFormConnect

Important Note

Select event types

Important Note

Submit a test and inspect delivery

Sample Payloads

form_response.created — Contact Us form

Important Note

lead.created — Contact Us form

Important Note

Handler Examples

Node.js (Express)

Important Note

Python (Flask)

Important Note

Idempotency tip

Important Note

Troubleshooting

Still having issues?

Related Integrations

References & Official Documentation

Next Steps

Configure MyFormConnect

Advanced Features

Need Help?

MyFormConnect - Request Demo

Thank you for scheduling a demo!

MyFormConnect - Any issues?

Thank you for your request!

MyFormConnect - Tailored Solution