Skip to content
WiggliWiggli Knowledge Base
Integrations

Integration with the Wiggli ATS

The Wiggli ATS connected to Intelligence, so candidates push from search and projects straight into ATS vacancies with one click.

CLIENT-ONLY · How-To

Outcome

Section titled “Outcome”

A working ATS integration that lets you push candidates into vacancies and pipeline stages.

Prerequisites

Section titled “Prerequisites”
  • Strategist or Oracle plan
  • An active Wiggli ATS account
  • Super Admin Owner credentials in the ATS (needed to generate the API key)

Why integrate

Section titled “Why integrate”
  • Centralized candidate data, with progression tracked in the ATS
  • The sourcing-to-pipeline handoff automated
  • Shared team access to candidate data and insights
  • ATS data feeding back into your sourcing decisions

Steps

Section titled “Steps”

Step 1: Generate the API key in the ATS

Section titled “Step 1: Generate the API key in the ATS”
  1. Sign in to the Wiggli ATS as Super Admin Owner.
  2. [GAP: confirm the navigation path to API key generation in the ATS.]
  3. Generate a new API key.
  4. Copy and save both the API Key and your Customer ID. The key is shown only once.

Step 2: Set up the integration in Intelligence

Section titled “Step 2: Set up the integration in Intelligence”
  1. Sign in to Intelligence as a Super Admin.
  2. Click the Settings gear (bottom left).
  3. Open the Integration tab.
  4. Click Request Integration.
  5. Paste your API Key and Customer ID.
  6. Submit. A success notification confirms activation.

[SCREENSHOT: Integration tab with the Request Integration form]

Verification

Section titled “Verification”

A success notification appears. The Integration tab shows the connection as active. The Add to ATS action becomes available on profiles and projects.

Troubleshooting

Section titled “Troubleshooting”
  • “Invalid API Key.” Check for stray spaces. Regenerate if needed.
  • “Customer ID not found.” Use the Customer ID from your ATS, not the workspace ID.
  • Integration not visible. Native ATS integration requires Strategist or Oracle.
  • Worked, then failed. The API key may have been regenerated in the ATS. Reconnect with the new key.

Best practices

Section titled “Best practices”
  • Set up the integration during onboarding. It shapes how recruiters use projects and pipelines.
  • Note who generated the API key and when. If they leave, you may need to regenerate.
  • Test with a single candidate push before rolling it into the team’s workflow.
Section titled “Related articles”

Still stuck?

Your customer success manager reads faster than any search bar.

Get help