Flowcrafter 1.0-beta-1

Flowcrafter turns WordPress form submissions into visual workflows: enrich leads via HTTP request, route them with Switch rules, update entry fields, and email your team the request with context already attached. Flow Tags move data between steps.

VERSION:
1.0-beta-1
UPDATED:
2026-11-20
DEVELOPER:
Gravity Wiz
LICENSE:
GPLv2 or greater
AUTO UPDATE:
Yes

Description

Who Flowcrafter Is Built For

If you run a WordPress site where form entries pile up faster than anyone can sort them, Flowcrafter is aimed at you. Agencies handling client inquiries, sales teams who live in their inbox, operations staff who copy data from one tab to another: they all share the same problem. The form submission arrives, and then a person has to do everything else by hand. Flowcrafter replaces that manual part with a visual canvas where each step after the submission is a block you connect to the next.

The Flowcrafter WordPress plugin starts at a form submission and lets you chain actions behind it. Look up the company behind an email address through an HTTP request, send each lead down a different path with Switch rules, write the results back into the entry, and email your team a message that already carries the context. Flow Tags carry data from one step to the next, so nothing has to be retyped.

What Is the Real Cost of a Form That Stops at Submit?

A typical contact form collects a name, an email address, and a few lines about a project. That is thin material. Someone on your team reads it, opens a browser, searches for the company, guesses at its size, decides who should reply, and forwards the message with a note. Multiply that by every inquiry and the routine eats hours that should go to actual conversations.

The delays are only part of it. Leads get routed by whoever happens to see the notification first. Details found during research live in a personal notes file rather than on the entry. A colleague opening the entry a week later sees the same bare three fields the visitor typed, with none of the homework attached.

Plenty of automation tools can fire off a notification. Fewer let you build the logic inside WordPress, next to the entries themselves, and keep the enriched result with the original request.

How Does Flowcrafter Handle a Submission From Start to Finish?

Flowcrafter models the process as five kinds of steps. You place them on the canvas, wire them together, and the workflow runs each time a form is submitted.

Form Submitted: the starting point

Everything begins with what the visitor shares. A name, an email, a short description of the project. That is enough to trigger the flow. You do not need to ask for more fields up front just to qualify a lead, because later steps can fill in the gaps.

HTTP Request: fetch the missing context

Point an HTTP Request step at an enrichment service and pass along the email address from the entry. The response can tell you which company the person works for, and the details you get back become available to later steps through Flow Tags. Your visitor never sees this happen and never has to fill in a longer form.

Switch: choose the right path

Switch applies rules to decide where each lead goes next. Split by team size, by region, or by any other value you hold at that point in the run. A small studio can go to one person, a larger organization to another, and a lead from a region you cover through a partner can take its own route. You can also branch on an answer the visitor gave or on the result of an earlier action.

Update Entry Field: keep it all on the record

Once the data is gathered, write it back. Company name, team size, and the assigned team are stored beside the original request, so the entry becomes a complete record in three steps rather than a stub. Open it later and the fields are already filled in.

Send Email: hand it over with context

The last step emails your team. Instead of a bare notification, the message includes the request and the enrichment together. A note might read as an inquiry from Northstar Studio, a team rolling out onboarding to four offices, with the company details already attached. The person replying starts one step ahead.

Core Features

  • Visual workflow canvas: build the sequence of steps by connecting blocks, so the path a submission takes is visible at a glance.
  • Flow Tags: move data between steps, such as an email address going into a request or a returned company name going into an email.
  • HTTP Request step: reach out to an outside service during a run and use what comes back.
  • Switch rules: branch on an answer or on the result of an earlier action, with different paths for different leads.
  • Update Entry Field: store enriched values on the original entry instead of leaving them in an email thread.
  • Entry list tools: filter, group, format, and loop through lists of entries when a workflow needs to work with more than one record.
  • Gravity Forms feeds: update entries and run compatible Gravity Forms feeds as part of a flow.
  • Testing and run history: try your paths before relying on them and inspect what happened in earlier runs.

The testing tools matter more than they sound. A routing rule that sends enterprise leads to the wrong person is worse than no rule at all, and being able to walk a path and read the history afterward lets you catch that before a real prospect does.

Practical Applications

Agencies and studios taking inquiries

A design or development shop can enrich every inquiry with the company behind the email, then route by team size. Solo founders go to a lead who handles small projects, while larger organizations reach a senior contact. The email arrives with the company details in place, which makes the first reply more specific.

Sales and partnership teams

A region-based Switch can assign leads to the right territory owner automatically. The assigned team is saved on the entry, so anyone reviewing the pipeline later can see who took it and why, without asking around.

Operations and internal requests

Forms are not only for prospects. An internal request form can branch on the answer to a dropdown, update a field with the responsible group, and notify that group with the details attached. Entry list tools help when a workflow needs to group or loop through several records before sending a summary.

Developers extending the product

Flowcrafter is released under the GPL, so site owners and developers are free to adapt it and extend it for their own projects. If your workflow depends on a service the stock steps do not cover, the HTTP Request step handles many cases, and the license leaves the door open for deeper customization.

Frequently Asked Questions

Does the enrichment step only work with one specific service?

No. The HTTP Request step is generic, so you point it at whichever enrichment service you use and map the email address into the call. What comes back is available to later steps through Flow Tags. The details you can retrieve depend on the service you choose, not on Flowcrafter.

Can different leads follow different paths in the same workflow?

Yes, that is the job of the Switch step. You define rules based on an answer in the entry or the result of an earlier action, such as team size or region. Each rule leads to its own branch, so one form can feed several routes, each ending in its own update or email.

Where does the enriched data end up after the workflow runs?

It can be written to the original entry using Update Entry Field, next to what the visitor submitted. That keeps the company, team size, and assigned team on the record itself. The run history also lets you review what each step did, which helps when you want to confirm why a particular lead went where it did.

Category: