Skip to content
LeadFuzeLeadFuze

Run a saved search on a schedule

Set Automatic contact lists on a saved filter to Daily or Weekly and LeadFuze builds a list of new matches for you on that schedule. Each newly delivered contact uses one enrichment credit.

#Set up a schedule

  1. #Open the save window

    Set your filters on the Find people tab, then click Save these filters.

  2. #Name the filter

    Enter a Filter name of up to 80 characters.

  3. #Choose a schedule

    Pick an option in Automatic contact lists:

    OptionWhen it runs
    Off, save criteria onlyNever. The criteria are just saved.
    Daily at 09:00 in account timezoneEvery day at 09:00
    Weekly, Monday at 09:00 in account timezoneEvery Monday at 09:00

    If your account timezone is missing or invalid, runs use UTC.

  4. #Set a maximum

    In Maximum new contacts per scheduled run, enter a number from 1 to 100,000. The default is 1,000.

  5. #Click Save filters

    The first run happens at the next 09:00 (daily) or the next Monday at 09:00 (weekly) after you save.

#What each run produces

Each run searches with your saved criteria and builds a contact list. The list is named after your saved filter, shortened if needed, followed by the run date, for example "Texas CEOs 2025-01-06". Find it under My lists & exports. Lists keep processing if you leave the page.

#What it costs

  • Each newly delivered contact uses one enrichment credit.
  • Repeat access to a contact within 30 days is free.
  • Only successfully retrieved contacts are charged.
  • A list stops when your available credits run out. Partial files keep the contacts that were completed.
  • A run never delivers more than your Maximum new contacts per scheduled run.

Warning

Scheduled runs spend credits without you being present. Choose a maximum you are comfortable with and keep enough credits available.

#Stop a schedule

Open the saved filter, set Automatic contact lists to Off, and save again.

#When a schedule turns itself off

A schedule is switched off automatically if the person or API key that created it is no longer authorized. This happens when:

  • The API key used to create it is no longer active.
  • The user who created it no longer belongs to the account, or no longer has the Account Admin or Account User role.

If the source is unavailable, a run is retried up to 3 times. If it still fails, it is recorded with the error source_unavailable. The schedule itself stays on for the next run.

Was this article helpful?