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.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.