CONNECT APP
Build with Greenhouse
Human Resources
- API key
MCP
Give your agent Greenhouse tools
Every Greenhouse action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Greenhouse account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "greenhouse",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Add Attachment to Candidate:
const result = await mcp.callTool({
name: "greenhouse-add-attachment-to-candidate",
arguments: {
userId: "User Id",
candidateId: "Candidate ID",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "greenhouse",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Add Attachment to Candidate:
result = await session.call_tool("greenhouse-add-attachment-to-candidate", {
"userId": "User Id",
"candidateId": "Candidate ID",
})API PROXY
Call the Greenhouse API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Greenhouse API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://harvest.greenhouse.io/v1/user_roles",
})
// Any allowed Greenhouse endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://harvest.greenhouse.io/v1/user_roles
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9oYXJ2ZXN0LmdyZWVuaG91c2UuaW8vdjEvdXNlcl9yb2xlcw?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Greenhouse actions from your backend
Connect a user's Greenhouse account once, then run Add Attachment to Candidate on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "greenhouse-add-attachment-to-candidate",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
greenhouse: { authProvisionId: "apn_xxxxxxx" },
userId: "User Id",
candidateId: "Candidate ID",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="greenhouse-add-attachment-to-candidate",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"greenhouse": {"authProvisionId": "apn_xxxxxxx"},
"userId": "User Id",
"candidateId": "Candidate ID",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "greenhouse-add-attachment-to-candidate",
"configured_props": {
"greenhouse": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User Id",
"candidateId": "Candidate ID"
}
}'TOOLS
Greenhouse actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Add Attachment to Candidate
actionAdds an attachment to a specific candidate or prospect. See the documentationWritev1.0.3 -
Create Candidate
actionCreates a new candidate entry in Greenhouse. See the documentationWritev0.0.2 -
Create Prospect
actionCreates a new prospect entry in Greenhouse. See the documentationWritev0.0.3 -
List Candidate ID Options
actionRetrieves available options for the Candidate ID field.Read-onlyv0.0.1 -
List Educations Options
actionRetrieves available options for the Educations field.Read-onlyv0.0.1 -
List Job IDs Options
actionRetrieves available options for the Job IDs field.Read-onlyv0.0.1 -
List User ID Options
actionRetrieves available options for the User ID field.Read-onlyv0.0.1
EVENTS
Greenhouse triggers
Event sources your backend can deploy for users and receive through a webhook.
-
New Candidate Application
triggerEmit new event when a candidate submits a new application.v0.0.1 -
New Candidate Watching
triggerEmit new event when a candidate's application or status changes.v0.0.1 -
New Scheduled Interview
triggerEmit new event when a new interview is scheduled within a specific time period.v0.0.1
MULTI-APP
Use Greenhouse with other popular apps
Most products don't stop at one integration. Pair Greenhouse with the other apps your users rely on, and ship use cases that span both.
- App slug
- greenhouse
- Authentication
- API key
- Categories
- Human Resources
- Actions
- 7
- Triggers
- 3
- API proxy
- Available