Share
Virtual Assistant + Make Automation: How the Combo Works
Most VA conversations focus on task delegation. Most automation conversations focus on eliminating tasks entirely. The founders who move fastest are the ones who figure out that the real advantage isn't choosing between delegation and automation — it's combining both in a single hire.
A virtual assistant who uses Make automation — someone who executes tasks and builds the workflows that eliminate those tasks over time — is a fundamentally different hire from a traditional VA. Here's how the combination actually works and what Jarvis builds for clients.
What Make.com Actually Does (and What It Can't)
Make.com (formerly Integromat) is a workflow automation platform that connects apps and runs automated processes. When a lead fills out a form, Make can automatically add them to your CRM, send a confirmation email, notify your team in Slack, and schedule a follow-up — without anyone touching anything.
What Make can do:
- Connect 1,500+ apps via API without code
- Trigger automated actions based on events (form submissions, new emails, new CRM records, Shopify orders)
- Run scheduled automations (daily reports, weekly follow-up sequences, monthly data syncs)
- Transform and route data between systems
- Build multi-step workflows with logic (if/then branching, filters, error handling)
What Make can't do:
- Make judgment calls that require human context
- Handle situations outside its defined workflow logic
- Replace the relationship-building and communication work a VA does
This is exactly why VA + Make is more powerful than either alone. Make handles the repeatable, rule-based work. Your VA handles the judgment-call work and builds the Make workflows that progressively reduce the judgment-call work over time.
What a VA Trained in Make Can Build for Your Business
Lead intake automation
When a prospect fills out your contact form, Make automatically creates a CRM record, assigns them to a follow-up sequence, sends a confirmation email, and notifies your VA to review the lead. Zero manual data entry. Your VA's job shifts from entering data to reviewing lead quality.
One ecommerce founder we work with was manually entering 30-50 leads/week into his CRM from three different form sources. His Jarvis VA built a Make workflow that consolidated all three into a single CRM pipeline with automatic tagging and sequence enrollment. That 4 hours/week of manual data entry is now zero. See how Jarvis approaches automation for ecommerce.
Follow-up sequence automation
Instead of your VA manually sending follow-up emails on day 1, day 3, and day 7, Make runs the sequence automatically based on triggers (lead didn't reply, meeting wasn't booked, proposal wasn't signed). Your VA sets up and maintains the sequences; Make executes them.
Reporting automation
Weekly business metrics — revenue, leads, conversion rates, customer service response times — pulled from multiple sources and assembled into a single report automatically. Instead of your VA spending 2 hours building a weekly report manually, Make runs the data pull and formats the report. The VA reviews and adds commentary.
Shopify-to-CRM sync
For ecommerce businesses: when a customer makes a purchase, Make creates or updates their CRM record, tags them by product category, and enrolls them in the post-purchase email sequence. When they abandon a cart, Make sends a notification to your VA for manual follow-up on high-value carts.
Client onboarding automation
New client signed — Make sends the welcome email, creates the project in your PM tool, sends the intake form, schedules the onboarding call, and notifies your VA. Your VA handles the personal touches; Make handles the logistics.
How Jarvis Trains VAs in Make
Jarvis VAs arrive pre-trained in Make before placement. The training covers:
- Scenario structure and module logic
- Common app integrations (Google Sheets, Gmail, Slack, GoHighLevel, Shopify, Notion, HubSpot, Calendly)
- Error handling and webhook configuration
- Data mapping and transformation
- Testing and debugging workflows
This means your VA can build their first workflow in the first 30 days — not after six months of learning on the job. See the full onboarding timeline.
Want to see which of your workflows could be automated with Make?
We'll map your top repeatable processes and show exactly what a Jarvis VA would build in the first 60 days.
The Compound Effect Over 6 Months
Month 1: VA takes over task execution. First Make workflow live (usually lead intake or follow-up sequences). Manual data entry starts disappearing.
Month 2-3: Second and third Make workflows built. Reporting automated. VA shifts from reactive execution to proactive operations management.
Month 4-6: 60-70% of the VA's original task list is now automated. VA shifts to higher-leverage work — outreach, client relationship support, content operations, analytics review.
The result at month 6 is not just the same work being done by someone else. It's a meaningfully smaller operational footprint, running with less human time, producing more consistent output.
See real examples of this in our case studies and the full range of automation Jarvis builds.
Make vs. Zapier for VA-Built Automation
Both are workflow automation platforms. For VA-built automation at scale, Make is typically the better choice:
| Factor | Make | Zapier |
|---|---|---|
| Pricing | Lower per operation | Higher per task |
| Complexity | Handles multi-step complex workflows | Better for simple 2-step automations |
| Error handling | Built-in | Requires workarounds |
| Data transformation | Strong | Limited |
| Learning curve | Steeper | More beginner-friendly |
For simple two-step automations (form submitted, email sent), Zapier is faster to set up. For complex multi-step workflows with branching logic and data transformation, Make is more powerful and significantly cheaper at scale. Jarvis VAs are trained in both. See the products and services Jarvis offers.
Frequently asked questions
What is Make automation and how does a VA use it?
Make.com is a workflow automation platform that connects apps and runs automated processes. A VA trained in Make builds scenarios that automatically execute tasks — adding leads to CRMs, sending follow-up sequences, generating reports, syncing data between platforms — so those tasks stop requiring manual execution.
Can any VA learn Make automation?
With the right training, yes. Jarvis trains VAs in Make before placement, so they arrive capable of building and maintaining automation workflows. A VA without this training would need 3-6 months to develop the skills on the job, which is why pre-trained placement matters.
What processes are best suited for Make automation?
Any process that is: triggered by an event (form submission, new email, calendar event), involves moving data between systems, runs on a predictable schedule, or follows defined if/then logic. Lead intake, follow-up sequences, reporting, onboarding workflows, and data sync are the most common starting points.
What's the difference between Make and Zapier?
Both connect apps and automate workflows. Make handles more complex multi-step workflows with better error handling and lower pricing at scale. Zapier is easier to set up for simple two-step automations. Jarvis VAs are trained in both, and use the right tool for the complexity of the workflow.
How long does it take a Jarvis VA to build their first Make workflow?
With pre-training before placement, most Jarvis VAs have their first workflow live in the first 30 days. More complex multi-scenario automation stacks typically take 60-90 days to build out fully, as they're layered in alongside ongoing task execution.
Ready to Build an Automated Business?
The combination of a trained VA and Make automation is how founders running $10K-$200K/month businesses remove themselves from the operational day-to-day without losing control or quality. Jarvis builds this into every placement from day one.
Further Reading
Real Make Workflows Your VA Can Build This Week
Theory is useful. Real examples are better. Here are five Make automations that Jarvis VAs commonly build for clients — each one saving 3–8 hours per week once running.
Lead routing from Facebook/Instagram Ads. When a lead submits a form from a Meta ad, Make catches the webhook, creates a contact in GoHighLevel, assigns it to the right pipeline, and sends an immediate SMS + email from the GHL sequence. The VA builds this once; it runs forever. Every new ad lead gets contacted in under 60 seconds — no manual work, no missed leads overnight.
Client onboarding sequence trigger. When a new deal moves to "Closed Won" in GHL, Make fires: sends the welcome email, creates the client folder in Google Drive, creates a Notion task page for the account, and adds a task in Asana for the account manager. What used to be 30 minutes of manual setup per new client takes zero minutes.
Weekly report assembly. A scheduled Make scenario runs every Monday morning: pulls last week's data from Google Analytics + Meta Ads Manager API, populates a Google Sheets report template, and sends a Slack notification to the account team. The VA reviews the assembled data, adds commentary, and sends to the client. Build time: 2–3 hours. Weekly time saved: 4–6 hours.
Invoice payment follow-up. When a Stripe invoice goes overdue by 3 days, Make sends a personalized follow-up email. At 7 days, sends a second follow-up. At 14 days, creates a task for the VA to make a personal call. The VA sets the thresholds and the message copy; the automation handles the timing. Late invoice rate typically drops by 30–50% in the first 60 days.
Review request after service delivery. When an order is marked fulfilled in Shopify (or a service ticket closed in Zendesk), Make waits 3 days and sends a personalized review request email. No manual work. Review volume increases steadily without anyone thinking about it.
The Right Way to Think About VA + Automation
The mistake most business owners make when they start using automation: they automate tasks they should have delegated to a VA, and delegate tasks they should have automated. The result is a VA doing repetitive, mechanical work that a Make scenario would handle better — and automation trying to handle judgment calls that need a human.
The clear split: automate data movement and triggered sequences; use your VA for judgment and communication. Data that flows predictably between two connected systems → automate. Any task that requires reading context, adjusting tone, or making a decision based on variable inputs → VA.
When you get this right, your business has a real operations layer — not just a VA doing manual work, and not just automations running without oversight. See how Jarvis builds this for clients on the automation page and the full process here.