← Ashby tab · Help

𝒳Chk for Ashby — setup

When an interview is scheduled in Ashby, xChk puts two links on the candidate: the xChk interview link for interviewers (the candidate's interview page, details filled in) and the xChk verification link for the candidate. Ashby's own calendar invites carry them. Everyone on the interview panel is let in automatically. After the check, xChk fills xChk receipt and xChk risk (the network and device verdict, e.g. High 84: VPN, Datacenter) and adds a note on the candidate with the rating, the risk flags and the history link. Only verdicts go to Ashby; IP addresses, locations and device fingerprints stay in xChk behind the history link.

1. Create the API key in Ashby

Admin → Integrations → API Credentials → New. Leave Integration Partner empty. Tick:

Module	Access	Why
Candidates	read + write	read name/email/phone; write the xChk fields and the close note
Interviews	read	schedules and their interviewers
Jobs · Organization	read	the job; users, to verify the key
Hiring Process	read, write once	creates the three xChk fields on first connect
API Keys	write (optional)	lets xChk register its webhooks itself

Ashby shows the key once — copy it before closing the dialog.

2. Connect it in xChk

Developer → Ashby tab. Paste the key, check the owner email, Save & verify. The note under the button says what happened: fields created, webhooks registered (applicationSubmit, interviewScheduleCreate, interviewScheduleUpdate), or the permission that is missing. The first working key switches the integration on.

3. Let invites use the fields (Ashby, one tick per field)

Admin → Organization Setup → Custom Fields → Candidate → xChk interview link → tick Enable in Email Templates. Same for xChk verification link.

Ignore "Substitution Token" — that is for offer letters and e-signature documents, not invites. Ashby's API cannot tick this box, so it is a click.

4. Put the links in the default invites (once, for every interview)

Admin → Interviews & Scheduling → Scheduling Defaults → Communication. In each template, place the cursor and use the editor's T (Insert token) button — typing the words does not make a token.

Invite to Interviewers Template — first line:

Invite to Candidate Template — after the agenda:

Interview plans or single schedules that override the defaults need the same line. Reload any open scheduling page after step 3, or the tokens will not be in its menu.

5. Make sure Ashby can send invites

Ashby sends invites through the scheduler's connected Google or Microsoft calendar. If a schedule shows Pending invites after you click Schedule, connect your calendar in Ashby, then use Send to Interviewers / Send to Candidate on the schedule's overview.

6. Feedback form (recommended)

Admin → Interviews & Scheduling → Feedback Forms → New, titled exactly xChk identity check. Keep Overall Recommendation and Feedback; add a Short Answer question xChk risk and a URL question Interview history. Each check is then filed as real Ashby feedback on its interview: stars → recommendation (5 Strong Yes, 4 Yes, 3 No, 2–1 Strong No), the risk verdict and flags, and the history link. Without the form, xChk adds a note instead.

7. Try it

1. Start scheduling an interview for a candidate who has a phone number, with yourself on the panel.
2. Communications → Calendar Invites → Preview: your invite shows an in.xchk.io/interview.html?id=… link, not N/A.
3. Click Schedule. Open the link from your invite: the candidate's page opens with name, email and phone filled in.
4. Press Send SMS (use your own number for a test), run the check, mark the result. Ashby shows the receipt field and a note on the candidate.

---

Troubleshooting

• Preview says N/A. The link is filled in when the invite is sent, from the candidate's profile. Press Sync now on the xChk Ashby tab, then reload the scheduling page.
• xChk tokens missing from the token menu. Step 3, then reload the page.
• No invite email. Look at the schedule in Ashby — Pending invites means Ashby has not sent them (step 5). Ashby sends invites, not xChk.
• Ashby tab says "disabled". Tick enabled; events are acknowledged and ignored while it is off.
• "last REJECTED … secret does not match". Edit the webhook in Ashby → Admin → Webhooks and paste the secret shown on the xChk tab.
• Interviewer can't open the page. They must be on the schedule's panel with the same email they sign in to xChk with. The page re-checks Ashby when they open it.

Disconnect: xChk Ashby tab → Disconnect, then delete the three webhooks and the API key in Ashby. Questions: support@xchk.io