Solutions · Developers

Native WordPress architecture, with hooks where you need them

Ingestics runs entirely inside WordPress — no external middleware service, no separate server to maintain. Action and filter hooks let you extend fetch, transform, and publish behavior without touching core plugin files.

Solution Scenario — Illustrative Example

Here’s how a developer could use Ingestics

A developer wants to surface internal business data on a WordPress site, kept in sync with the source of truth in a CRM or internal system — without building a custom integration from scratch.

ConnectConfigure the CRM or internal API as a provider using Bearer or OAuth2 authentication.
AutomateTrigger fetches via the inbound webhook endpoint when the source system reports a data change, instead of relying only on a fixed schedule.
ControlCustom post types keep CRM-sourced content separate from editorial content.
ExtendHook into fetch and publish events to trigger downstream logic in your own code.

Built for extension

Native WordPress hooks, not a proprietary API

Ingestics exposes WordPress action and filter hooks so you can extend behavior in your own theme or plugin code.

Action hooks on key events

Hook into events like a completed fetch run or a newly published post to run your own follow-up logic.

Filter hooks on request behavior

Filter outbound request arguments, cache key limits, and cooldown timing without editing plugin files.

Custom post type support (Lite+)

Publish imported content into any registered custom post type, not just the default Post type.

Multiple authentication methods

API Key, Bearer, and Basic on every plan; OAuth2 client credentials on Lite; OAuth2 authorization-code with auto-refresh on Pro; AWS SigV4 on Business.

No external middleware

Runs entirely inside your WordPress install

There’s no separate service to deploy, monitor, or keep patched. Fetch, transform, and publish logic all runs inside the WordPress process you already operate.

Read the technical documentation

Full hook reference, field mapping syntax, and configuration detail live in the docs.