Recruit links the outside tools your team already uses — skills tests, interview-integrity checks, CRM, HR systems, calendars, company sign-in, messaging, email, and your careers page. The connections are already built. To turn one on, an admin enters that provider's login or key. There's no development work to do.
Find the app, connect credentials, work from the hiring record, monitor connection health.
Every connection is described with its category, current status, setup effort, health signal, and governance notes — all in one place.
Active connections show their enabled state, credential check, test action, and webhook status so admins know immediately if something needs attention.
Assessments, interview integrity, CRM, HRMS, calendars, SSO, messaging, email, external API, careers page, and background checks are all on one page.
Admins configure credentials in the settings pages. Recruiters then trigger checks and view results from the candidate record — no portal switching needed.
Scores, reports, email delivery, and API events are stored against the candidate's hiring record and timeline, not in disconnected external accounts.
Each card below shows what the connection does, whether it is live today or on the roadmap, how much setup is involved, and who is responsible for that setup.
Schedule interviews and generate meeting links without leaving Recruit. Recruiter availability stays inside the hiring workflow, and calendar access is limited to what scheduling needs.
Team members sign in with Microsoft or Google. Role assignment and login approval still happen inside Recruit, so access does not bypass the normal governance flow.
Send skills tests to candidates straight from their record in Recruit. The connection is built and works with any test provider. An admin adds your chosen provider's login to switch it on, and scores come back automatically against the right job and interview round.
Proctoring tools check for suspicious activity during remote interviews and send a report to Recruit. The report attaches to the interview round so the hiring team reviews it alongside the evaluation — not in a separate portal.
AI-generated notes and interview summaries are stored on the hiring record, linked to the correct round. Interviewers spend less time writing up notes and more time on the evaluation itself.
Candidate and contact records stay in sync between Recruit and HubSpot. Account Managers and recruiters see the same information without switching between tools.
When a candidate is hired, their accepted offer details move to your HR system automatically. There is no need to re-enter the same information a second time.
Hiring notifications — offer approvals, stage changes, interview reminders — go to the Slack, Teams, or Telegram channels your team already uses. No one needs to log into Recruit to stay informed.
Candidate updates are sent from Recruit using your own mail settings, so emails arrive from your domain rather than a generic sender. Admins control the SMTP configuration.
Hiring events are sent to your own systems the moment they happen. Admins choose which events are sent, and the API lets your technical team build custom integrations against Recruit data.
Open roles are published to your careers page automatically as they are created in Recruit. The page is configurable by admins and does not require a developer to update job listings.
Planned: publish roles to external job boards from Recruit and track which board each application came from. Recruiting leads will be able to see which channels produce quality candidates.
Background check status — pending, cleared, or flagged — will appear in the candidate hiring timeline. The offer workflow will wait for clearance before proceeding.
The Integration Marketplace connects to the admin settings pages and hiring record pages already in Recruit. There is no separate system to learn.
Browse by category, current status, or setup effort to find the connection your team needs.
Admins enter provider URLs, API keys, and webhook secrets in the Recruit settings pages. No development work is required for most connections.
Recruiters send tests, trigger checks, and review results from the candidate record — not from separate vendor portals.
Each connection shows its current state, last result, and any errors. TA leads can check status without asking IT.
Recruiters interact with connected tools from within the candidate record in Recruit. The vendor handles delivery; Recruit handles the result, the health signal, and the audit trail.
Results arrive via the provider's webhook and are stored on the candidate record automatically. No manual import is needed.
Send skill tests from the candidate screen. Score, time taken, and completion status come back to the candidate record linked to the correct job and stage.
Proctoring tools check for suspicious activity during remote interviews. Reports attach to the interview round for the hiring team to review — not a separate dashboard that no one visits.
Background check status — pending, cleared, or flagged — appears in the candidate hiring timeline. The offer workflow waits for the right status before proceeding.
The admin command centre shows pending checks, received results, and flagged items across all open roles. TA heads and Account Managers can review integration status without logging into individual vendor accounts.
View full size
Captured Jun 16, 2026
Source: local seeded admin command-centre capture
Integrations are built to reduce the number of portals recruiters need to maintain — not add another one. Every result feeds the existing hiring record and timeline.
Credentials are entered by admins, masked after saving, and testable without exposing the raw value anywhere in the application.
Each active integration shows its enabled state, a test action, and the last result or error. Webhook readiness is shown where relevant.
Scores, reports, and status updates are stored against the candidate timeline with the provider name, timestamp, and the job and round they belong to.
Setup and credential management are restricted to admin roles. Day-to-day recruiter actions happen from the normal hiring pages.
Compare connections, configure provider health, and route results back to the hiring record.