# Greenhouse: Application History

## Description

* If enabled, table capturing the history of applications as they advance through job stages.

## Supported Data Sources

* <img src="https://fivetran.com/integrations/greenhouse/resources/greenhouse.svg" alt="" data-size="line"> Greenhouse

## Columns

| Type     | Name                          | Description                                                                        |
| -------- | ----------------------------- | ---------------------------------------------------------------------------------- |
| INTEGER  | application\_id               | Foreign key referencing the APPLICATION that was updated.                          |
| INTEGER  | new\_stage\_id                | Foreign key referencing the JOB\_STAGE that the application was advanced to.       |
| STRING   | new\_status                   | Status of the application as of this updated.                                      |
| DATETIME | valid\_from                   | Timestamp of when the application was advanced.                                    |
| DATETIME | valid\_until                  | Timestamp of when the application was moved to a further stage.                    |
| STRING   | new\_stage                    | Name of the newly advanced job stage.                                              |
| STRING   | full\_name                    | Full name of the applicant.                                                        |
| STRING   | current\_status               | Current status of the application. One of - active, rejected, hired.               |
| STRING   | recruiter\_name               | Full name of the application's recruiter.                                          |
| STRING   | hiring\_managers              | Hiring manager(s) for the pursued job.                                             |
| STRING   | sourced\_from                 | Where the application was sourced from.                                            |
| STRING   | sourced\_from\_type           | The category of source that the application came from.                             |
| STRING   | job\_title                    | Title of the job role the candidate is applying for.                               |
| INTEGER  | job\_id                       | Foreign key referencing the JOB being applied for.                                 |
| INTEGER  | candidate\_id                 | Foreign key referencing the unique CANDIDATE associated with this application.     |
| INTEGER  | days\_in\_stage               | Number of calendar days the application spent in this stage.                       |
| STRING   | job\_departments              | Semicolon-separated list of the departments that the job is listed under.          |
| STRING   | job\_parent\_departments      | Semicolon-separated list of the *parent* departments that the job is listed under. |
| STRING   | job\_offices                  | Semicolon-separated list of the offices that the job is listed under.              |
| STRING   | candidate\_gender             | Description of the applicant's gender identity.                                    |
| STRING   | candidate\_disability\_status | Description of the applicant's disability status.                                  |
| STRING   | candidate\_race               | Description of applicant's provided race.                                          |
| STRING   | candidate\_veteran\_status    | Description of the applicant's veteran status.                                     |
| INTEGER  | count\_activities\_in\_stage  | Total count of the activities performed while the candidate was in this stage.     |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://endash-guidance-docs.gitbook.io/cigro-data-templates/data-model-templates/greenhouse-application-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.