Integrating Incode with Ashby ATS

Overview

This guide explains how to integrate Incode Workforce identity verification into Ashby ATS, embedding trust and compliance into your recruiting workflow. By verifying candidates during key stages of the hiring journey, you reduce fraud risks, meet compliance obligations, and ensure fair hiring practices.

We’ll cover:

• The candidate journey with identity verification in Ashby
• How to orchestrate automation with Tines
• Custom integration steps with Ashby ATS
• What eKYC means in hiring

Candidate Journey

Below is a typical candidate journey showing where Incode fits into the Ashby recruiting pipeline:

1. Application Submission – Candidate applies via the Ashby job board.
2. eKYC Check – Candidate’s phone number and email are run through Incode’s electronic Know Your Customer (eKYC) risk engine.
3. Risk Scoring & Routing
   • High risk → Immediate ID verification (document + selfie).
   • Medium risk → Verification required before recruiter or hiring manager interview.
   • Low risk → Candidate progresses directly into interviews.
4. Final Verification – Prior to offer, all candidates complete a final Incode ID verification.
5. Results Sync – Verification outcomes (status, risk score, timestamp) are written back into Ashby, stored on the candidate’s profile.

This layered trust model ensures every stage of hiring has the right identity assurance level.

What is eKYC?

eKYC (electronic Know Your Customer) is a digital identity verification process. While traditionally used in banking, eKYC in ATS workflows means:

• Using candidate attributes (email, phone, IP/device signals) to detect risk.
• Checking for fraud history, synthetic identity patterns, or data mismatches.
• Returning a risk score (Low, Medium, High) that informs how the candidate is routed.

Recruiters benefit by focusing on real candidates, while risky applicants are flagged for earlier and stricter verification.

Integration with Ashby via Tines

We use Tines to automate the flow between Ashby → Incode → Ashby.

Example Flow in Tines

• Trigger: Candidate submits an application in Ashby.
• Action: Tines pulls candidate details (name, email, phone) via the Ashby API.
• Verification: Based on eKYC results, Incode sends the candidate an ID verification link.
• Callback: Incode returns verification results to Tines.
• Update: Tines pushes verification status back into Ashby ATS.

Step-by-Step Custom Integration Guide

1. Prerequisites

• An Ashby ATS account with API access.
• An Incode Workforce developer account.
• A Tines workspace for automation orchestration.

2. Configure Ashby Webhooks

Set up a webhook in Ashby to trigger when a candidate is created or changes stages.

• Navigate to Admin -> Integrations -> Webhooks

• Event: Application Submitted and Candidate Application Changed Stage

• Payload: Candidate’s basic details (name, email, phone)

• Destination: Your Tines webhook URL

3. Configure custom Candidate Fields in Ashby

• Navigate to Admin -> Organization Setup -> Custom Fields

• Under Candidate, create custom fields for the desired Incode results

  • Phone Risk Score [Incode]
  • Email Risk Score [Incode]
  • First Name [Incode]
  • Last Name [Incode]
  • Verification Result [Incode]
  • Selfie Image [Incode]

4. Build a Tines Story

• Import the Tines example story.
• Configure credentials for Ashby and Incode APIs.
• Add decision logic for routing based on eKYC risk scoring.

5. Connect to Incode APIs

Use the Incode Workforce API to initiate and track verification:

• POST /ekyc/check → Initiates risk screening.
• POST /identity/verify → Sends document + selfie verification link.
• GET /identity/status/{id} → Retrieves real-time verification results.

6. Sync Results to Ashby

• Push verification results back into Ashby using its API.
• Populate candidate custom fields like Verification Status and Risk Score.
• Optionally configure Ashby automation rules to auto-advance or hold candidates based on verification results.

Example Use Cases

• High-volume recruiting – Filter out fraudulent applications at scale.
• Sensitive roles – Enforce mandatory verification before interviews.
• Global compliance – Satisfy KYC/AML requirements in regulated hiring environments.

Benefits

• Seamless – Recruiters never leave Ashby. Verification data is displayed inline.
• Secure – Detects fraudulent candidates before they reach interview stages.
• Frictionless – Most candidates only verify once, while high-risk profiles undergo additional checks.

Next Steps

• Map your hiring workflow in Ashby to the verification checkpoints.
• Import and adapt the Tines Story (other SOAR tool of choice) to Ashby.
• Test with sample candidates before rolling out to recruiters.

By combining Ashby ATS, Tines, and Incode, you can embed identity trust directly into your recruiting pipeline, keeping hiring efficient, secure, and compliant.