Drupal Webform Module Setup: Forms, Handlers, Integrations

With 500+ daily submissions on a Drupal site, managers spend up to 3 hours manually distributing leads. Validation errors, lost data in CRM, unstructured responses — typical pain for Drupal site owners. According to our estimates, up to 30% of leads go to competitors due to processing delays. The Drupal Webform setup with custom form handlers solves these tasks—but without proper configuration, forms only create an illusion of automation. Our Webform Drupal integration includes custom WebformHandler for seamless CRM connection. Pricing starts at $500 for a simple form and up to $2000 for complex integrations, reducing lead handling costs by 80%. For example, a client saved $8,000 monthly after setting up Webform with CRM integration, increasing conversion by 25% and cutting processing time from 5 minutes to 10 seconds.

What Problems Does Webform Solve?

Loss of leads due to manual processing

When using plain HTML forms without Webform, managers must copy data from email into CRM. This takes 5-10 minutes per submission, and at 100 submissions per day — 8-16 man-hours. Webform with a webhook handler transfers data to CRM in seconds, completely eliminating manual entry.

Validation errors and unstructured data

Without frontend and backend validation, empty or incorrect fields get into CRM. Webform provides over 50 element types with validation: required fields, input masks, minimum/maximum length. For example, a phone field with mask +7 (999) 999-99-99 reduces incorrect numbers by 70%.

Complex scenarios with conditional logic and multi-step

When the form should adapt to user choice — when "Support" is selected, an order number appears; when "Sales" — a company name. Implementing this with plain HTML+JS is complex and unreliable. Webform supports the states API: fields are hidden or become required depending on other field values. In one project, we configured a 5-step form where each step depends on the previous, reducing abandonment by 40%.

How to Configure Webform?

The entire process includes six stages:

1. Requirements analysis — clarify load (up to 1000 submissions/day), field types, dependencies, handlers, CRM (AmoCRM, Bitrix24, Salesforce, or custom).
2. YAML configuration design — versioned in Git.
3. Form creation via UI or YAML.
4. Handler configuration — email, webhook, custom.
5. Testing 15+ scenarios (including edge cases).
6. Deployment with monitoring and logging.

Example of a minimal feedback form YAML:

elements: | name: '#type': textfield '#title': 'Name' '#required': true '#maxlength': 100 email: '#type': email '#title': 'Email' '#required': true phone: '#type': tel '#title': 'Phone' '#input_mask': '+7 (999) 999-99-99' message: '#type': textarea '#title': 'Message' '#required': true '#minlength': 10 '#rows': 5 department: '#type': select '#title': 'Department' '#options': sales: Sales support: Support other: Other 

Conditional logic — show company field only for legal entities:

 company_name: '#type': textfield '#title': 'Company name' '#states': visible: ':input[name="client_type"]': value: business required: ':input[name="client_type"]': value: business 

Handler configuration

Email handler — standard, sends an HTML email with data. Webhook handler — sends data to CRM REST API. Custom PHP handler — when additional actions are needed: logging, sending to Telegram, enriching data from an external API. Example of a custom handler for CRM:

// src/Plugin/WebformHandler/CrmWebformHandler.php namespace Drupal\mymodule\Plugin\WebformHandler; use Drupal\webform\Plugin\WebformHandlerBase; use Drupal\webform\WebformSubmissionInterface; /** * @WebformHandler( * id = "crm_integration", * label = @Translation("CRM Integration"), * category = @Translation("External"), * description = @Translation("Sends submission to CRM"), * cardinality = WebformHandlerBase::CARDINALITY_SINGLE, * results = WebformHandlerBase::RESULTS_PROCESSED, * ) */ class CrmWebformHandler extends WebformHandlerBase { public function postSave(WebformSubmissionInterface $webform_submission, bool $update): void { $data = $webform_submission->getData(); \Drupal::httpClient()->post('https://api.example.com/leads', [ 'json' => [ 'name' => $data['name'], 'email' => $data['email'], 'message' => $data['message'], 'source' => 'drupal-webform', ], ]); } } 

This handler processes requests 10 times faster than email, which is critical under high load.

Common mistakes in Webform configuration

Setup Deliverables

When ordering Webform setup, you get:

• YAML configuration of all forms (versioned in Git);
• Configured handlers (email, webhook, custom);
• Integration with CRM/Telegram/other services;
• Testing of 15+ scenarios (including edge cases);
• Documentation on form structure and handlers;
• Operator training (showing Results interface);
• Monitoring and logging for 2 weeks after deployment.

Timeline: simple form with email — 3-5 hours. Integration with CRM via custom handler — plus 1-2 days. Cost is calculated individually; typical range $500-$2000.

A ready-made Webform is not just lead collection, but a full pipeline: data enters CRM instantly, validation errors eliminated, load up to 1000 submissions per day causes no issues. We guarantee the configured form will work flawlessly for 12 months. Order Webform setup — get a working form in 2 days. Contact us for a consultation on your project.

Additional resources: Webform module on Drupal.org, Webhook on Wikipedia.