Many sites get their content from a file that someone else keeps up to date: a booking system’s event list, a partner’s price list, a Google Sheet the team edits. Import Export by RockStarLab can import that file straight from its link and then do it again every hour, day or week, downloading the current version each time. Rows that already exist are updated, new rows are added, and nothing is duplicated. The example is a coffee roastery whose booking tool publishes its tasting events as a CSV file.
Free: import from a URL, schedules, updating existing posts and the AI agent abilities. Products, orders and other WooCommerce data need PRO; see automatic supplier feed import for WooCommerce.
Short Answer
- Go to Import Export → Import, choose the content type and, in step 2, paste the file’s link under Or import a file from a URL. Click Fetch File.
- Map the columns and, in step 5, choose a field that identifies each row, such as Slug, with If Match Found: Update.
- Run the import once and check the result.
- Go to Jobs Log → Schedules, choose that job as the Source Job, set Recurring and Daily (or hourly, twice daily, weekly) and click Add schedule.
What the link must be
The link has to return the file itself, not a web page that shows it: CSV, XML, JSON, XLSX, ODS, or a ZIP with one of them. The site must be able to reach it; addresses on a private network are refused. Some common sources:
- Google Sheets: in the sheet, choose File → Share → Publish to web, pick the tab and Comma-separated values (.csv), and copy the link (see Google’s help on publishing). We checked that a public Google Sheet link is downloaded as a CSV file with all its rows.
- A booking, shop or inventory system that offers a CSV or XML export link.
- A file on your own server or storage that another tool updates.
Step 1: Import the file from its link
Our booking tool publishes the upcoming tastings with a slug, a title, a description and a status for each event:
post_name,post_title,post_content,post_status
tasting-ethiopia-guji,"Ethiopia Guji Tasting, November 14","Saturday, November 14, 11:00. Floral, peach and black tea. 8 seats.",publish
tasting-colombia-huila,"Colombia Huila Tasting, November 21","Saturday, November 21, 11:00. Caramel and red apple. 8 seats.",publish
tasting-kenya-nyeri,"Kenya Nyeri Tasting, November 28","Saturday, November 28, 11:00. Blackcurrant and grapefruit. 8 seats.",publish
In Import Export → Import, choose Posts, then paste the link in step 2:

Fetch File downloads it and shows where it came from:

In step 4, Auto Map matched all four columns, because they are named after WordPress fields. With other column names, map them by hand or apply a saved mapping template.
Step 2: Update rows that already exist
A repeated import must recognise the events it has already created. In step 5, set Check for Existing Items by Field to a value that stays the same for each row. We used Slug; a title works too if it never changes.

The first run created the three events:

Step 3: Schedule it
Open Jobs Log → Schedules, name the schedule and choose the import you just ran as the Source Job. Each run makes a new job with the same settings and downloads the file again from the same link.

The schedule runs with WP-Cron, which starts on visits to your site. On a site with few visitors, a run can start later than planned; a real cron job on your host that calls wp-cron.php every few minutes makes the time exact.
What happened at the next run
Before the first scheduled run, the booking tool’s file changed: the Colombia tasting sold out, the Kenya tasting moved to 12:00 and a Brazil tasting was added. The schedule ran at 16:10 and made job #70:

The job read 4 rows: 3 matched existing events by slug and were updated, and 1 was created. Colombia now says “sold out” in the title, Kenya shows the new time, and Brazil Cerrado is a new post. The Ethiopia row had not changed, so its post stayed as it was. The site had four tasting posts, with no duplicates.
When the file can’t be downloaded
Links sometimes fail: the source is being updated, the server is down or the file was moved. To see what happens, we removed the file before a run. The run didn’t start, and the schedule shows why:

The schedule stays active and tries again at its next run, so one failed download doesn’t stop a daily import. Nothing on the site changes when the file can’t be read. If the reason doesn’t go away, fix the link or edit the schedule. A one-time schedule stops after a failed run. To be told about failed rows in jobs that did run, turn on email or webhook alerts.
Removing rows
A scheduled import adds and updates; it doesn’t delete posts whose rows disappear from the file. To take an event down, keep its row and change its status, for example to draft or private.
With an AI agent
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) can set up the same import:
Import the tastings from https://www.example-roastery.com/wp-content/uploads/feeds/tastings.csv
as posts, update existing ones by slug, and repeat it every day at 7:00.
In our run, the agent downloaded the file with rsl-ie/upload-from-url, which returned 4 rows and the columns post_name, post_title, post_content and post_status. It started the import with rsl-ie/import-start, with unique_field set to post_name and if_exists set to update; the job processed 4 rows with no failures. It then made a daily schedule from that job with rsl-ie/schedule-create. We ran the schedule early to test it: its job downloaded the file again from the link and updated the same 4 posts without creating new ones. rsl-ie/schedule-get also returns error_code and error_message when a run could not start, so the agent can tell you why.
Before you schedule it
A scheduled import changes content without anyone watching, so back up the site first and run the import by hand once. Check that the identifying field really matches the existing posts: with the wrong field, every run would create new posts instead of updating them.
FAQ
Can I import a Google Sheet automatically?
Yes. Publish the tab as CSV with File → Share → Publish to web, paste that link in the import and schedule it. Your edits in the sheet reach the site at the next run.
Does a scheduled import create duplicates?
No, if step 5 checks a field that identifies each row, such as the slug or the title, with If Match Found: Update. Existing posts are updated and only new rows create posts.
How often can it run?
Hourly, twice daily, daily or weekly. The time depends on WP-Cron, so use a real cron job on low-traffic sites.
What if the link doesn’t work at a run?
That run is skipped, Jobs Log → Schedules shows the reason, and the next run tries again.
Does it delete posts that are no longer in the file?
No. Change the row’s status to draft or private instead.
Related Guides
- Save and Reuse Field Mapping Templates for Recurring WordPress Imports
- Get Email and Webhook Alerts When a WordPress Import Finishes (and Fix Failed Rows)
- Automatic Supplier Feed Import for WooCommerce (Hourly or Daily)
- Import a Large CSV (100k Rows) Without Crashing Your Site
Get the free plugin on WordPress.org.

Comments 0
Have a question or a tip to share? Leave it below.