WordPress Content Automation & Scheduling – Ingestics
WP-Cron Integration
Ingestics uses WordPress’s native WP-Cron system for all scheduling. No external cron daemon or server-side configuration is required. The plugin registers custom cron intervals and hooks its fetch routines into the WP-Cron event loop, so your scheduled tasks run as part of the normal WordPress lifecycle.
Configurable Intervals
Choose from six built-in intervals or define a custom schedule:
- Hourly – fetch every 60 minutes
- Every 2 hours
- Every 6 hours
- Every 12 hours
- Daily – fetch once per day
- Custom – define your own interval in minutes
Each interval is available per provider, so you can fetch high-priority sources more frequently and lower-priority sources less often.
Provider-Level Scheduling
Every provider – whether API or RSS – has its own schedule setting. You can configure Provider A to fetch hourly, Provider B every 6 hours, and Provider C daily, all from the provider configuration screen. Changes take effect on the next cron cycle.
Provider Rotation
When multiple providers feed into the same post type or campaign, Ingestics can rotate between them. Rotation distributes the fetch load across providers, preventing any single source from dominating your content stream.
Provider Toggles
Enable or disable any provider without deleting its configuration. Disabled providers are skipped during scheduled runs but retain all settings, credentials, and mapping rules. This is useful for seasonal sources, temporary maintenance, or testing.
Separate API and RSS Schedules (Business Tier)
On the Business tier, API providers and RSS providers can run on completely separate cron schedules. This means your API fetches can run on a different cadence than your RSS fetches, giving you fine-grained control over how each source type is processed and published.
Configuration
| Setting | Description | Default |
|---|---|---|
| Schedule interval | How often the provider fetches new content | Hourly |
| Custom interval | Custom fetch interval in minutes (when Custom is selected) | 60 |
| Provider toggle | Enable or disable the provider without deleting configuration | Enabled |
| Provider rotation | Distribute fetch load across multiple providers | Disabled |
| Separate API/RSS schedules | Run API and RSS providers on independent cron cycles | Business only |
Tier Availability
| Tier | Scheduling | Features |
|---|---|---|
| Free | Manual fetch only | No scheduling |
| Lite | Scheduled | Hourly to daily intervals, provider-level scheduling |
| Pro | Scheduled | Custom intervals, provider rotation, provider toggles |
| Business | Separate schedules | Independent API and RSS cron schedules |
Frequently Asked Questions
Do I need to set up a server-side cron job?
No. Ingestics uses WordPress’s built-in WP-Cron system. As long as your site receives regular traffic or you have a cron trigger configured, scheduled fetches will run automatically. For low-traffic sites, you can set up a system cron to hit wp-cron.php for more reliable timing.
Can different providers have different schedules?
Yes. Each provider has its own schedule setting. You can configure one provider to fetch hourly, another every 6 hours, and a third daily – all independently.
What is the difference between disabling and deleting a provider?
Disabling a provider pauses its scheduled fetches but keeps all configuration, credentials, and mapping rules intact. Deleting a provider removes it entirely. Use the toggle for temporary pauses or maintenance windows.
Start automating.
Download Ingestics free. Start fetching APIs and RSS feeds in minutes.