Documentation

ATS integration planning

Connect screening to your hiring workflow without overcomplicating day one. We start with dashboard or batch intake, then scope ATS automation where it meaningfully reduces retyping and status chasing.

Current approach

Information Direct supports ATS-friendly workflows through account setup, dashboard order requests, release-form review, batch intake, and operations handoff. Native ATS marketplace apps and direct API automation are scoped case by case rather than enabled as a public self-serve feature.

Good first integration goals

  • Reduce duplicate entry. Capture candidate name, email, role, package, and external requisition ID once.
  • Keep release forms organized. Attach signed disclosure and authorization documents to the order request or approved operations workflow.
  • Route status clearly. Decide whether status belongs in the dashboard, email, ATS notes, or a secure integration endpoint.
  • Preserve audit trails. Keep timestamps, actor, order reference, and action type without logging raw sensitive identifiers.

Systems we can evaluate

We can discuss integration patterns for systems such as Greenhouse, BambooHR, Workable, iCIMS, Lever, Workday, JazzHR, SmartRecruiters, and custom internal tools. The exact path depends on each platform's API access, your admin permissions, your compliance workflow, and Digital Delve/provider sign-off for any automated send or report handoff.

Recommended rollout

  1. Dashboard first. Use the Information Direct dashboard for order requests, release uploads, and operations alerts.
  2. Batch intake second. For higher volume, standardize CSV or structured batch uploads so operations can process many candidates consistently.
  3. ATS handoff third. Add ATS links, status notes, or integration endpoints once package matrix and release-form handling are stable.
  4. Automation last. Enable automated sends or report SSO only after credentials, templates, webhook controls, and provider approvals are verified.

What we need from your team

  • ATS name and admin contact.
  • Candidate fields available in the ATS.
  • Package defaults by role, location, or department.
  • Release-form process and retention requirements.
  • Whether status updates should return to recruiters, HR admins, or a shared mailbox.
  • Security requirements such as SSO, IP allowlists, vendor review, and audit export.

Need help scoping?

Email support@informationdirect.us with your ATS, expected monthly volume, and desired package matrix. We will recommend whether to start with dashboard intake, batch workflow, provider SSO, or a custom integration plan.

Was this helpful? Tell us what's missing
Create Account