Getting Started With Zapify
This page takes you from an empty install to a working automation. It should take about five minutes.
Install Zapify
Install and activate it like any other plugin — from Plugins → Add New, or by uploading the zip. Zapify adds a Zapify item to the admin menu with five screens: Automations, Templates, Logs, Settings, and Support.
Nothing runs until you build something and set it live, so activating is safe on a site that is already busy.
Build your first automation
Go to Zapify → Automations and choose Add new.
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.
- In bulk — runs once for every member of a set, such as every subscriber.
You cannot change this later once you have built on it, because the choice decides which triggers are even available.
2. Add a trigger
Under When this happens, choose Add trigger. Pick an integration, then pick the thing to watch for.
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.
3. Add an action
Under Do this, choose Add action and pick what should follow.
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.
4. Set it live
Use the status control at the top. 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.
Where to go next
- Filters and conditions — run it only sometimes
- Delays — make an action wait
- Templates — start from something that already works