Popular automations
What you can automate with Plutio + Webflow
Webflow forms look clean and work great on the front end, but the back end is intentionally minimal. Submissions land in an email notification and a CSV export. Connecting Webflow to Plutio through Zapier turns that raw form data into a client workflow. Here are the automations designers and agencies build most often.
Create contacts from site inquiries
When someone fills out a contact form on a Webflow site, the integration creates a new person in Plutio with their name, email, phone number, and any other fields the form collects. Instead of waiting for a designer or account manager to check email and manually log the lead, the contact shows up in Plutio within seconds of the form being submitted.
Build tasks from new project inquiries
If a Webflow site has a "Start a project" or "Get a quote" form, each submission can create a task in Plutio with the project details pulled directly from the form fields. The task title, description, and due date come from what the prospect submitted, so nothing gets lost in translation between the inquiry and the work that follows.
Route leads to the right team member
If you manage multiple clients or service lines, you can set up separate Zaps for separate Webflow forms. A contact form on a design services page routes to one Plutio board, a quote request on a development services page routes to another, and each goes to the right team member without anyone sorting the inbox.
Turn ecommerce orders into client records
For Webflow ecommerce sites, the "New Order" trigger fires when a purchase comes through. You can use that to create a contact in Plutio, add an invoice, or start a fulfillment task. The order details (customer name, email, product, amount) all flow into Plutio from the Zapier trigger.
Log form submissions as project notes
If you build sites for clients who want a record of their incoming leads, you can Zap each Webflow form submission into a note on an existing Plutio project. Every inquiry lands as a timestamped entry in the project, so your client can see lead volume without needing access to Webflow.
Trigger proposals from quote request forms
For designers who use Webflow to collect project briefs, a form submission can trigger a Plutio task to create and send a proposal. The scope details from the form go into the task description, so the proposal is ready to write without re-reading the email notification from Webflow.
How do I turn Webflow form submissions into Plutio contacts?
Set up a Zap with Webflow's "New Form Submission" trigger and Plutio's "Create Person" action. Every submission on your chosen Webflow form creates a new contact in Plutio with the fields you mapped.
The Webflow form trigger fires instantly. As soon as someone submits a form on the site, Zapier picks up the data and sends it to Plutio. You pick which form (Webflow shows you all forms across the site) and Zapier shows you every field from that form so you can decide what goes where in Plutio.
On the Plutio side, the "Create Person" action lets you fill in the contact's name, email, phone, company, and custom fields. If the form collected a budget range or project description, you can store those in a note attached to the contact record.
Webflow sends the value of every field the person submitted, including any hidden fields you added to the form. Fields the person left blank come through as empty strings, not as errors. Zapier handles empty fields without breaking the contact record in Plutio.
What gets synced
- Name and email mapped from Webflow form fields to Plutio contact properties
- Phone and company if your Webflow form collects them
- Project details, budget, or service type stored in contact notes or custom fields
- Submission timestamp so you know when the inquiry came in
- Form name tagged on the contact so you can track which form or page generated the lead
How do I create projects from Webflow form submissions?
Use Webflow's "New Form Submission" trigger with Plutio's "Create Task" or "Create Task Board" action. Each inquiry becomes a task or full project in Plutio with the scope, timeline, and client details from the form already filled in.
Webflow forms tend to be lean by design, since the platform has no conditional logic built in. If your form collects a project name, deadline, and brief, all three can flow directly into a Plutio task or project board. For more complex intake requirements, you can chain this with a Jotform or Tally form that handles branching logic.
For a simple setup: the Webflow form collects name, email, and project description, and the Zap creates a Plutio task with the description as the task body, assigned to you with a follow-up date you set in Zapier.
You can combine the "Create Person" and "Create Task" actions in a multi-step Zap. Step 1 creates the contact in Plutio, step 2 creates the task linked to that contact. Both fire from a single form submission, and both require Zapier's Starter plan ($29.99/month) for multi-step Zap support.
Mapping Webflow fields to Plutio project details
- Project name or service type mapped to the task or project title
- Project brief or description mapped to the task body or project notes
- Timeline or deadline mapped to the task due date if the form collects it
- Budget stored in project notes or a custom field
How do I connect Plutio to Webflow?
The connection runs through Zapier. You pick Webflow as the trigger, Plutio as the action, map the form fields, and turn the Zap on. Setup takes about 5 minutes.
Before you start, make sure you have a Webflow account with a paid site plan (the free Starter plan caps at 50 lifetime form submissions, which is not enough for ongoing automation), a Zapier account (free plan works for single-step Zaps), and a Plutio account (the free trial gives you full access). You also need at least one Webflow form that has received a test submission so Zapier can see the field names during setup.
Step by step
- Step 1: Log into Zapier and click "Create a Zap"
- Step 2: Search for Webflow and select the "New Form Submission" trigger. Connect your Webflow account when Zapier asks for authorization.
- Step 3: Select your Webflow site from the dropdown. Zapier will show you all the forms on that site. Pick the form you want to connect, then pull a test submission.
- Step 4: Add Plutio as the action app. Choose "Create Person" for a contact, "Create Task" for a task, or "Create Task Board" for a full project.
- Step 5: Connect your Plutio account, map each form field to the matching Plutio field, test the Zap, and turn it on.
Each Webflow form needs its own Zap. If your site has three forms (contact, quote, newsletter), you set up three Zaps. Separate Zaps give you precise control over what each form creates in Plutio.
How much does Plutio + Webflow + Zapier cost?
The minimum setup for ongoing form automation costs around $33 per month (Webflow Basic at $14 + Plutio Core at $19). Zapier's free plan covers single-step Zaps at no extra cost.
Webflow pricing
Webflow's Starter plan is free but caps at 50 lifetime form submissions, which is not workable for ongoing lead capture. The Basic plan at $14 per month (billed annually) unlocks unlimited form submissions and is the minimum for this integration to work reliably. The CMS plan at $23 per month adds a content management system, and the Business plan at $39 per month handles higher traffic and custom code. Ecommerce plans start at $29 per month and are required for the "New Order" trigger.
Zapier pricing
Zapier's free plan supports 100 tasks per month with single-step Zaps (one trigger, one action). For multi-step Zaps (creating a contact and a task from the same submission), the Starter plan costs $29.99 per month and includes 750 tasks. Webflow is not a premium Zapier app, so you don't need a paid Zapier plan just to use this trigger.
Plutio pricing
Plutio's Core plan starts at $19 per month and includes CRM, projects, tasks, invoicing, contracts, and proposals. The Pro plan at $49 per month adds time tracking, client portals, and custom automations. Both plans support the Zapier integration. Plutio also offers a 14-day free trial with full access to every feature.
Bottom line: Webflow Basic ($14/month) + Zapier Free + Plutio Core ($19/month) = $33 per month for the full stack. If you need multi-step Zaps, add Zapier Starter ($29.99/month) for a total of about $63 per month.
What if my Webflow sync breaks?
Check Zapier's task history first. Every Zap run shows a status (success, error, or filtered). If a submission didn't reach Plutio, the error message tells you exactly which step failed.
Most failures come from an expired Webflow connection, a changed form, or hitting Zapier's monthly task limit. Here's how to fix the most common issues.
Common issues and fixes
- Webflow authorization expired: Your Webflow account connection can expire or get disconnected in Zapier. If submissions stop syncing, open the Zap, click the Webflow step, and reconnect your account.
- Form field names changed: If you renamed or deleted fields in your Webflow form, the field mapping in Zapier points to the wrong data. Re-select the form and re-map the fields.
- Site plan downgraded: If your Webflow site got moved to the free Starter plan, form submissions stop flowing after 50 lifetime submissions. Upgrade the site to a paid plan to restore the flow.
- Zapier task limit reached: On the free Zapier plan, you get 100 tasks per month. Once the limit is hit, Zaps pause until the next billing cycle. Upgrade or reduce the number of active Zaps.
Disconnecting the Zap doesn't delete anything in Plutio. Contacts, tasks, and projects already created stay exactly where they are. You can reconnect anytime by turning the Zap back on.
