reject_application
Facts
Connectors.GreenhouseRecruiting.functions.RejectApplicationGreenhouse RecruitingInput parameters
Required input parameters
application_idintegerRequiredThe ID of the application to be rejected
9876543candidate_idintegerRequiredThe ID of the candidate for whom an application is being rejected
12345Optional input parameters
notesstringOptionalAny notes you want to associate with this rejection action
rejection_reason_idintegerOptionalThe ID of the application rejection reason, based on your defined rejection reasons in Greenhouse Recruiting
Output parameters
Optional output parameters
candidate_idintegerOptionalCandidate ID
idintegerOptionalApplication ID
statusstringOptionalStatus
Authentication
Required workspace environment variables
This connector relies on workspace environment variables for authentication.
Before adding this connector to a workflow, the following workspace environment variables need to be configured by a workspace admin:
GREENHOUSE_RECRUITING_SYSTEM_USER_IDGREENHOUSE_RECRUITING_API_KEY
Admins can set workspace environment variables for connectors that require them from within Workflow Builder, in the Manage Integrations section.
To open the Manage Integrations section, open Workflow Builder and access the additional options menu to the right of the Create Workflow button.
Usage info
First, import Connectors from deno-slack-hub into your project's import_map.json file, like this:
{
"imports": {
"deno-slack-hub/": "https://deno.land/x/deno_slack_hub@2.2.0/",
"deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.14.2/",
"deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/"
}
}
Next, import Connectors at the top of your workflow's definition file:
import { Connectors } from "deno-slack-hub/mod.ts";
Finally, add the connector as a step in your workflow just like you would a Slack function.
SomeWorkflow.addStep(
Connectors.GreenhouseRecruiting.functions.RejectApplication, {
//...
🧙🏼 Your admin may need to approve the connector first. If your workspace has been configured to only allow admin-approved apps, the CLI will prompt you to send an admin approval request the first time you try to use a connector that hasn't been approved by an admin yet. While waiting for admin approval, the CLI may report an error like this:
Workflow function X is referring to an unknown step output parameter YYou can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.