Outcome
A CI job can trigger a configured workflow through the REST webhook endpoint after code or JSON artifacts are deployed.
Trigger Workflows from CI via Webhook
Let GitHub Actions or another deployment system trigger a WPChangeSync workflow.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
High. External trigger path. Store tokens securely, use POST-only triggers, and rate-limit retries.
Before you start
- The workflow has a webhook token.
- The token is stored as a CI secret.
- The workflow itself still uses dry runs, backups, approvals, or narrow scope for production.
Steps
- Create the workflow
Build and test the workflow manually first. - Generate/store the webhook token
Copy the webhook URL/token into your CI secret store. - Trigger after artifact deploy
Call the webhook only after JSON/code files are present on the server. - Check response and Activity
Fail the CI job if the webhook call fails, then inspect WPChangeSync Activity for execution details. - Rate-limit retries
Avoid loops that repeatedly trigger the same workflow.
- name: Trigger WPChangeSyncn run: curl -X POST "${{ secrets.WPCHANGESYNC_WEBHOOK }}"Webhook does not replace permissions
The endpoint uses token authentication and rate limiting, but the workflow still needs safe scope and review for production writes.Verify and recover
After completing this guide, verify the result in Activity and on the target site. Keep the pre-change export or backup until the release has been accepted. If anything looks wrong, stop further syncs, restore the affected item or integration from backup, and re-run with a narrower scope or safer conflict strategy.