Bulk actions from a project
Multiple project actions on a selection of candidates at once: reveal contacts, add to campaign, push to ATS, export, or remove.
CLIENT-ONLY · How-To
Outcome
Section titled “Outcome”One action applied to many candidates at once, instead of repeating it per profile.
Prerequisites
Section titled “Prerequisites”- A project with multiple candidates
- Permissions for the action (reveal needs credits, ATS push needs the integration)
- Open the project and select candidates with the checkboxes. The header checkbox selects all on the page.
- The bulk action bar appears.
- Choose the action:
Working past the 200-profile cap
Section titled “Working past the 200-profile cap”Bulk actions are capped at 200 profiles per action to keep the system fast and predictable under load. To process a larger set:
- Select the first 200 profiles. Apply the bulk action (add to project, add to campaign, etc.).
- Click the selection arrow at the top of the column and choose
Skip 200. This unselects the first 200 and selects the next 200. - Apply the same bulk action again.
- Repeat until the full set is processed.
This works the same way across the search results view and the project view. The 200 cap is a per-action limit, not a daily limit, so you can run as many passes as the set needs.
Reveal contacts
Section titled “Reveal contacts”Runs each profile through the waterfall. Credits are deducted as matches are found; profiles where nothing is found cost nothing. See Reveal candidate contact information.
Add to campaign
Section titled “Add to campaign”Pick the destination campaign and confirm. Profiles without revealed contact info are flagged; reveal them first or let Wiggli skip them.
Add to ATS
Section titled “Add to ATS”Pick the vacancy, the pipeline stage, an optional note, and confirm. Up to 200 profiles per bulk action.
Export to CSV
Section titled “Export to CSV”Confirm to export. Monthly limits by plan: Hunter 250/month and 100/action, Strategist 1,000/month and 250/action, Oracle 1,500/seat and 500/action.
Remove from project
Section titled “Remove from project”Removes the candidate from this project only. They stay in our database and any other projects.
[SCREENSHOT: Project view with the bulk action bar]
Verification
Section titled “Verification”Each action returns a confirmation with the count processed and any skips (e.g. “180 added, 20 skipped, missing contact info”). Spend history reflects any reveal charges. The ATS shows newly added candidates under the chosen vacancy and stage.
Troubleshooting
Section titled “Troubleshooting”- Bulk button grayed out. No candidates selected.
- “Selection limit reached.” Per-action caps apply (typically 200). Process in batches.
- CSV missing fields. Plan-dependent. Custom export mapping is Oracle-only.
- Candidates skipped in Add to campaign. Usually duplicate profiles. Check the skip reason in the confirmation.
Best practices
Section titled “Best practices”- Reveal first, then add to campaign. Avoids skipped profiles.
- Push to the ATS only after screening. Sourced stage is fine; earlier stages clutter the pipeline.
- ATS push is cleaner than CSV export for handing candidates to the team.
Related articles
Section titled “Related articles”Still stuck?
Your customer success manager reads faster than any search bar.