More dollars and less work with
our ApplicantStack integration
The Activity object is used to represent an activity for a candidate performed by a user.
The Application Object is used to represent a candidate's journey through a particular Job's recruiting process. If a Candidate applies for multiple Jobs, there will be a separate Application for each Job if the third-party integration allows it.
The Candidate object is used to represent profile information about a given Candidate. Because it is specific to a Candidate, this information stays constant across applications.
The Job object can be used to track any jobs that are currently or will be open/closed for applications.
The JobInterviewStage object is used to represent a particular recruiting stage for an Application. A given Application typically has the JobInterviewStage object represented in the current_stage field.
The Office object is used to represent an office within a company. A given Job has the Office ID in its offices field.
The RejectReason object is used to represent a reason for rejecting an application. These can typically be configured within an ATS system.
Stop diverting your engineers to yet another integration and let them get back to work.
Manage your simplified integration issues in a single pane. No therapist required.
Launch integrations in days, not quarters. Your sales team will thank you.