Ingestics — Documentation

Installation & Activation

Ingestics is a standard WordPress plugin. Install it the same way as any other plugin — no middleware or build step required. Commercial licensing is Freemius-integrated, and optional features such as AI, translation, Pexels, Slack, Zapier/Make bridges, or external APIs use the accounts/keys you configure.

From the WordPress Plugin Directory

1. Go to WordPress Admin → Plugins → Add New.
2. Search for Ingestics.
3. Click Install Now, then Activate.

Manual Upload

1. Download the .zip file from your account or the plugin directory.
2. Go to Plugins → Add New → Upload Plugin.
3. Choose the .zip file and click Install Now, then Activate.

Managing Plan

If you purchase a paid plan, manage activation and plan state through the License/Account screen. Paid features require the matching paid plan and the premium-capable build where applicable.

1. Go to Ingestics → License in your WordPress admin.
2. Follow the activation/account prompts for your paid plan.
3. After license confirms the plan state, tier features become available; existing providers, posts, and settings are preserved during the normal upgrade path.

Setup Wizard

The Setup Wizard walks you through adding your first provider in a few minutes. It is available on all tiers and requires no technical knowledge.

1. Go to Ingestics → Dashboard and click Launch Setup Wizard.
2. Choose your source type: REST API or RSS / Atom Feed.
3. Enter the endpoint URL or feed URL.
4. Map the response fields to WordPress post fields (title, content, image, etc.).
5. Choose the publish settings available to your tier. Scheduling and per-provider custom post types unlock from Lite upward.
6. Click Save & Activate. Ingestics will fetch the first batch immediately.

Adding a Provider

A provider is a single configured connection to one REST API endpoint. You can have multiple providers running simultaneously, each fetching to its own post type, category, and schedule.

1. Go to Ingestics → Providers → Add New.
2. Enter a name for the provider (internal reference only).
3. Enter the Endpoint URL. Supports https:// and http://.
4. Select the HTTP Method (GET is most common; POST is supported).
5. Add any required query parameters or request headers.
6. Choose the Authentication type — see Auth Types.
7. Configure Field Mapping — see Field Mapping.
8. Set the Post Type, Post Status, and Category for published posts.
9. Click Save Provider.

Field Mapping

Field mapping tells Ingestics which JSON or XML fields from the API response correspond to WordPress post fields. For HTML responses, selector mapping is also available for structured extraction.

Call Inspector

The planned/last-call preview shows the request URL, headers, parameters, and last actual call details without exposing secrets. Use Run Live Test on Lite+ to fire a real HTTP request and inspect the raw response and parsed items before saving a provider.

1. On the provider edit screen, click Inspect.
2. Review the response body. If field mapping is configured, matched fields are highlighted.
3. All sensitive header values (API keys, tokens) are automatically masked in the Inspector output.

Pagination

Ingestics supports cursor-based and offset-based pagination for APIs that return results across multiple pages.

Cursor Pagination Pro+

Ingestics reads the cursor or next-page token from the response and automatically follows pages until no more results are returned or the configured item limit is reached.

Exponential Backoff Retry Pro+

On rate-limit or server errors (HTTP 429, 500–503), Ingestics retries the request with exponentially increasing delays before marking the fetch as failed.

Adding a Feed

Ingestics can subscribe to any RSS 2.0 or Atom feed and publish new items as WordPress posts automatically.

1. Go to Ingestics → Providers → Add New and select RSS / Atom as the source type.
2. Enter the feed URL directly, or enter a site URL and click Auto-Discover Feed (Lite+) — Ingestics will find the feed URL automatically.
3. Configure Post Type, Post Status, and Category.
4. Set the Output Mode: full content, excerpt, title-only, or raw (Business).
5. Click Save Provider.

Full-Text Extraction Lite+

Many RSS feeds only include a short summary or truncated excerpt rather than the full article body. Full-Text Extraction fetches the linked article page and extracts the main content, giving you the complete text as the post body.

1. On the feed provider settings, enable Full-Text Extraction.
2. Ingestics will follow each item’s link, fetch the page, and extract the article body using its content-detection algorithm.
3. The extracted content replaces the feed summary as post_content.

Cron Intervals

Ingestics uses WordPress cron to schedule automatic fetches. The following intervals are available by tier:

Custom Frequency Pro+

Set a fetch interval in hours rather than the predefined steps. For example, 0.5 gives a 30-minute fetch, 1.5 gives every 90 minutes.

1. On the scheduling settings, select Custom Interval from the frequency dropdown.
2. Enter the interval in hours (minimum: 0.25 h — i.e. 15 minutes; maximum: 168 h).
3. Save. The cron reschedules immediately.

Auth Types Overview

Ingestics supports the following authentication methods. Credentials are stored AES-encrypted with a unique random IV by default.

OAuth2 Lite+

Client Credentials (Lite+)

1. Select OAuth2 — Client Credentials as the auth type.
2. Enter the Token URL, Client ID, and Client Secret.
3. Optionally enter a Scope if required by the API.
4. Ingestics fetches an access token before each scheduled fetch and caches it until expiry.

Auth Code + Auto-Refresh Pro+

1. Select OAuth2 — Auth Code.
2. Enter the Authorization URL, Token URL, Client ID, Client Secret, and Redirect URI.
3. Click Authorize to complete the OAuth2 flow in a popup. Ingestics stores the refresh token securely.
4. Access tokens are refreshed automatically before expiry — no manual re-authorization needed.

AWS SigV4 Business

AWS Signature Version 4 is required for AWS API Gateway endpoints and other AWS services.

1. Select AWS SigV4 as the auth type.
2. Enter your AWS Access Key ID, Secret Access Key, Region, and Service (e.g. execute-api).
3. Ingestics signs each request with a fresh SigV4 signature at fetch time.

Filter Rules

The filter engine evaluates each fetched item before it is published. Items that match a rule can be rejected (discarded entirely) or saved as draft (held for manual review). There is no separate “flag” status — draft is the holding state.

Pro tier enables a core 6-rule set. Business tier unlocks all 14 rules. Each rule has a configurable action: reject (item is discarded) or draft (item is saved as a draft for manual review).

Rules are evaluated independently. The most restrictive action among all triggered rules wins (reject beats draft).

Blocked Keywords Business

Maintain a global list of blocked keywords. Any item where any field contains a blocked keyword is automatically rejected before publishing — regardless of other filter rules.

1. Go to Ingestics → Settings → Blocked Keywords.
2. Add one keyword or phrase per line.
3. Save. The list applies to all providers immediately.

Duplicate Detection

Ingestics checks each incoming item against existing WordPress posts before publishing. Duplicate detection uses the configured duplicate fields, with title and source URL as the default comparison path. If a duplicate is found, the item is skipped or handled according to the configured filter behavior.

Gutenberg Block & Shortcode Lite+

Ingestics provides a native Gutenberg Feed Block, a shortcode, and template tags to display fetched content anywhere on your site.

Gutenberg Block

Find the Ingestics Feed block in the Gutenberg block inserter. Select your provider, choose a layout (Grid, Carousel, or Ticker), and set the number of items to display.

Shortcode

Use [aapi_feed] (or [auto_api_feed]) in any post, page, or widget to embed a feed. For theme-level rendering, use aapi_get_feed() or aapi_render_feed(). Pass attributes to control the output:

Elementor & Bricks Builder Pro+

Ingestics registers native widgets for Elementor and Bricks Builder. Find the Ingestics Feed widget in the widget panel of each builder, drag it onto your page, and configure it using the builder’s sidebar controls.

• Select provider, layout, item count, and column count.
• Style using the builder’s native style controls — no custom CSS required.

Layouts

Inbound Webhook Trigger Pro+

Trigger a fetch on-demand from any external service — GitHub Actions, CI pipelines, 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 and enable Inbound Webhook Trigger.
2. Set a strong Webhook Shared Secret.
3. Send a POST request to https://yoursite.com/wp-json/ingestics/v1/trigger. Legacy /wp-json/auto-api/v1/trigger compatibility may remain for older integrations.
4. Include the secret in the X-AAPI-Webhook-Secret request header. Ingestics will run the fetch immediately.
5. Webhook defaults are POST + header secret. Legacy GET and query-string secret fallback are compatibility toggles that remain disabled unless explicitly enabled.
6. 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.

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 spreadsheets, etc.

1. Go to Ingestics → Settings → Integrations and enable External Webhook Bridge.
2. Enter your Bridge Webhook URL (e.g. your Make scenario webhook or Zapier catch hook URL).
3. Ingestics sends POST JSON payloads to that URL for both fetch_run_completed and post_published events, but only when this feature is explicitly enabled and configured by an administrator.

AI Content Rewriting Business

Automatically rewrite fetched content using an AI provider before publishing. Rewrites or paraphrases fetched content according to your configured prompt; editorial review and source-rights checks are still recommended.

Supported AI Providers

• OpenAI — enter your API key and any model name (e.g. gpt-4.1-mini)
• Anthropic — enter your API key and any model name (e.g. claude-3-5-haiku-latest)
• Google Gemini — enter your API key and model name

Setup

1. Go to Ingestics → Settings → AI Rewrite.
2. Select your AI provider and enter the API key.
3. Choose the model and set a rewrite prompt (or use the default).
4. Enable rewriting per provider on the provider settings screen.

Translation Business

Translate ingested content into any language before publishing. Configure translation per provider so different providers can publish to different language audiences from a single source feed.

Supported Translation Services

• DeepL
• Google Translate
• LibreTranslate (self-hosted)
• OpenAI, Anthropic, Google Gemini — reuse the AI Rewrite credentials; no separate key needed

Setup

1. Go to Ingestics → Settings → Translation.
2. Select the translation service and enter the API key.
3. On each provider, set the Target Language.

Twig Templates Business

Use the Twig templating engine to fully control how fetched data is assembled into post content. Access any response field, apply filters, loop over arrays, and use conditionals.

1. On the provider settings, select Twig Template as the content mode.
2. Write your Twig template in the editor. All response fields are available as {{ item.fieldname }}.
3. Use the Preview button to render the template against a live API response before saving.

FAQ

Posts are not being published automatically

Check the following:

• The provider is set to Active and a schedule interval is selected (scheduling requires Lite+).
• WordPress cron is running. On low-traffic sites, add a real server cron job: */5 * * * * wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1
• Check Ingestics → Logs for fetch errors.

The Call Inspector shows a 401 or 403 error

Authentication is failing. Verify your API key, token, or OAuth2 credentials. Check that the key has the required permissions on the API side. For Bearer tokens, confirm the token has not expired.

Duplicate posts are appearing

Check Ingestics → Settings → Deduplication. The Duplicate check fields setting (default: title,url) controls which fields are compared against existing posts. Ensure the field values from your API are stable and unique per item. You can also check which post statuses are included in the duplicate check via Duplicate check statuses.

Images are not being attached to posts

Ensure the image URL field is mapped to _thumbnail_id in field mapping. The URL must be publicly accessible — Ingestics downloads the image from your server’s perspective, so local or authenticated URLs will fail.

My paid plan is not syncing

Ensure your server can make outbound HTTPS requests to api.freemius.com. Some hosts block outbound connections — ask your host to whitelist it, or check with wp_remote_get('https://api.freemius.com') via a test snippet.

Debug & Logs

Ingestics maintains a fetch log for every provider run. Access it at Ingestics → Logs. Run summaries include reconciliation metrics (fetched, created/published, filtered, duplicates, errors, and unaccounted counts).