Skip to content
WiggliWiggli Knowledge Base
Integrations

Adding Candidates to the Wiggli ATS

Candidates pushed from Intelligence into a Wiggli ATS vacancy and pipeline stage, individually or in bulk.

CLIENT-ONLY · How-To

Outcome

Section titled “Outcome”

Candidates added to the right ATS vacancy and stage, with source attribution.

Prerequisites

Section titled “Prerequisites”
  • The ATS integration set up (see Integration with the Wiggli ATS)
  • The candidate selected in a search result or project
  • A vacancy in the ATS with at least one pipeline stage

Steps

Section titled “Steps”

Single candidate

Section titled “Single candidate”
  1. Open the profile and click Add to ATS.
  2. Choose the export method:
    • Reveal Contacts & Proceed. Wiggli runs the waterfall; credits are deducted as matches are found. The contact info is attached to the profile, then the export continues.
    • Proceed Without Revealing. Skip the reveal; the ATS record uses whatever contact info is already on the profile.
  3. In the Add Talent to ATS panel:
    • Select the Vacancy (browse or search by Vacancy ID).
    • Choose the Pipeline Stage (typically Sourced).
    • Leave a Note (optional).
  4. Confirm.

Bulk

Section titled “Bulk”
  1. From search results or a project, select candidates with the checkboxes (up to 200).
  2. Click Add to ATS.
  3. Same process: vacancy, stage, optional note, confirm.

[SCREENSHOT: Add Talent to ATS panel with vacancy and stage selectors]

Verification

Section titled “Verification”

A confirmation shows the count added. In the ATS, the candidates appear under the chosen vacancy and stage, with source marked “Wiggli Intelligence”.

Troubleshooting

Section titled “Troubleshooting”
  • Add to ATS grayed out. Integration not set up. Check Settings, Integration.
  • “Vacancy not found.” The vacancy is archived/closed, or you lack access. Confirm in the ATS.
  • “Duplicate candidate.” Already in that vacancy. Duplicates are blocked.
  • Bulk add, some missing in ATS. Usually duplicates, which Wiggli skips without failing the batch. After every bulk push, an export report (an Excel file) lands in your Intelligence notification center, listing each profile as succeeded or failed. Open it to see exactly what happened instead of guessing. If profiles failed for any reason other than duplicates, send the report to support.
  • Added to wrong vacancy. No undo. Reassign in the ATS manually.

Best practices

Section titled “Best practices”
  • Reveal contact info before pushing when possible. The ATS record is more useful with email and phone.
  • Check for the Already in ATS tag before revealing or adding. The tag appears on search results and project rows when the profile already exists in your ATS, so you can skip the reveal (and the credits) for candidates you already have.
  • Use the note field to pass context: which search, which Co-pilot signal flagged them.
  • Push to Sourced by default. Earlier stages clutter; later stages skip useful steps.
  • For bulk pushes, double-check the vacancy. 200 candidates in the wrong vacancy is painful to undo.
Section titled “Related articles”

Still stuck?

Your customer success manager reads faster than any search bar.

Get help