Skip to main content
Data Export lets you take everything Alex holds about your hiring out as CSV files, so you can report on it in a spreadsheet or load it into another system.

​
Requesting an export

  1. Log into your Alex dashboard.
  2. Go to Settings → Data Export.
  3. Switch on each entity you want, and set its filters. The count next to each entity shows how many records the filters match.
  4. Enter one or more email addresses and click Start Export.
Alex builds one CSV file per entity, compresses them into a single ZIP archive, and emails a download link to every address you entered. The email also lists the filters each file was built with, so it can be filed as a record of the export.

​
History and reruns

The History tab lists every export your company has requested, who requested it, the entities and filters it covered, and when it was created. A completed export can be downloaded from the row. An expired export can be rerun: the rerun opens with the same entities and filters, which you can change before starting it.

​
The entities

Each entity is one file in the archive, with one row per record. Where your company is connected to an ATS, the ATS’s own identifiers appear in extra columns named after it, such as Bullhorn ID or Bullhorn Req ID.

​
Jobs

One row per job.

​
Candidates

One row per candidate, with their most recent application and interview.

​
Interviews

One row per interview.

​
Activity

One row per event on a candidate’s Activity thread: every message, call, interview, workflow step, ATS write, task, note, application, status change and recruiter-call handoff, in the order it happened. It is the same thread you see on the candidate’s Activity tab. The export covers the candidates invited to interview in the date range you choose, on the jobs you choose, and includes their whole history, not only the events inside the range. A date range is required, and one export covers up to 5,000 candidates; narrow the date range or the jobs to export more in parts. What the columns hold:
  • Kind is the event’s type: message, call, interview, step, ats, task, note, application, status or handoff.
  • Actor is who did it: alex, candidate, system, or the name of the recruiter or outside sender.
  • Channel, Direction and Recipients are filled for messages: email, sms or whatsapp; in or out; and the address the message went to when the row records one.
  • Event is the one-line summary: a message’s subject, a call’s title, a workflow step’s name, a task’s name, a status change’s new status, or a handoff call’s title.
  • Outcome is how it ended: a step’s result or state, a task’s state, what changed a status (ats:Bullhorn, dashboard, withdrawal, reopen), a handoff’s outcome (booked, rescheduled, cancelled, missed, no_availability, completed), an interview’s recommendation, or why a message or call failed.
  • Detail is what the event did, flattened: the fields a step wrote, the clauses a filter checked, the values a task collected, an interview’s score and duration, a handoff’s booked time and host. It is capped at 1,000 characters.
  • Text is the full text of a message, up to 5,000 characters.
  • Internal is Yes for events the candidate never saw, such as a note to the recruiter or a workflow step.
  • Ended At is when a step that took time, or a task, ended.

​
Unanswered Questions

One row per question candidates asked that Alex could not answer.

​
Interview Q&A

One row per interview question and the candidate’s answer. Pick at least one job, and choose the columns to include.