How to Create a ClickUp Task When a Major WordPress Update Is Installed

A major WordPress release deserves a proper check: the front end, the checkout, the contact forms. Zapify creates a ClickUp task for it the moment WordPress is updated, with the old and new version in the title. It uses the free WordPress is updated trigger, set to major releases, and the Create a task action. ClickUp is a Zapify PRO integration.

What this automation does

The automation is one trigger plus one action:

• Trigger: WordPress is updated (WPADMIN_CORE_UPDATED, WP Admin), set to Major release
• Action: Create a task (CLICKUP_CREATE_TASK, ClickUp)

When WordPress moves to a new major version, such as 6.8 to 6.9, Zapify creates a task in the ClickUp list you choose. Minor releases are ignored, because the trigger's Release type field filters them out.

Before you start

• A ClickUp personal API token, from Settings → Apps — see ClickUp's authentication docs.
• The List ID of the list new tasks should land in — the number in the list's URL.

How to build the automation

Step 1: Connect ClickUp

1. Go to Settings → Connections and click Add New.

2. Choose ClickUp, paste in your API token, and name the connection something like Site maintenance ClickUp.

3. Save.

See Connections for how this screen works generally.

Step 2: Create a new automation

1. In the WordPress admin, go to Zapify → Automations.
2. Click Add New to open the builder.
3. Name it clearly, such as Create a test task after a major WordPress update.

Step 3: Add the "WordPress is updated" trigger

1. Click Add Trigger.
2. Choose WP Admin as the app.
3. Select the trigger WordPress is updated.
4. In the Release type field, choose Major release.

Step 4: Add the "Create a task" action

1. Click Add Action.
2. Choose ClickUp as the app.
3. Select Create a task.

Step 5: Configure the action

Field	Required	What it does
Connection	Yes	The ClickUp connection from Step 1.
List ID	Yes	The list the task should be created in.
Task name	Yes	For example Test the site after WordPress {New version}.
Description	No	A checklist, with the old and new version inserted as tokens.
Priority	No	None, Urgent, High, Normal or Low.

For example:

• Task name: Test the site after WordPress {New version}
• Description: WordPress moved from {Old version} to {New version} (automatic: {Automatic update}). Check the home page, checkout, contact forms and login.

Step 6: Set the steps Live and save

1. Set both the trigger and the action to Live. A new automation starts as Draft and will not run until its steps are Live.
2. Click Save.

Tokens you can use

Token	What it holds
Old version	The WordPress version before the update.
New version	The WordPress version after the update.
Release type	major or minor.
Automatic update	yes when WordPress updated itself, no when someone did it by hand.
Actor user ID / Actor username	The logged-in person who did it. Empty (and 0) when nobody was logged in, as with an automatic update.

How to test it

Core updates cannot be triggered on demand, so test on a staging copy of the site: update WordPress from Dashboard → Updates when a new major version is offered. The task should appear in your list within a minute, or open Zapify → Logs to see what ClickUp answered.

Conclusion

With the free WordPress is updated trigger and the Create a task action, every major release starts with a task instead of an assumption. For a plain alert, see emailing when WordPress is updated.

FAQs

Is this free in Zapify?

The trigger is free. The ClickUp action needs an active Zapify PRO licence and a Connection.

Why was no task created for a minor update?

The trigger is set to Major release, which ignores changes such as 6.8.1 to 6.8.2. Change Release type to Any release if you want a task for those too.

How does Zapify decide what is major?

A release is major when the first two numbers change, such as 6.8 to 6.9. Anything else counts as minor.

Does it run for automatic updates?

Yes. The automation runs whoever starts the update, and Automatic update tells you which it was.

Do I need to write any code?

No. Everything is configured in the Zapify visual builder.