What we do
Tools
Industries
Department
How we workLet's talk →
Home/Wix/Wix Automations, From Simple Rules to Velo Code

What Wix Automations Can Do Now, and the Steps That Still Need a Developer

If you last looked at Wix Automations a while ago, it has grown. The new builder takes IF/ELSE conditions, delays and several actions in one flow, and besides emails and coupons it can send an HTTP request, start from an incoming webhook or run your own Velo code. That moves the wall rather than removing it. Once a step talks to QuickBooks, a CRM or a warehouse, someone has to own the login, the data it sends and what happens when it fails.

Rules that stay inside Wix vs. steps that leave it

No code needed

Inside the builder

  • Triggers come from the Wix apps on your site, so a site with Stores and Bookings sees order, cart and booking triggers.
  • Thank-you, welcome, abandoned-cart and overdue-invoice emails, coupons, chat auto-replies and tasks for your team.
  • IF/ELSE conditions, with a path for when the condition isn't met, and delays such as a coupon three days after the first email.
  • A Zapier connection for posting to Slack, a sheet or another app on each run.
Someone technical owns it

Steps that call out

  • Send HTTP request pushes data to another system, which has to accept it and authenticate it.
  • Webhook received starts a flow from outside, once you paste a sample JSON payload and set its structure.
  • Run Velo Code needs Velo turned on and the site published, and the code is yours to write and maintain.
  • Any decision that depends on data held somewhere else, such as a balance, a stock count or a customer's history.

If the rule only needs what Wix already knows, build it yourself in the builder. If it needs to ask or tell another system something, plan for code and for someone who watches it.

Which rule belongs in which Wix tool

The rule you want Where it belongs What to watch
Email a coupon to carts left behind The builder, with a delay step before the email. Very little. This is the job the builder was made for.
Treat big orders differently from small ones An IF/ELSE condition in the builder. A condition can only test data the trigger carries. A customer's lifetime value in your CRM isn't on the order.
Post new form leads to Slack or a spreadsheet Zapier, triggered from the same Wix events. Each run uses Zapier tasks, so busy forms add to the bill.
Create an invoice in QuickBooks or a deal in your CRM A small backend or app working against the Wix and accounting APIs. QuickBooks and most CRMs issue logins that expire, and a fixed header in an HTTP step can't renew one.
Check stock somewhere else before confirming Run Velo Code, or backend code it calls. When the outside system is slow or down, the code has to decide what the customer sees. Write that path on purpose.
Start a Wix flow when something happens elsewhere The Webhook received trigger. Wix's guide doesn't describe signing or a secret, so the unique URL is the only protection. Keep it as private as a password.

Wix automations that pass the test run and then go quiet

The webhook URL changed under you

How you'll know: The outside service still posts, and Wix never runs the flow.

Fix: Switching an automation to another trigger and back to Webhook received gives it a new URL. Update the sender every time, or leave the trigger alone once it's live.

The payload grew a field Wix never learned

How you'll know: A new value from the other system never appears in the email or the next step.

Fix: Wix doesn't update the payload structure on its own. Paste a fresh sample, preview it, save it, and remap the field.

A login that lasts an hour

How you'll know: The HTTP step to QuickBooks or a CRM works on the day you build it and returns errors from the next morning.

Fix: The token you pasted expired. Put a small service in between that holds the account connection, renews it, and takes simple calls from Wix.

Nobody hears about failed runs

How you'll know: You find out a week later, from a customer who never got their confirmation.

Fix: Firewalls and outages on the other side do block outgoing requests. Log every call your code makes, and alert someone when one fails.

Questions people ask

What are Wix Automations?

The rule builder in your Wix dashboard. You pick a trigger from one of your site's apps, such as a form submission, an order or a booking, then the actions that follow: an email, a coupon, a chat reply, a task for your team. The newer builder lets one automation hold conditions, delays and several actions.

Is Wix's email automation good enough for marketing?

For standard sequences, yes: welcome emails, thank-yous, abandoned-cart reminders and coupons, with delays between them. Stores that want deep segmentation or long nurture programs tend to move to a dedicated email tool later.

Can Wix Automations connect to Zapier?

Yes. Wix connects to Zapier, so the same site events can post a Slack message, add a spreadsheet row or start something in another app, without code.

Can Wix Automations use if/else conditions?

Yes, in the new automation builder. You can add IF/ELSE conditions and choose what happens when a condition isn't met. The condition can only look at data the trigger brings with it.

Do I need Velo to use Wix Automations?

Not for the standard triggers and actions. You do need Velo turned on, and a published site, to use the Run Velo Code action, and Wix asks for Velo before data can be sent out by webhook.

Can I build automation beyond what Wix Automations offers?

Yes. Velo code and custom integrations against Wix's APIs can check outside systems, branch on what they find and keep a record of each run. n-frames builds those for Wix sites when the step has to reach QuickBooks, a CRM or stock held elsewhere.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.