Skip to content

Webhook Automations

How to Send a Webhook When a New User Registers in WordPress

Plenty of tools accept a webhook — Zapier, Make, a CRM, a billing system, a script of your own. Zapify can send each new user to one the moment they register, using the A user registers trigger and the Send a webhook action. Both are free.

What this automation does

The automation is one trigger plus one action:

  • Trigger: A user registers (WP_USER_REGISTERS, WordPress)
  • Action: Send a webhook (WEBHOOK_SEND, Webhooks)

Whenever a new account is created, Zapify sends an HTTP request to the URL you give it, with the user's details in the body.

Before you start

  • The destination URL, and its expected body format and authentication, from the receiving service.
  • Both the trigger and the action are free.

Internal addresses are blocked

Zapify refuses to call loopback, link-local and private network addresses, and checks again after redirects. Use a public URL. See Webhooks for details.

How to build the automation

Step 1: 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 Send new users to my CRM.

Create a new automation

Step 2: Add the "A user registers" trigger

  1. Click Add Trigger.

Add a trigger

  1. Choose WordPress as the app.

Select WordPress as the trigger

  1. Select A user registers.

Select A user registers

Step 3: Add the "Send a webhook" action

  1. Click Add Action.

Add an action

  1. Choose Webhooks as the app.

Select Webhooks as the action

  1. Select Send a webhook.

Select Send a webhook

Step 4: Configure the request

Field Required What it does
URL Yes The endpoint to call.
Method Yes POST is the usual choice.
Headers No Extra headers. Values may contain tokens.
Body Yes JSON fields is the safe choice. Zapify builds the JSON, so a value containing a quote cannot break it.
Fields Depends The key and value pairs of the body.
Authentication No None, Bearer token, or Username and password; or pick a saved auth profile.

For example, add these fields:

  • email set to {{trigger:USER_EMAIL}}
  • first_name set to {{trigger:USER_FIRST_NAME}}
  • last_name set to {{trigger:USER_LAST_NAME}}
  • user_id set to {{trigger:USER_ID}}

A key such as customer.email nests the value inside a customer object.

Configure the Send a webhook action

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.

  1. Set the trigger and every action to Live.
  2. Click Save.

Set the automation live

Step 6: Test it

Register a test account. Check that the receiving service got the request, or open Zapify → Logs to see the response it returned.

Tokens you can use

Token What it holds
User ID / Username / User email The new account.
Display name / First name / Last name / User role Name and role.
Registration date / User website When they registered, and the website they entered.

Conclusion

With the A user registers trigger and the Send a webhook action, any service that accepts a request can hear about a new user. For the opposite direction, see sending an email when a webhook is received.

FAQs

Is this free in Zapify?

Yes. The trigger and the Send a webhook action are both free.

Should I send the password?

No. Zapify does not expose it, and a webhook should not carry credentials.

What if the receiving service is down?

The run shows the failure in Zapify → Logs. Automatic retry policies are a Zapify PRO feature.

Can I send it to Zapier or Make?

Yes. Create a catch-hook step in either, paste its URL into URL, and use JSON fields.

Do I need to write any code?

No. The destination decides the format; the rest is configured visually.

Was this page helpful?