Frequently Asked Questions
Ingestics FAQ
Answers to common questions about what Ingestics does, how plans and licensing work, and how to get started. Looking for setup steps, feature how-tos, or troubleshooting? Visit the documentation.
What is Ingestics and how is it different from other content import plugins?
Ingestics is a fully automated content ingestion and publishing pipeline for WordPress. Unlike traditional RSS importers or CSV importers, Ingestics connects to supported REST APIs and RSS/Atom feeds, applies authentication, can run AI-powered content transformation when Business features are configured, enforces content quality filters by tier, and supports manual, scheduled, and webhook-driven publishing according to the active tier. It is not a scraper — it works with APIs that provide structured data in standard formats. Key differentiators include native support for major authentication standards including OAuth2 and AWS SigV4, a built-in AI rewrite and translation pipeline on the Business tier, a visual Query Builder for no-code parameter construction, a tiered content filter engine, and front-end display via Gutenberg, Elementor, and Bricks without any additional plugin.
Does Ingestics use Freemius for licensing or payments?
Yes. Plan and license state is managed through Freemius, the licensing platform used by the plugin. License status, upgrades, and account details are available from the License tab inside the plugin, or through your Freemius account.
What happens if the license check fails?
Tier access is resolved from license plan state. If the license state cannot be resolved during a refresh, feature gating may temporarily fall back to Free-tier behavior until license state sync succeeds again. Your configured providers and settings are preserved during this time.
Can I use the plugin on multiple sites?
Multi-site usage depends on the site activations included in your plan. To use Ingestics on additional domains, add the required seats to your plan. To move usage to a new domain, deactivate the old site first, then activate the new site.
Is my API key / secret stored securely?
Yes. All sensitive values are stored using AES encryption with a unique random initialization vector and an HMAC-based integrity check. This covers webhook secrets, bridge secrets, transform auth values, stock image API keys, OAuth/API credentials, and AI/translation service API keys. In previews and stored snapshots, sensitive header values and query parameters are automatically masked. See the security page for full details.
Still have questions?
Browse the documentation for setup guides and feature how-tos, check pricing for plan details, or reach out to support directly.