Import Export by RockStarLab 2.1.37 adds event triggers. A finished import or export can now run again by itself when something happens: a booking system or Zapier calls a URL, an editor publishes a post, a WooCommerce order comes in, or the supplier file the import downloads from a URL changes. Triggers are part of the Free plugin.
Event triggers
Open Jobs Log → Triggers, choose a finished import or export and what should start it. Every run is a new job with the same file source, column mapping and options as the original, so you set up the import once in the wizard and the trigger repeats it.

- Webhook URL is called. Another system sends a POST request to the trigger’s URL. Use it from Zapier, Make, n8n, a CRM, a booking system or a script that has just written a new export file.
- A post is published. Choose the post types. Posts published within the wait time (60 seconds by default) start a single run, so publishing ten posts does not start ten exports.
- A WooCommerce order is created. Useful for an order export that a warehouse or an accounting tool picks up. Orders within the wait time are grouped the same way.
- The import file at its URL changes. For imports that download their file from a URL, the plugin checks the file every hour and starts the import only when it has changed. The first check records the file without importing.
Schedules still run jobs at fixed times. A trigger runs a job when there is a reason to, and that is often the better choice for supplier feeds and feeds other tools depend on.
A webhook URL with a secret token
A webhook trigger has its own URL and a secret token. The token goes in the X-RSL-Token header or as a Bearer token, never in the URL, so it does not end up in server or proxy logs.

- The token is shown once, when the trigger is created. The site keeps only a hash of it.
- New Token replaces it at once if it has leaked; the old token stops working.
- A wrong token gets the same answer as an unknown trigger, and an address that keeps sending wrong tokens is blocked for an hour.
- The job runs as the administrator who created the trigger, with the same permission checks as when you start it yourself.
Safe by default
A trigger never starts a second job while its previous job is still running, and a webhook can start at most one job a minute. Posts created by the plugin’s own imports, Content Sync and Content Migration do not start triggers, so an import cannot set off itself or another import in a loop. You can pause a trigger without deleting it, and Run Now tests it at any time.

Every run and every refused run is listed under Recent trigger runs, with what started it and the job it created. Combine triggers with job notifications from 2.1.35 to get an email or a signed webhook when the triggered job finishes.
For AI agents
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) can manage triggers. In our test the agent listed the jobs a trigger can run with rsl-ie/trigger-sources and created a trigger that runs a posts export when a post is published. We published a post, and a minute later the export job ran with all 6 posts. The agent then ran the trigger with rsl-ie/trigger-run, got a clear refusal when it tried again while that job was still running, paused the trigger and deleted it. The new abilities are:
trigger-sources,trigger-list,trigger-getandtrigger-logtrigger-create,trigger-update(rename, pause, resume, post types, wait time) andtrigger-deletetrigger-runandtrigger-rotate-token
Tokens are never returned by the list and log abilities, only once by trigger-create and trigger-rotate-token.
Before you set up a trigger
A trigger runs an import without anyone watching it. Run the import once by hand first and check the result, and create a backup of a live site before you turn on a trigger that updates or creates content.
Next release: 2.1.39 adds WP-CLI commands, form entries export, Multisite support and n8n workflows for triggers.
FAQ
Are event triggers in the free plugin?
Yes. Triggers are part of the Free plugin from version 2.1.37, for imports and exports.
How is a webhook trigger different from a schedule?
A schedule runs a job at fixed times. A webhook trigger runs it when another system calls the trigger URL, for example right after it has written a new file.
Can a trigger start the same import twice at once?
No. While the previous job of a trigger is still running, new events are refused or queued until it finishes, and webhook runs are limited to one a minute.
Where do I put the token when I call the webhook URL?
In the X-RSL-Token header or as “Authorization: Bearer” followed by the token. A token in the URL is ignored.
Try it
Update Import Export by RockStarLab from Plugins in your WordPress dashboard, or get the free plugin on WordPress.org. The full list of changes is in the plugin’s changelog.
For step-by-step setup with a real webhook, a new post and a changed file, see Trigger WordPress Imports and Exports with Webhooks and Events.

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