When you use Get on Board integrations to export candidates from your recruiting process to an external ATS, this article is for your company team members who received an integration-disabled email.
Why this email was sent
You receive this email when Get on Board detects repeated authentication failures while exporting candidates to your external ATS integration (Lever or Greenhouse).
The system monitors auth errors from your ATS credentials. If it detects repeated failures, it disables the integration automatically to prevent continuous failed exports.
Exact trigger
The email is sent when all of this is true:
- Candidate exports return authentication errors (
401or403). - The same integration reaches 3 auth failures in a rolling 24-hour window.
- The integration is still enabled at the moment the threshold is reached.
When the threshold is reached, Get on Board disables that integration and notifies your confirmed team members.
What is affected after auto-disable
After the integration is disabled:
- New candidate exports to that ATS stop.
- Export retries do not keep running against a disabled integration.
- Your recruiting process in Get on Board remains available; the issue is specifically the external ATS export connection.
What to do now
- Go to your Integrations settings in Get on Board:
/external-systems - Open the affected provider (Lever or Greenhouse).
- Update or reconnect credentials (API key/token, permissions, or account access).
- Re-enable the integration.
- Validate by sending a new export and confirming it appears in your ATS.
Common causes
Common reasons include:
- Expired, rotated, or revoked API key.
- Credentials with missing permissions.
- Provider-side access changes (user removed, role changed, workspace restrictions).
- Lever keys that are not valid for candidate export operations.
Who receives this email
Get on Board sends this notification to your confirmed team members. Each recipient gets the message in their own locale when available.
More from Integrations and developer tools
