Web forms and CRM lead capture

02What the module does

• Website inquiries straight into the CRMA form on your website sends data to Draivix via the API, and the system creates a lead—a potential customer record—in the CRM. No inquiry ever gets lost in an email inbox.
• Every detail in the right fieldYou map form fields to name, email, phone, company, IP address and source page. The lead fields are populated automatically so nobody has to retype them.
• Leads arrive pre-sortedThe form settings determine the lead’s status, source and tags, defaulting to status “new” and source “web”. Sales reps can immediately see where every inquiry came from.
• Each inquiry recorded only onceEvery submission carries its own identifier. If the same submission arrives again, the system returns a duplicate status instead of creating a second lead, so your sales rep never works the same inquiry twice.
• Full visibility into every submissionEvery submission is logged with a status: pending, created, duplicate, failed or rejected. In the submission list, you can see everything that arrived and how it was handled.
• See why a submission was rejectedThe system rejects invalid data and saves the submission with a rejected status along with the validation error details. You can easily trace what went wrong.
• Inquiries come with a ready-made taskOnce a lead is created, the form can create a follow-up task for a designated user. When enabled, the sales rep has the next step waiting right in their task list.
• Instant alert for the sales repWhen a lead is created, the system can send an in-app notification if configured on the form. The sales rep finds out about the new inquiry immediately without having to watch the lead list.
• Leads are kept even if a follow-up step failsIf creating the follow-up task or notification fails, the error is logged on the submission while the newly created lead stays intact. You never lose an inquiry because of a secondary error.
• Shared key blocks unauthorized submissionsYou can protect a form with a shared secret key that the sender must pass in the request header. Without it, the system rejects the request.
• Rate limits stop form floodingForm intake enforces its own submission rate limit per domain and IP address, setting a hard cap against repeated spam submissions.
• Mandatory consent on the formThe store form requires a name, email, message and consent, and responds externally only with a confirmation of receipt—without exposing internal data. Submissions without consent are not accepted.
• All 12 capabilities in a single module

05Frequently asked questions