The short answer: Rippling customers use Proof for pre-hire Screen and Identify checks, but the integration is API-limited — recruiters can't see results inline on the candidate card, so email notifications (in progress) are becoming the main way recipients learn a check has been completed.
1. How the Integration Works Today
Recruiters using Rippling as their ATS currently have to manually send Proof links to candidates, then log into a separate UI to view results — Rippling's API doesn't support writing directly to candidate records or triggering workflows from third-party apps, so there's no native, inline result view on the candidate card. Proof writes results to custom objects, which live in a separate section of Rippling rather than attached to the candidate record itself.
2. Known API Constraints
These are current limitations of Rippling's API — not bugs on Proof's side. Set customer expectations accordingly.
3. Email Notifications for Completed Screenings
To bridge the gap while results stay hard to find inline, Proof is adding a configurable email notification that fires when a Screen or Identify experience completes. The recipient list is set at the account or job level, so it can be pointed at whoever the customer wants to review results.
Summary Checklist
- Set expectations that results won't appear inline on the Rippling candidate card — this is an API limitation, not a bug.
- Confirmed whether the customer is asking about email notifications, hard gating, or the inline view before responding — these are different asks with different answers.
- Did not commit to hard gating or a native inline Rippling view — both are currently unsupported by Rippling's API.
Updated