Documentation

Webhooks & Automation Triggers

How to trigger fetches from external services, send outbound event payloads, and configure failure digest notifications.

Inbound Webhook Trigger Pro+

Trigger a fetch on-demand from any external service — GitHub Actions, CI pipelines, Zapier, Make, IFTTT, or any tool that can send an HTTP request. This is a single global endpoint for the whole plugin, not per-provider.

  1. Go to Ingestics → Settings → Automation (or Settings → Advanced) and enable Inbound Webhook Trigger.
  2. Copy the Webhook Trigger URL: https://yoursite.com/wp-json/ingestics/v1/trigger. Legacy /wp-json/auto-api/v1/trigger compatibility may remain for older integrations.
  3. Generate or set a strong Webhook Secret (stored AES-encrypted). Share this secret with the external service that will call your endpoint.
  4. Configure the rate limit: maximum requests per IP per minute. Keep legacy GET method and query-string secret fallback disabled unless an integration absolutely requires them — webhook defaults are POST + header secret.
  5. In your external service, set up a POST request to the webhook URL with the header X-AAPI-Webhook-Secret: your_secret.
  6. Send a JSON body with the fetch_type parameter: api, rss, both, or publish. Optionally include campaign (Pro+) to trigger a specific campaign:

{ "fetch_type": "both", "campaign": "my-campaign-name" }

Ingestics validates the secret, checks the rate limit, and executes the requested operation. For WordPress-native automation, you can also trigger runs via aapi_trigger_fetch, aapi_trigger_fetch_api, aapi_trigger_fetch_rss, and aapi_trigger_publish.

Keep your shared secret private — anyone who knows it can trigger a fetch. Rate limiting is recommended for public-facing sites.

External Webhook Bridge Business

Send outbound Ingestics event payloads to external automation platforms — Make (Integromat), Zapier, or any webhook endpoint — for both fetch-run completion and post-publish activity. Use it to trigger downstream workflows: store results, send Slack messages, update a CRM record or spreadsheet, etc.

  1. Go to Ingestics → Settings → Integrations (or Settings → Advanced → Connector Bridge) and enable External Webhook Bridge.
  2. Enter your Bridge Webhook URL (e.g. your Make scenario webhook or Zapier catch hook URL).
  3. Enter a Bridge Secret — Ingestics uses it to generate an HMAC signature header (X-AAPI-Signature) so your receiving endpoint can verify the source. Stored AES-encrypted.
  4. Ingestics sends POST JSON payloads to that URL for both fetch_run_completed and post_published events, including event metadata such as post ID/URL (for publish events), provider name, fetch type, campaign, and source URL where available — but only when this feature is explicitly enabled and configured by an administrator.
  5. In Zapier or Make, create a “Catch Hook” trigger pointed at the bridge URL, then build your automation from there.

Failure Digests Pro+

Email and Slack notifications on fetch failures — configure them under Settings → Integrations → Failure Digests (or Settings → General → Failure Digests).

  1. Enable Email Digest and enter the recipient email address. Digests include a summary of failed providers, error messages, item skip counts, and retry statuses.
  2. Enable Slack Digest and enter your Slack Incoming Webhook URL.
  3. Set the digest frequency. Digests fire on the cron schedule rather than immediately after each failure — this prevents notification floods during temporary outages.