Skip to content
WiggliWiggli Knowledge Base
Integrations

Connecting a third-party ATS (TeamTailor, Recruitee, and others)

A connection between Wiggli Intelligence and a non-Wiggli ATS (TeamTailor, Recruitee, and others), so candidates push from Intelligence into your ATS with one click.

CLIENT-ONLY · How-To

Outcome

Section titled “Outcome”

A working integration between Intelligence and your existing ATS that lets you push candidates into vacancies and pipeline stages without leaving Wiggli.

Supported ATS systems

Section titled “Supported ATS systems”

Wiggli connects to several third-party ATS platforms in addition to the Wiggli ATS. The integration tab in Settings shows the full list of currently supported systems. TeamTailor and Recruitee are the most commonly used. [GAP: confirm the full list of currently supported third-party ATS systems. Add CRM-style platforms here if relevant.]

If the ATS you use isn’t listed, contact your Wiggli customer success manager. Integration with a new ATS may be possible.

Beyond live integrations, Wiggli also runs full data migrations from platforms such as Lever: postings, candidates, notes, feedback, and files move over via an API key and a scoping document, typically within three to five weeks depending on data volume. Ask your customer success manager to set one up.

Prerequisites

Section titled “Prerequisites”
  • Strategist or Oracle plan
  • An active account in the target ATS
  • Admin access in the ATS (needed to generate an API key and configure scope)
  • Super Admin access in Intelligence (needed to configure the integration)

Why integrate

Section titled “Why integrate”
  • Candidates flow from sourcing into the ATS pipeline without manual re-entry
  • Profiles already in your ATS are flagged in Intelligence with an Already in ATS tag, so recruiters skip duplicate reveals (and save credits)
  • One workspace for the team, one source of truth for candidate progression

Steps

Section titled “Steps”

Step 1: Generate the API key in your ATS

Section titled “Step 1: Generate the API key in your ATS”

The exact navigation depends on the ATS, but the pattern is the same across platforms.

  1. Sign in to your ATS as an admin.
  2. Go to your ATS settings and find the API or integrations section.
  3. Create a new API key. Give it a clear name (e.g. Wiggli Intelligence) so you can identify it later if you need to revoke or rotate it.
  4. Set the scope to admin.
  5. Set the permissions to read, write, and create.
  6. Confirm and copy the key. Most ATS platforms show the key only once. Save it somewhere temporary while you finish the setup.

TeamTailor specifics

Section titled “TeamTailor specifics”

In TeamTailor, the API key lives under Settings > API Keys. When generating the key:

  • API scope: admin
  • Permissions: tick read, write, and create
  • After saving, TeamTailor displays the key. Copy it.

Step 2: Connect the ATS in Intelligence

Section titled “Step 2: Connect the ATS in Intelligence”
  1. Sign in to Intelligence as a Super Admin.
  2. Click the Settings gear.
  3. Open the Integration tab.
  4. Select the ATS from the list of supported integrations.
  5. Paste the API key.
  6. Submit.

[SCREENSHOT: Integration tab with the third-party ATS connection form]

Step 4: Wait for the initial sync

Section titled “Step 4: Wait for the initial sync”

The first sync gives Intelligence enough ATS context to support duplicate detection from the start. For small databases (a few hundred candidates) this takes a few minutes. For larger databases (10,000+ candidates) it can take until the following morning. The integration is usable as soon as it’s connected; the Already in ATS tag becomes accurate as the sync completes.

Verification

Section titled “Verification”

The Integration tab shows the connection as active. The Add to ATS action is available on profiles and projects, with the ATS logo visible. Once the initial sync is complete, search results for known candidates from your ATS show the Already in ATS tag.

Test with a single candidate push before rolling out to the team. In the ATS, confirm the candidate appears in the correct vacancy and pipeline stage, with source attributed to Wiggli.

Troubleshooting

Section titled “Troubleshooting”
  • “Invalid API key.” Check for stray spaces. Confirm the key was created with admin scope and read/write/create permissions. Regenerate if needed.
  • Integration not visible in Settings. Third-party ATS integration requires Strategist or Oracle.
  • Push works, but no Already in ATS tags. The initial sync is still running.
  • Sync taking longer than expected. Large ATS databases (30,000+) can take several hours. If it’s been over 24 hours, contact support.
  • API key revoked or rotated in the ATS. The integration breaks silently. Generate a new key and reconnect in Intelligence.
  • Worked, then failed. Most often the API key was regenerated, the API user was deactivated, or the ATS revoked the integration. Check the ATS first.

Best practices

Section titled “Best practices”
  • Generate a dedicated API key for Wiggli rather than reusing one from another integration (Zapier, Mailchimp, etc.). A dedicated key is easier to audit and rotate without breaking other tools.
  • Note who generated the key and when. If they leave the company, the integration may need to be reconnected with a new key.
  • Set up the integration during onboarding so the team learns the sourcing-to-ATS workflow from day one rather than retrofitting it later.
  • Accept webhook setup when prompted. The credit savings from accurate duplicate detection add up.
  • Test with one candidate before pushing in bulk. Wrong vacancy on a 200-profile bulk push is painful to undo.
Section titled “Related articles”

Still stuck?

Your customer success manager reads faster than any search bar.

Get help