Zapier

Zapier watches thousands of apps. When something happens in one of them that should change a member, a form response, a purchase, a cancellation, the Zap can post the update straight to your site. The native webhook needs no connector and no custom headers, so it drops into the standard Webhooks action.

Build the action

1. In your Zap, add an action step and choose Webhooks by Zapier, then POST.
2. Paste the URL:

https://YOURSITE.com/?operation=update_member_data&membauth=YOUR_AUTH_KEY

3. Set Payload Type to Json.
4. In the Data field, paste the payload and wire your trigger fields into it:

{
  "email": "{{email}}",
  "fields": { "newsletter_optin": "yes" },
  "add_tags": [12]
}

Each value comes from the field picker, so the member's email is whatever your trigger app reported. Tag IDs are your local Torii tag IDs, and field keys are your local field slugs.

5. Leave headers alone. The key rides the query string, so Zapier needs nothing else configured.

Test it

Publish the Zap and run it once against a member you control. Open the task in Zap history: the response body shows {"success": true, "data": "Completed."} when the update landed. Then check the member in WordPress; the field value and tag should be there.