How to Connect Your Forms to Anything with Webhooks

You built a form. People are filling it out. Now what?

Most form builders stop at collecting data. You get a spreadsheet, maybe an email notification, and then it's on you to manually move that data into your CRM, your Slack, your email tool — whatever comes next.

That's not automation. That's a copy-paste job with extra steps.

Jot.Space forms have a built-in webhook system that sends form submission data anywhere — the moment someone hits submit. No middleware. No third-party glue. Just your form, your endpoint, your data.

What Is a Webhook?

If you've never used one, a webhook is just a URL that receives data. When something happens (like a form submission), your app sends that data to the URL as a POST request. The receiving system does whatever it wants with it.

Think of it like a push notification for your backend. Instead of checking "did anyone submit my form?" every five minutes, the form tells your system the instant it happens.

How Jot.Space Webhooks Work

When you create a form in Jot.Space, you can attach one or more webhooks in the form settings. Each webhook gets a URL, custom headers for authentication, a payload template with {{field_name}} placeholders, automatic retry logic, and delivery logs.

If you don't set a custom template, every submission sends a clean JSON payload with the form ID, form name, submission ID, timestamp, all field data, and metadata like source URL.

Need the data shaped differently for your CRM or Slack? Use a custom payload template. Jot replaces {{field_name}} placeholders with actual submission values before sending. Send data directly to Slack's incoming webhook format, a CRM's API, or any system that accepts JSON — without middleware.

Real Use Cases

Send new leads to your CRM — point a webhook at your CRM's API and every form submission creates a new contact automatically. Post to Slack when someone books — your team sees it instantly. Trigger an email sequence — new subscriber gets added to your drip campaign immediately. Log submissions to Google Sheets — use a Google Apps Script as your webhook URL. Feed data to your own backend — point the webhook at your API and get raw data in real time.

Why Not Just Use Email Notifications?

Email notifications are fine for knowing someone submitted. They're terrible for automation. You can't parse them programmatically, they get buried or filtered, there's no retry logic, and you can't shape the data. Webhooks give you structured data, instant delivery, automatic retries, and complete control over the format.

Webhook Logs: Know What Happened

Every webhook delivery is logged. You can see the status code, response body, duration, and retry attempts. No more wondering if a submission went through — you have receipts.

Getting Started

Create a form in Jot.Space (Forms add-on required). Go to form settings, add your endpoint URL, optionally set custom headers and payload template, submit a test, and check the webhook logs to verify delivery. Your form is now connected to anything that accepts HTTP.