# Lever: Opportunity Stage History ## Description * Table capturing each stage that an opportunity has advanced too. ## Supported Data Sources * Lever ## Columns | Type | Name | Description | | -------- | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | STRING | opportunity\_id | Foreign key referencing the id of the OPPORTUNITY. | | STRING | opportunity\_contact\_name | Contact full name. | | DATETIME | valid\_from | Timestamp of when the opportunity was changed to this stage. | | DATETIME | valid\_ending\_at | Timestamp of when the opportunity left this stage (either by advancing or being archived). | | STRING | stage | Name of the stage. | | STRING | stage\_id | Foreign key referencing the STAGE that the opportunity was changed to. | | INTEGER | stage\_index\_in\_pipeline | The index of the stage in the pipeline at the time the stage change occurred. | | STRING | updater\_user\_name | Full name of the user who updated the candidate to this stage. | | STRING | archive\_reason | Reason that the opportunity was ultimately archived. | | STRING | job\_title | Title of the job posting role.Title of the job posting role. | | INTEGER | job\_department | Tag for the department to which the job posting's team belongs, if present. | | STRING | job\_location | Tag for job position location. | | STRING | job\_team | Tag for the team to which the job posting belongs (a sub-category of department). | | STRING | application\_type | Type of the application. An application can be of type referral, user, or posting. Applications of type referral are created when a user refers a candidate for a job posting. Applications have type user when they are applied manually to a posting in Lever. Applications have type posting when a candidate applies to a job posting through your company's jobs page. | | STRING | application\_sources | Aggregated list of the channels through which this opportunity was sourced. | | STRING | hiring\_manager\_name | Full name of the hiring manager of role for which the opportunity applied. | | STRING | opportunity\_owner\_name | Full name of the user who owns the opportunity in Lever. | | INTEGER | days\_in\_stage | The number of calendar days in which the opportunity has remained in this stage (ie until they advanced or were archived). | --- # 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/lever-opportunity-stage-history.md?ask= ``` 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.