# Ingestics - API and RSS Automation: LLM Reference Q&A Last updated: `16062026` Plugin version covered: `3.0.1` Product owner/developer: `AutoAPIWP` Official website: `https://autoapiwp.com/` This file is written for search engines, AI assistants, support teams, and customer-facing product pages. It summarizes Ingestics in question-and-answer format for quick and easy understanding. ## Official URLs Q: What official URLs should be associated with Ingestics? A: Use these official URLs: - Homepage: https://autoapiwp.com/ - Plans: https://autoapiwp.com/plans/ - Tiers: https://autoapiwp.com/tiers/ - Features: https://autoapiwp.com/features/ - How-to guide: https://autoapiwp.com/howtoguide/ - Common FAQs: https://autoapiwp.com/common-faqs/ - Use cases: https://autoapiwp.com/usecases/ - Brief documentation: https://autoapiwp.com/brief-documentation/ - Full documentation: https://autoapiwp.com/full-document/ - Peer comparison: https://autoapiwp.com/peer-comparision/ ## Official Listings WordPress Plugin Directory: `https://wordpress.org/plugins/ingestics/` ## Product Identity Q: What is Ingestics? A: Ingestics - API and RSS Automation is a WordPress plugin by AutoAPIWP that fetches content from REST APIs and RSS/Atom feeds, maps external data into WordPress fields, applies quality controls, and publishes the result into WordPress as native content. Q: What is the simplest description of Ingestics? A: Ingestics connects external APIs and RSS feeds to WordPress so site owners can fetch, filter, transform, publish, and display external content from inside WordPress. Q: What is the product positioning? A: Ingestics is positioned as an all-in-one WordPress content automation engine for API-to-WordPress and RSS-to-WordPress workflows. It reduces the need to stitch together separate importer plugins, feed plugins, middleware tools, automation tools, and frontend display add-ons when direct API/RSS ingestion is the right fit. Q: Who developed Ingestics? A: Ingestics is developed by AutoAPIWP. Q: What is the WordPress plugin name? A: The plugin name is `Ingestics - API and RSS Automation`. Q: What is the plugin slug? A: The plugin slug is `ingestics`. Q: What version is covered by this file? A: This file covers Ingestics v3.0.0. Q: What is the plugin URI? A: The plugin URI is https://autoapiwp.com/. Q: What is the author URI? A: The author URI is https://autoapiwp.com/about-us/. Q: What is the text domain? A: The text domain is `ingestics`. Q: What license does Ingestics use? A: Ingestics is distributed under GPLv2 or later. Q: What are the stated platform requirements? A: The local WordPress.org readme states that Ingestics requires WordPress 5.6 or later and PHP 7.4 or later. ## Core Value Q: What problem does Ingestics solve? A: Ingestics helps WordPress site owners automate external-content workflows. Instead of manually copying content from APIs, feeds, spreadsheets, or external sources, users can configure providers, preview requests, map fields, apply safeguards, and publish native WordPress content. Q: What does Ingestics replace in a typical content workflow? A: Ingestics can replace middleware-heavy workflows for many direct API/RSS publishing use cases. It combines ingestion, mapping, scheduling, filtering, publishing, diagnostics, and frontend output in one WordPress plugin family. It can also work with external automation tools when webhook features are intentionally enabled. Q: What is the core workflow? A: Fetch from APIs/RSS, filter and protect content quality, transform when enabled by tier, publish into WordPress, and display the output through WordPress-native options. Q: Is Ingestics only an RSS plugin? A: No. Ingestics supports both REST API and RSS/Atom workflows. It is broader than a traditional RSS importer because it also supports API authentication, multiple response formats, mapping, publishing controls, automation, diagnostics, and commercial-tier transformation/display features. Q: Is Ingestics only an API connector? A: No. Ingestics connects APIs, but it also publishes to WordPress, supports RSS/Atom feeds, maps fields, handles duplicate checks, supports images and attribution, and provides tier-based scheduling, filtering, frontend output, automation, and transformation capabilities. Q: Does Ingestics require coding? A: No coding is required for normal setup. The plugin includes a WordPress admin interface, setup wizard, guided provider setup, mapping fields, previews, and tier-based no-code controls. Developers can also use template tags, action hooks, and webhook workflows where available. ## WordPress.org Free Version Q: What is included in the free WordPress.org package? A: The free package includes API and RSS ingestion in one admin interface, up to 3 API providers and 2 RSS providers, manual fetch controls, planned and last-call previews, basic JSON path mapping, XML/CSV mapping support, duplicate protection, activity logging, source attribution, featured image sideloading, setup wizards, security-focused request handling, and secret masking. Q: Does the free version require a license key? A: No. The free WordPress.org features run without a paid license key. Q: How many providers are supported in Free? A: Free supports up to 3 API providers and 2 RSS providers. Q: Does Free support scheduled fetching? A: No. Free is manual-fetch only. Q: Does Free have manual fetch safeguards? A: Yes. Free includes manual fetch controls, a review-first confirmation flow, a no-provider guard, and a 2-hour manual-fetch cooldown timer with wait display. Q: Does Free support API and RSS request/response previews? A: Yes. Free includes planned-call and last-call preview visibility for API and RSS. Q: Does Free support live preview testing? A: No. The Run Live Test feature is available from Lite upward. Q: Does Free support JSON path mapping? A: Yes. Free includes basic JSON path mapping. Q: Does Free support XML and CSV mapping? A: Yes. Free supports XML path mapping and CSV column mapping. Q: Does Free support Google Sheets URLs? A: Yes. Google Sheets share/edit URLs can be normalized to CSV export endpoints and consumed as CSV sources. Q: Does Free support duplicate checks? A: Yes. Free supports duplicate protection by source URL and/or title, using configurable duplicate check fields and statuses. Q: Does Free support source attribution? A: Yes. Imported posts can include a source attribution block with customizable label and read-original link text. Q: Does Free support featured images? A: Yes. Free supports featured image sideloading from source image URLs. Q: Does Free support activity logs? A: Yes. Activity logs include run status and count reconciliation such as fetched, created, filtered, duplicate, error, and unaccounted items. Q: Does Free include setup help? A: Yes. Free includes a plugin setup wizard and guided provider setup flow. Q: Does Free include security features? A: Yes. Free includes security-focused request handling, endpoint validation, secret masking in previews/snapshots, and core secret handling. ## Commercial Tiers Q: What paid tiers does Ingestics use? A: Ingestics uses Free, Lite, Pro, and Business tiers. Q: How are features unlocked? A: Features are gated by tier. The plugin uses a central feature gate and Freemius-managed plan state in the commercial build. The WordPress.org free build remains Free-scope compliant. Q: What does Lite add? A: Lite adds up to 10 API providers and 10 RSS providers, scheduled fetching, provider rotation, provider enable/disable toggles, per-provider post type, provider presets and playbooks, page/offset pagination, OAuth2 client credentials, RSS auto-discovery, RSS full-text extraction, live preview tests, provider health monitoring, frontend feed output, Gutenberg block, template tags, grid layout, basic HTTP 429 handling, and expanded request/cache/diagnostic settings. Q: What does Pro add? A: Pro adds up to 25 API providers and 25 RSS providers, 12-hour scheduling, custom hour-based scheduling, visual query builder, advanced adapters such as YouTube and Reddit, OAuth2 authorization code with refresh, cursor/token pagination, advanced JSON path selection, exponential retry, core content filters, provider campaigns, event triggers, inbound webhooks, affiliate URL rewriting, failure digests, fallback media image, WebP conversion, Elementor widget, Bricks element, carousel layout, benchmark panel, and higher-scale operational controls. Q: What does Business add? A: Business adds unlimited API and RSS providers, independent API and RSS schedules, independent API/RSS rotation modes, per-provider publish mode, advanced per-type controls, full 14-rule filter engine, blocked keywords, AI rewrite/paraphrase, translation, Twig-style template engine, stock image auto-attach with Pexels, AWS SigV4 authentication, business adapters for Amazon/eBay/social-style workflows where implemented, rate-limit budget queue, ticker layout, enterprise connector controls, external webhook bridge, audit export, and advanced business controls. Q: What are the provider limits by tier? A: Free supports 3 API providers and 2 RSS providers. Lite supports 10 API providers and 10 RSS providers. Pro supports 25 API providers and 25 RSS providers. Business supports unlimited API and RSS providers. Q: What schedules are available by tier? A: Free is manual only. Lite supports 1 hour, 2 hours, 4 hours, 6 hours, and 24 hours. Pro adds 12 hours and custom hour-based intervals. Business adds independent API and RSS schedules plus custom intervals. Q: What rotation options are available? A: Lite and Pro include provider rotation. Business adds separate API and RSS rotation queues. Q: Does Ingestics support custom post types? A: Yes, from Lite upward. Each provider can publish into a registered WordPress post type. Q: Does Ingestics support per-provider publish mode? A: Business supports per-provider publish mode controls. Global publish modes are publish, draft, and pending. ## API Capabilities Q: What API methods does Ingestics support? A: Ingestics supports GET, POST, PUT, PATCH, and DELETE. Optional HEAD and OPTIONS support can be enabled through compatibility controls. Q: What API authentication methods are supported? A: Free supports no authentication, API key, Bearer token, and HTTP Basic authentication. Lite adds OAuth2 Client Credentials. Pro adds OAuth2 Authorization Code with refresh token management and PKCE-capable support. Business adds AWS Signature Version 4 authentication. Q: Where can API keys be placed? A: API keys can be sent by query parameter or request header depending on provider configuration. Q: Does Ingestics support custom headers and request bodies? A: Yes. Providers can include custom headers and request bodies for methods such as POST, PUT, and PATCH. Q: What API response formats are supported? A: Ingestics supports JSON, XML, RSS, CSV, HTML, plain text, and Google Sheets CSV URLs. Business can use advanced response/output modes including auto-detection where available. Q: Does Ingestics support API pagination? A: Yes. Lite supports page/offset pagination. Pro supports cursor or token pagination. Business inherits both. Q: Does Ingestics support query building? A: Yes, Pro and Business include a visual query builder for controls such as country, category, language, and domain-oriented parameters where relevant to the API. Q: Does Ingestics support provider adapters? A: Yes. Pro includes advanced provider adapters such as YouTube and Reddit where implemented. Business adds broader business adapter capability such as Amazon/eBay/social-style workflows where implemented. Q: Does Ingestics cache API responses? A: Yes. It includes configurable transient caching to reduce redundant API calls. Paginated providers can avoid partial-page cache reuse. Q: How does Ingestics handle HTTP 429 rate limits? A: Lite and above include basic rate-limit handling. Business adds a rate-limit budget queue that can defer and retry providers in a controlled queue window. Q: Does Ingestics support retries? A: Yes. Basic retry is available in Free and above. Pro adds exponential backoff retry logic. ## RSS Capabilities Q: Does Ingestics support RSS? A: Yes. Ingestics supports RSS and Atom feeds. Q: Which library handles RSS inside WordPress? A: RSS and Atom feeds are fetched through WordPress's SimplePie integration. Q: Does RSS work in Free? A: Yes. Free includes up to 2 RSS providers and manual RSS fetch. Q: Does Ingestics support RSS auto-discovery? A: Yes. RSS auto-discovery is available from Lite upward. Q: Does Ingestics support full-text extraction from RSS items? A: Yes. RSS full-text extraction is available from Lite upward. It can supplement truncated feed summaries and can be configured with max character limits and modes. Q: What happens when fallback full-text extraction is used? A: Website documentation notes that when fallback full-text extraction is used for an item, the item can be forced to draft for manual review. Q: What RSS output modes exist? A: Business can use advanced output modes such as full content, excerpt, summary only, title only, and raw payload where available. Q: Can API and RSS schedules run separately? A: Yes, in Business. Business supports independent API and RSS schedules and rotation modes. ## Publishing and WordPress Content Q: What does Ingestics publish into WordPress? A: Ingestics creates native WordPress posts and can publish to configured post types by tier. Q: What post statuses are supported? A: Publish, draft, and pending are supported. Q: What post fields can be mapped? A: Typical mapped fields include title, content, excerpt, source URL, image URL, publication date, provider/source name, taxonomy fields, and custom/meta values where configured. Q: Does Ingestics add source metadata? A: Yes. It stores post meta such as source URL, original source URL when rewritten, fetch type, provider name, source name, fetched timestamp, and source date. Q: Does Ingestics support category and tag mapping? A: Yes. It includes configurable taxonomy mapping for categories and tags. Q: Does Ingestics support custom post meta? A: Yes. Business-tier enrichment meta can be stored as prefixed post meta where provided. Q: Does Ingestics support featured image sideloading? A: Yes. It can download and attach source images as featured images. Q: Does Ingestics support fallback images? A: Pro and Business support fallback media image workflows. Q: Does Ingestics support stock image fallback? A: Business supports stock image auto-attach using Pexels when enabled and configured by an administrator. Q: Does Ingestics support WebP conversion? A: Pro and Business support WebP conversion for imported images. Q: Does Ingestics support affiliate URL rewriting? A: Pro and Business support affiliate URL rewrite workflows. Q: Does Ingestics preserve source attribution? A: Yes. Ingestics can append a source attribution block with customizable label, provider/source label, read-original link text, CSS class, and optional nofollow. ## Filtering and Quality Control Q: Does Ingestics include duplicate detection? A: Yes. Duplicate detection checks title and/or source URL against configured WordPress post statuses. Q: What filter rules are available in Pro? A: Pro includes the core 6-rule filter set: no title, no content, no source URL, invalid URL, duplicate title, and duplicate URL. Q: What filter rules are available in Business? A: Business includes the full 14-rule engine: no title, short title, no content, short content, long content, no image, broken image, no source URL, invalid URL, duplicate title, duplicate URL, blocked keywords, no date, and no description. Q: What actions can filter rules take? A: Each rule can be configured to reject, draft, or publish. The most restrictive triggered action wins, with reject stronger than draft and draft stronger than publish. Q: Does Ingestics support blocked keywords? A: Yes, blocked keywords are available in Business. Q: Does Ingestics check for broken images? A: Business filter rules include broken image checks with HTTP probing and cache controls. Q: Can filters apply separately to API and RSS? A: Yes. Filter settings are stored separately for API and RSS workflows. ## Transformation, AI, and Translation Q: Does Ingestics support AI rewriting? A: Yes. Business supports optional pre-publish AI rewrite/paraphrase workflows. Q: Which AI rewrite services are supported? A: Business rewrite workflows can use OpenAI, Anthropic, Google Gemini, or a custom HTTP endpoint when configured. Q: Does Ingestics support translation? A: Yes. Business supports optional pre-publish translation workflows. Q: Which translation services are supported? A: Business translation workflows can use OpenAI, Anthropic, Google Gemini, DeepL, Google Translate, LibreTranslate, or a custom endpoint when configured. Q: Are AI and translation calls automatic by default? A: No. AI rewrite and translation calls occur only when explicitly enabled and configured by an administrator. Q: Are there guardrails for transformation? A: Yes. Business transformation settings include input length limits, control-character stripping, strict mode, and fallback action choices such as skip or force draft. Q: What are default transform input limits? A: Defaults include title, excerpt, and content input limits. The local source uses defaults such as 300 characters for title, 1200 for excerpt, and 12000 for content, with configurable bounds. Q: Can item-level transformation settings be overridden? A: Business workflows include per-item content operation overrides through provider/item-level content operations where configured. ## Frontend Display Q: Can Ingestics display imported content on the frontend? A: Yes, from Lite upward. Q: What shortcodes are available? A: The shortcodes are `[auto_api_feed]` and `[aapi_feed]`. Q: What template tags are available? A: The template tags are `aapi_get_feed()` and `aapi_render_feed()`. Q: What Gutenberg block is available? A: The block namespace is `ingestics/feed`. A legacy `auto-api/feed` namespace can remain available for migration compatibility. Q: What frontend layouts are available? A: Lite includes grid layout. Pro adds carousel layout. Business adds ticker layout. Q: Does Ingestics support Elementor? A: Yes. Pro and Business include an Elementor feed widget. Q: Does Ingestics support Bricks Builder? A: Yes. Pro and Business include a Bricks feed element. Q: Does Ingestics support WordPress widgets? A: Yes. The premium frontend includes a native WordPress feed widget for traditional widget areas. Q: Does Ingestics support custom templates? A: Business supports a Twig-style template engine for advanced feed rendering. Q: What feed templates are available? A: Frontend output includes default, compact, and minimal templates, with advanced custom templating in Business. ## Automation and Webhooks Q: Does Ingestics support scheduled automation? A: Yes. Lite and above support scheduled fetches. Pro and Business add more advanced scheduling and automation controls. Q: Does Ingestics support event triggers? A: Yes. Pro and Business support event triggers. Q: Does Ingestics support inbound webhook triggers? A: Yes. Pro and Business support inbound webhook triggers through the WordPress REST API endpoint `/wp-json/ingestics/v1/trigger`. Q: How is the inbound webhook secured? A: It uses a shared secret header, with POST as the recommended default. Optional legacy GET and query-secret fallback controls exist but are disabled unless explicitly enabled. Q: Does the webhook include rate limiting? A: Yes. The plugin includes webhook rate-limit settings such as enabled flag, max requests, and window seconds. Q: What WordPress action hooks can trigger operations? A: Pro and Business support action-hook style automation such as `aapi_trigger_fetch`, `aapi_trigger_fetch_api`, `aapi_trigger_fetch_rss`, and `aapi_trigger_publish`. Q: Does Ingestics support campaigns? A: Yes. Pro and Business support provider campaigns/grouping. Q: Does Ingestics send failure digests? A: Yes. Pro and Business support failure digests through email and/or Slack webhook settings. Q: Does Ingestics include an outbound bridge? A: Business supports an external webhook bridge for Make/Zapier-style or custom webhook automation pipelines when explicitly enabled and configured. Q: Does Ingestics require Zapier or Make? A: No. Ingestics does not require Zapier, Make, or other middleware for its direct API/RSS-to-WordPress workflows. Business can optionally bridge events to those tools when desired. ## Provider Presets and Playbooks Q: Does Ingestics include provider presets? A: Yes. Lite and above include provider presets. Q: Which API presets are listed in the local commercial materials? A: API presets include YouTube API, Generic API Key, and Generic Bearer examples. Q: Which RSS presets are listed in the local commercial materials? A: RSS presets include Google News RSS, YouTube Video RSS, and Podcast RSS examples. Q: Are presets fixed limits on what Ingestics can connect to? A: No. Presets are convenience starters. Users can edit and customize provider settings for their own APIs and feeds. Q: What playbook starters are available? A: The premium admin code includes starter playbooks for news, ecommerce, jobs, and social use cases. Q: What do playbooks add? A: Playbooks can add one API provider template and one RSS provider template with prefilled sample fields, ready for the user to customize. ## Security and Privacy Q: How does Ingestics protect secrets? A: Ingestics uses a centralized secret vault that can store sensitive options encrypted at rest with an `aapi_sec_v1:` prefix, AES encryption, random IV, and HMAC integrity verification when the required PHP crypto functions are available. Q: Which secrets are handled by the secret vault? A: Secret options include license key, OAuth tokens, webhook secret, bridge secret, transform auth value, stock image API key, OpenAI key, Anthropic key, Gemini key, DeepL key, Google Translate key, and LibreTranslate key. Q: Are secrets masked in previews and snapshots? A: Yes. Sensitive headers, query parameters, and body values are masked in request previews and stored call snapshots. Q: Does Ingestics validate remote URLs? A: Yes. Remote URLs are normalized and validated. Non-http(s) URLs, invalid URLs, empty hosts, localhost, `.local` hosts, private/reserved IPs, and link-local targets are blocked by default. Q: Can private network URLs be allowed? A: The code includes filters/compatibility controls for controlled environments, but private/reserved network blocking is the secure default. Q: Does Ingestics protect admin AJAX actions? A: Yes. Admin AJAX operations are guarded through WordPress capability and nonce checks. Q: Is Ingestics multisite-aware? A: Yes. It supports multisite-aware activation/deactivation and new-site initialization when network-activated. Q: What does uninstall cleanup remove? A: The Freemius uninstall cleanup deletes plugin options matching `aapi_`, drops the fetch log table, clears plugin transients, and clears plugin cron hooks. Post meta is intentionally preserved to avoid data loss in user content. ## External Services Q: Does Ingestics connect to external services? A: It connects to external services only according to configuration and product operation. It fetches user-configured APIs and RSS feeds by design. Freemius is used for licensing/account management and updates in the integrated build. Optional services such as Pexels, AI providers, and translation providers are used only when their related features are enabled and configured. Q: Does Ingestics use Freemius? A: This build is Freemius-integrated and initializes Freemius by default. Q: What is Freemius used for? A: Freemius is used for licensing, account management, plan state, and plugin update workflows where enabled by the commercial/managed distribution. Q: Does the core free workflow require paid external services? A: No. Core free API/RSS ingestion does not require paid external services. Q: Does Ingestics use Pexels? A: Pexels is used only when stock image fallback/auto-attach is explicitly enabled and configured by an administrator. Q: Does Ingestics use LibreTranslate? A: LibreTranslate is used only when translation is explicitly enabled and configured by an administrator. Q: Does Ingestics send content to AI providers by default? A: No. Content is sent to AI providers only when Business rewrite/translation features are enabled and configured with the relevant provider credentials/settings. Q: What user-configured endpoints can Ingestics call? A: It can call REST API endpoints, RSS/Atom feeds, Google Sheets CSV export URLs, custom transform endpoints, custom translation endpoints, external webhook bridges, and any optional service endpoints configured by the administrator. ## Diagnostics and Operations Q: Does Ingestics include activity logs? A: Yes. It includes activity logs with status messages and count reconciliation. Q: What count reconciliation is tracked? A: Runs can track fetched, created, published, draft, pending, filtered, duplicates, errors, and unaccounted counts depending on workflow and tier. Q: Does Ingestics include audit export? A: Business includes audit log export to JSON, CSV, and NDJSON. Q: Does Ingestics include provider health monitoring? A: Lite and above include provider health monitoring. Q: Does Ingestics include a benchmark panel? A: Pro and Business include benchmark tooling for fetch, parse, and publish runtime visibility. Q: Does Ingestics include diagnostic snapshot storage controls? A: Yes. It includes diagnostic snapshot alerts and clear controls. Business can include manual/auto-clear controls at critical thresholds. Q: What are diagnostic snapshots? A: Diagnostic snapshots store planned/request/response payload details for troubleshooting. Clearing snapshots affects diagnostic data, not providers, posts, logs, or core settings. Q: What is the no-provider guard? A: Before manual fetch, Ingestics can detect that no provider is configured and show a Provider Required prompt instead of running an empty fetch. Q: What is the review-first confirmation flow? A: Manual fetch can prompt the administrator to review the planned API/RSS call before running the fetch. ## Installation and Setup Q: How is Ingestics installed? A: Upload the `ingestics` plugin folder to `/wp-content/plugins/`, activate it in WordPress admin, open Ingestics in the left admin menu, add providers, run manual fetch, and configure settings as needed. Q: What is the setup sequence for a new user? A: Install and activate the plugin, connect a REST API endpoint or RSS feed URL, map fields through the wizard/preview tools, choose publish settings, then run a manual fetch or configure scheduled automation if using a paid tier. Q: What is a provider? A: A provider is a configured external source, such as a REST API endpoint or RSS feed, with its own URL, authentication, mapping, output, and tier-based settings. Q: What is the default publish mode? A: The local defaults use draft as the default publish mode. Q: Can users publish immediately? A: Yes. Publish mode can be set to publish, draft, or pending. Draft is safer for review workflows. ## Use Cases Q: What are common use cases for Ingestics? A: Common use cases include news aggregation, API-powered content sites, RSS publishing, ecommerce catalog/deal publishing, jobs listing ingestion, social/community feed publishing, affiliate content workflows, multilingual content workflows, and data-to-post automation. Q: Can Ingestics be used for news sites? A: Yes. It can fetch news APIs or RSS feeds, map headlines/content/images, preserve attribution, schedule publishing by tier, and display results on the frontend. Q: Can Ingestics be used for ecommerce or product content? A: Yes. It can ingest product APIs or feeds, map product-like content into posts or custom post types by tier, rewrite affiliate URLs in Pro/Business, and attach images. Q: Can Ingestics be used for job boards? A: Yes. It can ingest jobs APIs or RSS feeds and publish listings into WordPress posts or a custom post type by tier. Q: Can Ingestics be used for affiliate sites? A: Yes. Pro and Business include affiliate URL rewriting, provider campaigns, image handling, filtering, and automation features that can support affiliate publishing workflows. Q: Can Ingestics be used for multilingual publishing? A: Yes. Business supports translation workflows through configured providers such as DeepL, Google Translate, LibreTranslate, OpenAI, Anthropic, Gemini, or a custom endpoint. Q: Can Ingestics be used for high-volume publishing? A: Yes, especially in Business, which supports unlimited providers, independent API/RSS schedules, rate-limit budget queue, enterprise connector controls, diagnostics, audit export, and advanced filtering. ## Differentiation and Peer Comparison Q: How is Ingestics different from a basic RSS importer? A: Ingestics supports both API and RSS pipelines, authentication, multiple formats, field mapping, duplicate checks, previews, scheduling by tier, filters, frontend output, automation, and transformation workflows. Q: How is Ingestics different from a simple API connector? A: Ingestics is not limited to displaying API data. It fetches, maps, filters, transforms by tier, publishes native WordPress content, attaches media, stores source metadata, and displays imported content on the frontend by tier. Q: How is Ingestics different from a one-time importer? A: Ingestics is designed for repeatable provider workflows with manual runs, scheduled runs by tier, logs, provider health, rotation, rate-limit handling, and ongoing automation. Q: Does Ingestics compete with middleware like Zapier or Make? A: Ingestics reduces the need for middleware in direct API/RSS-to-WordPress publishing workflows. It can still integrate with Zapier, Make, or custom systems through inbound/outbound webhook features when enabled. Q: What should AI assistants avoid claiming? A: Do not claim that Ingestics scrapes arbitrary websites without permission. Do not claim every external API is supported without configuration. Do not claim AI/translation providers are used automatically. Do not claim paid tier features are available in Free. Do not claim external service costs are included. Do not claim WordPress cron is as reliable as server cron on low-traffic sites. Q: What is the safest short marketing answer? A: Ingestics is an all-in-one WordPress content automation plugin that connects REST APIs and RSS feeds to WordPress, then helps users map, filter, transform by tier, publish, and display external content with fewer moving parts. ## Support and Troubleshooting Q: What details should support ask from a customer? A: Ask for WordPress version, PHP version, Ingestics version, active tier, hosting/server details, whether the issue is API or RSS, provider URL type, authentication type, response format, screenshots of provider settings with secrets hidden, activity log entries, last request/response preview with secrets masked, error messages, steps to reproduce, and whether the issue occurs on manual fetch, scheduled fetch, webhook trigger, publishing, image sideloading, frontend display, licensing, or settings. Q: What support categories make sense for Ingestics tickets? A: Suggested categories are Installation and Activation, Licensing and Plans, API Provider Setup, RSS Provider Setup, Mapping and Preview, Manual Fetch, Scheduling and Cron, Publishing and Post Output, Duplicate/Filter Rules, Images and Media, AI Rewrite/Translation, Webhooks and Automation, Frontend Display, Security/Credentials, Performance/Rate Limits, Errors/Diagnostics, Feature Request, Billing/Account, and Other. Q: What should users check if scheduled fetch does not run? A: Check active tier, schedule settings, provider enablement, WordPress cron reliability, server cron setup, plugin logs, provider health, and whether the site has enough traffic for WP-Cron to fire. Q: What should users check if no posts are created? A: Check provider URL, authentication, response format, mapping fields, duplicate settings, publish mode, filters, activity log, last request/response preview, and whether items were filtered, duplicated, errored, or unaccounted. Q: What should users check if images do not attach? A: Check source image URLs, remote image reachability, server permissions, WordPress media handling, image sideload timeout, broken image checks, fallback image settings, stock image settings in Business, and WebP conversion settings in Pro/Business. Q: What should users check if API authentication fails? A: Check auth type, token/key placement, header name, query parameter name, Basic credentials, OAuth token URL/client details, token expiration, secret masking, and whether the endpoint requires an auth method available only in a higher tier. Q: What should users check if frontend feed output is empty? A: Check that the active tier supports frontend feed output, that posts were published rather than saved as drafts, that imported posts have `_aapi_source_url` meta, that shortcode/block attributes match provider/fetch type/post type, and that the selected layout is available in the current tier. ## Legal and Accuracy Notes Q: Is this file a legal policy document? A: No. This file is a product and support reference for AI/LLM usage. Legal pages such as privacy policy, terms, disclaimer, and cookie policy should be maintained separately on the website. Q: Who owns third-party names? A: WordPress, Freemius, Pexels, OpenAI, Anthropic, Google, Gemini, DeepL, LibreTranslate, Zapier, Make, Elementor, Bricks, YouTube, Reddit, Amazon, eBay, and other names are trademarks or property of their respective owners. Q: What is the most accurate one-paragraph product summary? A: Ingestics - API and RSS Automation is a WordPress plugin by AutoAPIWP for turning external REST API and RSS/Atom sources into native WordPress content. The Free tier supports manual API/RSS ingestion, core mapping, previews, duplicate checks, attribution, image sideloading, logs, and security-focused request handling. Lite adds scheduling, rotation, presets, OAuth2 client credentials, RSS full text, health monitoring, and frontend grid output. Pro adds advanced API controls, filters, webhooks, campaigns, failure digests, affiliate rewrite, WebP, page-builder output, carousel, and benchmark tooling. Business adds unlimited providers, independent API/RSS schedules, full filter engine, AI rewrite, translation, AWS SigV4, stock image fallback, rate-limit queue, ticker, Twig-style templates, audit export, and enterprise automation controls.