Recent runs
Start a run
Select stages to run. Overrides apply to this run only — they are merged onto your saved settings and never stored.
Run history
| Run | Stages | Status | Created | Duration |
|---|
Keyword → Jobs → Contacts
Expand a keyword to see the jobs it scraped, then a job to see its contacts. Tick jobs to add them to a campaign — any missing AI/enrichment steps run automatically.
| Company | Role | Keyword | Sector | Status | Location | Contacts |
|---|
| Name | Verify | Source | Title | Company | List | Lead |
|---|
Contact lists
Named buckets of leads on Instantly (separate from campaigns). Build/segment lists, then campaign later.
| Name | Contacts | Instantly ID |
|---|
Contacts grouped by list / keyword
Every enriched contact is grouped into a list named for the keyword that found it. Click a group to view its contacts.
Saved segments
Reusable contact filters saved from the Contacts tab (local — nothing is written to Instantly).
| Name | Matches | Filters |
|---|
| Niche | Sector | Name | State | Daily | Contacts | Instantly ID |
|---|
Approved outreach copy
This fixed sequence is sent to every lead — no AI generation. Only merge tags are filled per recipient.
Settings
Every setting is a field below, stored in the database — no JSON editing, no redeploy. API keys are never stored here: they stay in .env.
Advanced — edit the raw settings JSON
For keys the form doesn't cover. Saving here replaces the whole document and is validated the same way as the form.
Danger zone
Deletes every job, contact, campaign record, contact list, saved segment and run from this database — a clean slate to start over. Your config above is kept. This cannot be undone. Campaigns and lists already pushed to Instantly are not deleted there; re-running creates new ones rather than reusing the old ones.