Webhooks

Triggering Aimogen Pro rules and workflows over HTTP, and sending outbound notifications when work completes.

Webhooks work in both directions: external systems can trigger Aimogen Pro, and Aimogen Pro can notify external systems.

Inbound: running a rule#

Settings › General Settings › Enable Rule Running Using Webhooks

Once enabled, each rule shows its webhook URL in its details section.

POST /wp-json/aiomatic/v1/rules

curl -X POST "https://example.com/wp-json/aiomatic/v1/rules" \
  -H "Content-Type: application/json" \
  -d '{"ruleid":3,"ruletype":0,"secret":"YOUR_SITE_SECRET"}'

Authentication#

Two routes are accepted. A valid shared key passes, or the secret parameter matching the generated site secret, compared with hash_equals().

Both the plugin main switch and Enable Rule Running Using Webhooks must be on, or the route returns HTTP 403 with Rule webhook API not enabled. A wrong secret returns HTTP 401.

Inbound: triggering an OmniBlock workflow#

A separate route with its own switch.

Settings › OmniBlocks › Enable OmniBlocks Webhook Functionality

POST /wp-json/omniblock/v1/webhook

curl -X POST "https://example.com/wp-json/omniblock/v1/webhook" \
  -H "Content-Type: application/json" \
  -d '{"omniblockid":"5_a1b2c3d4","apikey":"YOUR_KEY","topic":"Sustainable packaging"}'

The omniblockid must contain exactly one underscore. Other shapes return Incorrect OmniBlock ID submitted in request or Incorrect format for OmniBlock IDs.

Full detail in Triggers and webhooks.

Outbound: notifying an external system#

Two mechanisms.

Per rule. A rule can call a webhook when it finishes, configured in the rule settings.

The send_webhook OmniBlock. More flexible: place it anywhere in a workflow and send exactly the payload you want, built from block outputs.

Body:
{
  "post_id":  "%%created_post_id_4%%",
  "post_url": "%%created_post_url_4%%",
  "title":    "%%ai_text_1%%",
  "created":  "%%current_date_time%%"
}

The call_webhook chatbot extension and agent tool let the AI call a webhook as an action.

Connecting to automation platforms#

The outbound webhook is how Aimogen Pro reaches Zapier, Make, n8n or your own service:

1. Create a webhook trigger in the platform, which gives you a URL.
2. Put that URL in a send_webhook block at the end of your workflow.
3. Build the payload from block outputs.

And inbound, the reverse: the platform posts to omniblock/v1/webhook and your workflow runs.

A complete round trip — a new row in a spreadsheet triggers your automation platform, which posts to the OmniBlock webhook, which generates and publishes an article, which posts back to the platform with the URL — needs no code at either end.

Security#

Outbound webhooks carry your generated content to a third party. Point them only at endpoints you control, and use HTTPS.

Verifying delivery#

System & Logs › Activity Logs records rule executions triggered by webhook, and errors from outbound calls.

For inbound debugging, the simplest test is a curl from a machine outside your server, so you exercise the same path as the real caller.

Common problems#

404 on the route. The feature is off. Both webhook features are off by default.

403 Rule webhook API not enabled. The main switch or the rule webhook setting is off.

401. The secret does not match.

Incorrect format for OmniBlock IDs. More than one underscore in omniblockid.

A firewall blocks it. WAFs frequently block /wp-json/. See Plugin and server conflicts.

The workflow runs but produces nothing. Not a webhook problem. See OmniBlocks troubleshooting.

Related#

• Triggers and webhooks
• REST API
• Scheduling and the posting cron