How to Send Form Submissions to Your CRM via Webhooks

Your lead capture form works great. People are filling it out, and submissions are coming in. But then what? If someone on your team has to manually copy leads from a spreadsheet into your CRM, you're wasting time and losing speed-to-lead—one of the most critical factors in converting prospects.

The solution is webhooks: automated HTTP requests that send form data directly to your CRM the moment someone submits. No manual data entry, no delays, no lost leads. In this guide, we'll explain what webhooks are, how they work, and walk you through setting up automated form-to-CRM connections.

What Are Webhooks?

Think of webhooks as automated messengers. When something happens—like a form submission—a webhook immediately sends that data to another system. Unlike traditional integrations that require polling (constantly checking for new data), webhooks push information in real-time.

Here's the basic flow:

• User fills out your form and clicks submit
• Your form platform packages the submission data as JSON
• A webhook sends this data to a specified URL (your CRM's API endpoint)
• Your CRM receives the data and creates a new contact/lead
• All of this happens in milliseconds, automatically

The Typical Setup Complexity

Setting up form-to-CRM webhooks traditionally requires technical work:

Understanding APIs

Each CRM has its own API with specific authentication requirements, endpoint URLs, and data formats. HubSpot expects data one way, Salesforce another. Without technical knowledge, navigating API documentation is daunting.

Data Transformation

Your form fields probably don't match your CRM fields exactly. Your form might call it "email" while HubSpot expects "email_address." Field mapping and data transformation typically require custom code.

Error Handling

What happens when a webhook fails? Network issues, API rate limits, and invalid data can all cause problems. Robust integrations need retry logic and error notifications—more engineering work.

Maintenance

APIs change. CRM platforms update their endpoints. Authentication tokens expire. Someone needs to maintain these integrations over time.

For many marketing teams, this complexity means either asking engineering for help (and waiting) or using middleware tools that add cost and another platform to manage.

Tapestry Connections: Webhooks Made Simple

Tapestry's Connections feature removes the complexity from webhook setup. Instead of wrestling with APIs, you configure integrations through a visual interface—and Tapestry handles the technical details.

How It Works

• Create a connection in Tapestry and select your destination (CRM, Slack, custom webhook)
• Authenticate with your CRM using OAuth (no API keys to manage)
• Map your form fields to CRM fields using a visual mapper
• Enable the connection and form data flows automatically
• Monitor delivery status and retry failed webhooks from the dashboard

Setting Up HubSpot Integration

Let's walk through connecting a Tapestry form to HubSpot. This same process works similarly for other CRMs.

Step 1: Create a Connection

In your Tapestry dashboard, go to Connections and click "Add Connection." Select HubSpot from the list of available destinations.

Step 2: Authenticate

Click "Connect to HubSpot" and sign into your HubSpot account. Authorize Tapestry to create contacts in your HubSpot instance. OAuth handles authentication securely—no copying API keys around.

Step 3: Map Your Fields

Now map your form fields to HubSpot contact properties. Tapestry shows your form fields on one side and HubSpot fields on the other. Drag to connect them, or use the dropdown to select mappings. Standard fields like email and name are often auto-detected.

Step 4: Configure Options

Set additional options like what happens when a contact already exists (update vs. skip), which HubSpot lists to add contacts to, and any custom properties to set. You can also configure notifications for failed deliveries.

Step 5: Test and Enable

Submit a test form entry and verify it appears in HubSpot correctly. Once confirmed, enable the connection for production traffic. Every future submission flows through automatically.

We had a contractor build our original form-to-Salesforce integration. It broke twice last year when Salesforce updated their API, and each fix cost us $500. The Tapestry connection has been rock-solid for months.

— Marketing Operations Manager

Salesforce Integration

Salesforce integration follows the same pattern, with a few Salesforce-specific options:

• Choose whether to create Leads or Contacts
• Map to custom Salesforce fields and objects
• Set Lead assignment rules
• Configure Lead Source and Campaign attribution
• Handle duplicate matching based on email

For organizations using Salesforce's more complex features (campaigns, custom objects), Tapestry provides advanced mapping options while keeping the interface approachable.

Custom Webhooks

Not using HubSpot or Salesforce? Tapestry's custom webhook option works with any system that can receive HTTP requests:

• Enter your endpoint URL
• Configure authentication (API key, Bearer token, Basic auth)
• Set custom headers if needed
• Map form fields to JSON payload structure
• Test with sample data before going live

This flexibility means you can connect forms to virtually any destination: your data warehouse, internal tools, marketing automation platforms, or custom applications.

Zapier and Make Integration

For destinations without direct API support, Tapestry works with integration platforms like Zapier and Make (formerly Integromat). Send form data to a Zapier webhook, and let Zapier route it to any of its 5,000+ connected apps.

This opens up possibilities like:

• Adding leads to Google Sheets for quick review
• Creating tasks in Asana or Monday.com for sales follow-up
• Sending personalized emails via Mailchimp or Sendgrid
• Posting to Slack channels for real-time notifications
• Triggering complex multi-step workflows

Monitoring and Troubleshooting

Webhooks can fail for various reasons—network issues, authentication problems, invalid data. Tapestry provides visibility into webhook health:

Delivery Logs

Every webhook request is logged with its payload, response, and timing. See exactly what was sent and how the destination responded. This makes debugging straightforward.

Automatic Retries

When a webhook fails due to a temporary issue (network timeout, rate limit), Tapestry automatically retries with exponential backoff. Most transient failures resolve without intervention.

Failure Alerts

Configure email or Slack notifications for persistent failures. Get alerted when something needs attention, rather than discovering days later that leads weren't flowing.

Getting Started

Ready to automate your form-to-CRM workflow? Sign up for Tapestry and set up your first connection. Whether you're using HubSpot, Salesforce, or any other system, you can have leads flowing automatically in minutes.

For more on building the forms themselves, check out our guide on creating lead capture forms without a developer. And to understand what happens after forms are live, explore automatic form analytics.