About Ingestics

A problem we faced. A product we built.

Ingestics started as a real project requirement: get data from a REST API into WordPress as published content, on a schedule, without middleware. The plugins we tried each did half the job. Importers handled files but not APIs. RSS plugins handled feeds but nothing else. API connector plugins fetched data but couldn’t publish it. Basic flows sat behind paid modules. No combined pipeline existed.

So we built it. Ingestics™ is a product by AutoAPIWP — the WordPress content ingestion plugin that runs the whole pipeline: fetch from REST APIs and RSS/Atom feeds, map fields, filter, and publish. It launched on WordPress.org and now spans four editions from a genuinely useful Free tier to Business-grade automation. See the full feature set.

What is still different about Ingestics?

  • Dual pipeline. API and RSS in one plugin, one admin interface. This remains the category gap that made us build it.
  • No middleware, no per-task fees. Everything runs on your server. No external automation service, no metered executions, no lock-in.
  • A free tier that does things. 3 API and 2 RSS providers, previews, duplicate checks, publish controls — a working product, not a teaser.

The principles behind every release

  1. Security is not optional. Provider credentials are stored encrypted, secrets are masked in diagnostics, and request handling is security-focused. We treat API keys in a WordPress database as the sensitive material they are.
  2. Show before you publish. Planned and last-call previews, activity logging, and draft-first workflows. Automation you can inspect.
  3. Your data stays yours. Uninstalling preserves your configuration and every post the plugin created. No hostage content.
  4. One install, four tiers. Upgrading is a license key, not a new plugin. Nothing else changes.
  5. AI assists, it doesn’t spam. Where AI features exist (Business), they rewrite, translate, and suggest — using your own provider keys, on content you sourced.
  6. Built to last. Fetches run in crash-safe, bounded background queues, with retention limits and recovery behavior engineered for unattended operation.

Where to next

Read the docs, browse use cases, or see how we compare with alternatives — including where they beat us.

Questions? Contact us.