WordPress lead routing with Zapier
A website enquiry needs a clear next action and someone responsible for it. Norml builds a routing workflow around your WordPress form, qualification fields and sales ownership rules. Zapier coordinates the handoff; Pipedrive holds the sales record and Slack makes the assignment visible.
A few clients we’ve worked with
What we do
Assign website enquiries using agreed service and region rules, record the handoff in Pipedrive, and alert the responsible team in Slack.
Give each enquiry a defined route.
Start with the decisions your team already makes: which enquiries belong to which service, territory or account owner, and which need a person to review them.
- Solution
- Automations
- Tools
- WordPress, Zapier, Pipedrive, Slack
- Trigger
- An accepted submission arrives through the website form's supported Zapier connection or a verified webhook.
- Outcome
- The workflow checks the enquiry, finds or creates the agreed Pipedrive records, assigns an owner, and posts an internal Slack alert with a record link.
- Form data and qualificationWe map the submission ID, contact details, requested service and routing fields. The form plugin determines the available trigger; WordPress itself does not supply a universal form-submission event. Spam and incomplete records follow an agreed review route before sales actions run.01
- Assignment rulesService and region rules produce one accountable owner. Existing-account ownership can take priority when the business requires it. We define rule order, conflicting matches and a fallback queue so a new dropdown value cannot quietly leave an enquiry unassigned.02
- CRM handoff and team alertPipedrive receives the agreed person, lead or deal information, with an activity when that is part of the scope. Slack gets a concise assignment notice after the CRM write succeeds. Sensitive free-text fields stay out of the message unless they are needed.03
Client reviews
“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
Agree on ownership before connecting the form.
- Source records and permissionsProvide the form plugin, example submissions, Pipedrive field definitions and active owner list. Connection access must cover the selected CRM actions and Slack channel. We check the required plugin and Zapier plan capabilities before committing to a route.01
- Duplicate and failure policyA stable submission ID identifies a delivery already processed. Contact matching is a separate decision: one person can submit different enquiries. The scope includes a processing record and recovery steps for partial runs, including a CRM success followed by a Slack failure.02
- Follow-up stays with your teamThe default workflow assigns internal work. Prospect emails, marketing enrolment, enrichment and round-robin capacity calculations require their own rules and approval. A named administrator owns routing changes and the unresolved-enquiry queue after handover.03
Test the handoff with representative enquiries.
- [Map the routes]Step 01
Review valid submissions, incomplete details and existing customers. Record the expected owner, CRM action and alert for each example before building the Zap.
- [Build and replay]Step 02
Configure the supported trigger, branching and destination fields. Test a repeated submission, conflicting rules and a rejected CRM write without contacting prospects.
- [Verify and hand over]Step 03
Check source IDs against destination records and alerts. Document how to pause routing, correct a record and resume only the missing action after a failure.
The people who do this work.
Meet the whole teamNo account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedRelated services.
From the Norml blog.
Lead-routing questions.
How are leads assigned?
Assignment follows the approved fields and rule order. For example, a requested service can select a team while an existing account owner overrides the general region rule. We test overlaps explicitly so two branches do not create competing assignments.
What happens to duplicate or incomplete enquiries?
A repeated delivery of the same submission is suppressed. A new enquiry by an existing contact can still create separate work. Missing qualification details and unmatched routes go into an owned review queue rather than receiving guessed values.
Can you use our existing WordPress form?
We check its documented trigger or webhook support and test the fields it provides. A form-specific connector may be needed. Compatibility is confirmed for your plugin and account configuration before the implementation scope is agreed.
Will this send sales emails?
No outbound email is included in the default handoff. Your team receives the CRM assignment and internal alert; any automatic prospect communication is scoped separately with its content and eligibility rules.
Define your enquiry handoff.
Bring your form URL, routing rules and examples of enquiries that need different owners. We will map the decisions and confirm a supported implementation route.