Advanced Custom Fields Automations
How to Update an ACF Options Page Field When a Webhook Is Received
A status banner, an opening-hours message or a maintenance notice sits in an ACF options page, but the thing that decides it may live elsewhere — a monitoring tool, a scheduler, another system. Zapify can let that system change the setting with the A webhook is received trigger and the Update a field on an options page action.
What this automation does
The automation is one trigger plus one action:
- Trigger: A webhook is received (
WEBHOOK_RECEIVED, Webhooks) - Action: Update a field on an options page (
ACF_UPDATE_OPTIONS_FIELD, Advanced Custom Fields)
When a request reaches the trigger's endpoint, Zapify writes a value from the request into the options-page field you choose.
Before you start
- Advanced Custom Fields installed and active, with an options page and the field you want to control.
- Something that can send a request to a URL, such as a monitoring tool, a script, or a service like Zapier.
PRO feature
The Update a field on an options page action is part of the Advanced Custom Fields PRO integration and needs an active Zapify PRO licence. The webhook trigger is free.
How to build the automation
Step 1: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Set the site banner from a webhook.
Step 2: Add the "A webhook is received" trigger
- Click Add Trigger.
- Choose Webhooks as the app.
- Select A webhook is received.
- Copy the endpoint URL the builder shows and give it to the sender. Treat it like a password.
- Turn on Require a signature and set a Signing secret so that only requests signed with your secret are accepted.
- Use Listen mode and send one sample request, so the fields of the payload appear as tokens. See Zapify Webhooks for how this works.
Step 3: Add the "Update a field on an options page" action
- Click Add Action.
- Choose Advanced Custom Fields as the app.
- Select Update a field on an options page.
Step 4: Configure the action
| Field | Required | What it does |
|---|---|---|
| Options page | Yes | The options page that holds the field. |
| Field | Yes | The field to write. |
| Value | Yes | Insert the payload token that carries the new text, for example the message field of the request. |
Step 5: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.
Step 6: Test it
Send a request with a message, then open the options page in the admin and check the field. Zapify → Logs shows the delivery and the result.
Conclusion
With the A webhook is received trigger and the Update a field on an options page action, anything that can send a request can change a site-wide setting. To be told when the setting changes, see sending an email when an ACF options field is updated.
FAQs
Is this free in Zapify?
The webhook trigger is free. The ACF action needs an active Zapify PRO licence.
Is it safe to let a webhook change a setting?
Turn on Require a signature so only your sender can do it, and keep the endpoint URL private. Anyone who has an unsigned URL can send data to it.
Will changing the field fire the options-page trigger?
No. Zapify's own writes do not start the ACF triggers.
Does the front end update straight away?
The value is stored immediately. If a caching plugin serves a cached page, clear the cache or wait for it to expire.
Do I need to write any code?
No on the Zapify side. The sender needs to be able to make an HTTP request.