Getting Started
Getting Started With Zapify Automations
Zapify turns "when this happens, do this" into a working WordPress automation without code. This page takes you from an empty install to a live automation in about five minutes: install the plugin, build one automation from a trigger and an action, set it live, and confirm it ran. An automation is Zapify's unit of work — one or more triggers plus an ordered list of actions.
What is a Zapify automation?
A Zapify automation is one or more triggers (the events to watch for) plus an ordered list of actions (what to do in response). It is not called a "recipe", "zap", or "workflow" — Zapify calls it an automation throughout the admin, the builder, and the logs. Each trigger and each action carries its own state — Live, Off, or Draft — so you can build and test a step before it affects anything.
Install Zapify
Install and activate Zapify like any other plugin — from Plugins → Add New, or by uploading the ZIP. On activation, Zapify adds a top-level Zapify item to the admin menu with four screens:
| Screen | What it is for |
|---|---|
| Automations | The list of your automations, and where you create new ones. |
| Templates | A gallery of ready-made automations to start from. |
| Logs | Every run, with what fired it and what each action did. |
| Settings | Data, logging, connections, webhooks, tools, and system status. |
Nothing runs until you build something and set it live, so activating Zapify is safe on a busy site.
Build your first automation
Go to Zapify → Automations and choose Add new. This opens the visual Builder over the Automations screen.
1. Choose what it runs for
The first thing Zapify asks is who the automation is about:
- Logged-in users — the ordinary case. The run is attributed to a person, and per-user limits work.
- Everyone — for things that happen without a logged-in visitor, such as an inbound webhook.
- On a schedule — no trigger at all; it runs on a clock. (PRO)
- In bulk — runs once for every member of a set, such as every subscriber. (PRO)
You cannot change this later once you have built on it, because the choice decides which triggers are even available.
PRO feature
Scheduled and bulk automations are Zapify PRO features. The logged-in and everyone modes are free.
2. Add a trigger
Under When this happens, choose Add trigger. Pick an integration, then pick the thing to watch for. The free build includes 23 triggers across WordPress, WooCommerce, Gravity Forms, Contact Form 7, WPForms, Fluent Forms, Webhooks, and Utilities — see Triggers and actions.
Integrations you do not have appear too, marked Not installed or Pro. You can open them to see exactly what they offer before deciding whether it is worth installing anything.
You can add more than one trigger and choose whether all of them or any of them must match. Multiple triggers with ALL/ANY matching are free.
3. Add an action
Under Do this, choose Add action and pick what should follow. The free build includes 18 actions.
Fields that accept a token show a {} button. A token is a value carried from the trigger — the customer's email address, the order total, the post title — and it is written like {{trigger:23:USER_EMAIL}}. You rarely type these; pick them from the list and Zapify writes the reference.
4. Set it live
Use the status control at the top to switch the automation from Draft to Live. Zapify refuses to go live if the automation could never work — no trigger, no action, a required field left empty, or a condition nobody finished — and it tells you which one.
Watch it run
Zapify → Logs shows every run: what fired it, which actions ran, what each one was configured with after the tokens were filled in, and why anything was skipped.
That last part matters. Zapify records the resolved configuration before each action executes, so a failed run tells you what it was actually about to do rather than what the automation says in the abstract.
Conclusion
You now have a live automation built from one trigger and one action, and you can confirm each run in the logs. From here, narrow when it runs with filters and conditions, make an action wait with delays, or start from a ready-made automation in templates.
FAQs
What is an automation in Zapify?
An automation is Zapify's name for a single "when this happens, do this" rule. It is one or more triggers — the events to watch for — plus an ordered list of actions to run in response. Zapify does not use the words "recipe", "zap", or "workflow". Each trigger and action has its own Live, Off, or Draft state so you can build and test in stages.
Is Zapify safe to activate on a live site?
Yes. Activating Zapify changes nothing on its own. No automation runs until you build one and switch its status to Live, so installing on a busy production site does not fire any actions. Automations start as drafts, and Zapify will not let one go live if it is incomplete.
How many triggers and actions does free Zapify include?
The free build of Zapify ships 23 triggers and 18 actions across WordPress, WooCommerce, Gravity Forms, Contact Form 7, WPForms, Fluent Forms, Webhooks, and Utilities. Premium integrations such as Slack, AI, and the LMS platforms appear in the builder greyed out so you can see what they offer before upgrading.
Can one automation have more than one trigger?
Yes, and it is free. Add several triggers to one automation and choose whether all of them must match or any of them will do. This lets a single automation respond to more than one event, or wait for a combination of events, without building duplicates.
Why did my automation not go live?
Zapify blocks a Live status when the automation could never work: no trigger, no action, a required field left empty, or a condition that was added but never filled in. When you try to go live, Zapify names the specific problem so you can fix it. See troubleshooting if a live automation still does nothing.