Manage scheduled imports

A scheduled import runs a lead sourcing action on a frequency instead of when you click it. The same search, the same scrape, the same feed — re-run on its own, appending only what is new.

This is the difference between a list and a pipeline. A one-off scrape is stale the week after you run it; a scheduled one keeps the table current without anyone remembering to.

What you can schedule

Any import action can be put on a schedule — Search Job Listings, Find Local Businesses, the scrapers, and RSS Feed.

A schedule stores the action, its inputs, its column mapping, and the frequency. Each run appends new rows to the same table using that saved mapping, so the table shape stays stable across runs.

Scheduling an import

Configure the import action as you normally would and run it once manually
Confirm the output and the column mapping are right — the schedule reuses that mapping on every run
Open Table → Import → Manage scheduled imports
Click New schedule, pick the action, and set the frequency and run time
Save it — the first automatic run happens at the next matching slot

Always run it manually once first. A schedule built on an unverified mapping repeats the same mistake on every run, and you find out a week later.

Managing existing schedules

The management screen lists every schedule in the table with its action, frequency, next run and last run. From there you can:

Action	What it does
Pause / resume	Stops future runs without deleting the schedule or its mapping
Edit	Change the inputs, the frequency or the run time
Run now	Fire the schedule immediately, outside its normal slot
Delete	Remove the schedule — rows it already created stay in the table

Deleting a schedule never deletes the rows it produced. Pausing is the reversible option; use it while you investigate a run that looks wrong.

Cost and credits

Every scheduled run spends credits exactly as a manual run does, and it does so without anyone watching. A daily import returning 200 rows is 30× a monthly one over a month.

Cap the result count on the action before you schedule it
Check credit usage after the first few automatic runs, not after a month
Pause schedules on tables you have stopped working — an abandoned daily scrape is the most common source of surprise spend

Common use cases

Daily hiring sweep. New reqs matching your ICP arrive each morning, already enriched by Auto Run.
Weekly directory pull. A niche directory checked every Monday, with dedupe keeping only genuinely new entries.
Feed monitoring. An RSS feed polled hourly for funding or product announcements.
Recurring social sweep. The same hashtag or subreddit re-scraped weekly to catch new posters.
Territory refresh. A local business search per suburb, re-run monthly as listings change.

Best practices

Run manually once and verify the mapping before scheduling anything
Match the frequency to how fast the source actually changes — a directory that updates monthly does not need a daily scrape
Put dedupe in front of enrichment; every recurring source re-returns items you already have
Pair schedules with Auto Run so new rows enrich themselves
Give each recurring source its own table rather than pointing several schedules at one
Review the schedule list monthly and pause anything feeding a table nobody opens

Where to next

Lead Sourcing — every action you can put on a schedule
Auto Run — enrich rows the moment a scheduled run creates them
Dedupe — keep recurring runs from stacking duplicates
Credit usage — watch what unattended runs are spending