Getting Support For Zapify

Before you write in

Two things answer most questions faster than we can:

The run log. Zapify → Logs records why each run did what it did, including the configuration each action was called with after tokens were resolved. If an automation did the wrong thing, this usually shows why.

Troubleshooting. The common causes of "it did not run" are listed there in the order they usually turn out to be the answer.

Contacting us

Zapify → Support in your admin has a form that includes your system status automatically — WordPress and PHP versions, active plugins, queue health. That context saves a round trip.

Zapify Pro customers get priority: their requests are handled ahead of free ones wherever possible.

What helps us help you

• What you expected, and what happened instead
• The automation's ID, from the list
• The run ID from the log, if it produced one
• Whether it ever worked, and what changed if so

A screenshot of the builder showing the automation is worth a lot — it tells us the trigger, the actions, and every switch and filter at a glance.

Reporting a security issue

Please do not open a public issue. Write to us directly and we will respond before disclosing anything.