Create Candidate with Greenhouse API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Greenhouse, HTTP / Webhook and 2,400+ other apps remarkably fast.

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

Create Candidate with the Greenhouse API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Greenhouse action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Create Candidate action
1. Connect your Greenhouse account
2. Select a User Id
3. Configure First Name
4. Configure Last Name
5. Optional- Configure Company
6. Optional- Configure Title
7. Optional- Configure Phone Numbers
8. Optional- Configure Addressses
9. Optional- Configure Email Addresses
10. Optional- Configure Website Addresses
11. Optional- Configure Social Media Addresses
12. Optional- Configure Tags
13. Optional- Configure Custom Fields
14. Optional- Select a Recruiter Id
15. Optional- Configure Recruiter Email
16. Optional- Select a Coordinator Id
17. Optional- Configure Coordinator Email
18. Optional- Select one or more Educations
19. Optional- Configure Employments
20. Optional- Configure Activity Feed Notes
21. Select one or more Job Ids
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests (Payload Only) on HTTP / Webhook

Description:Get a URL and emit the HTTP body as an event on every request

Version:0.1.1

Key:http-new-requests-payload-only

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Create Candidate on Greenhouse

Description:Creates a new candidate entry in Greenhouse. [See the documentation](https://developers.greenhouse.io/harvest.html#post-add-candidate)

Version:0.0.1

Key:greenhouse-create-candidate

View on GitHub

Greenhouse Overview#

The Greenhouse API offers a powerful suite of tools for automating and enhancing the recruitment process. It allows you to programmatically access candidate information, job listings, scorecards, and scheduling details, which opens a myriad of possibilities for streamlining recruiting workflows. By leveraging the Greenhouse API on Pipedream, you can automate repetitive tasks, integrate with other HR systems, analyze recruitment data, and build custom event-driven workflows to improve the efficiency and effectiveness of your hiring process.

Action Code#

import { parseObject } from "../../common/utils.mjs";
import common from "../common/base-create.mjs";

export default {
  ...common,
  key: "greenhouse-create-candidate",
  name: "Create Candidate",
  description: "Creates a new candidate entry in Greenhouse. [See the documentation](https://developers.greenhouse.io/harvest.html#post-add-candidate)",
  version: "0.0.1",
  type: "action",
  props: {
    ...common.props,
    educations: {
      propDefinition: [
        common.props.greenhouse,
        "educations",
      ],
      optional: true,
    },
    employments: {
      type: "string[]",
      label: "Employments",
      description: "A list of employment record objects. **Format: {\"company_name\": \"Greenhouse\",\"title\": \"Engineer\",\"start_date\": \"2001-09-15T00:00:00.000Z\",\"end_date\": \"2004-05-15T00:00:00.000Z\"}**",
      optional: true,
    },
    activityFeedNotes: {
      type: "string[]",
      label: "Activity Feed Notes",
      description: "A list of activity feed objects. **Format: {\"body\": \"John Locke was moved into Recruiter Phone Screen for Accounting Manager on 03/27/2014 by Boone Carlyle\",\"visibility\": \"admin_only\"}. Visibility can be one of: admin_only, private or public**",
      optional: true,
    },
    jobIds: {
      propDefinition: [
        common.props.greenhouse,
        "jobIds",
      ],
    },
  },
  methods: {
    getData() {
      return {
        educations: parseObject(this.educations)?.map((item) => ({
          degree_id: item,
        })),
        employments: parseObject(this.employments),
        activity_feed_notes: parseObject(this.activityFeedNotes)?.map((item) => ({
          ...item,
          user_id: this.userId,
        })),
        applications: parseObject(this.jobIds)?.map((item) => ({
          job_id: item,
        })),
      };
    },
    getFunc() {
      return this.greenhouse.createCandidate;
    },
    getSummary(response) {
      return `Successfully created candidate with Id: ${response.id}!`;
    },
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Greenhouse	`greenhouse`	`app`	This component uses the Greenhouse app.
User Id	`userId`	`string`	Select a value from the drop down menu.
First Name	`firstName`	`string`	The person's first name.
Last Name	`lastName`	`string`	The person's last name.
Company	`company`	`string`	The person's company.
Title	`title`	`string`	The person's title.
Phone Numbers	`phoneNumbers`	`string[]`	A list of phone numbers. The phone number includes a plus sign (+), then country code, city code, and local phone number.
Addressses	`addressses`	`string[]`	A list of addresses.
Email Addresses	`emailAddresses`	`string[]`	A list of email addresses.
Website Addresses	`websiteAddresses`	`string[]`	A list of website addresses .
Social Media Addresses	`socialMediaAddresses`	`string[]`	A list of social media addresses.
Tags	`tags`	`string[]`	A list of tags as strings.
Custom Fields	`customFields`	`object`	An object containing new custom field values. The fields are the custom field Id.
Recruiter Id	`recruiterId`	`string`	Select a value from the drop down menu.
Recruiter Email	`recruiterEmail`	`string`	The email of the recruiter - either id or email must be present.
Coordinator Id	`coordinatorId`	`string`	Select a value from the drop down menu.
Coordinator Email	`coordinatorEmail`	`string`	The email of the coordinator - either id or email must be present.
Educations	`educations`	`string[]`	Select a value from the drop down menu.
Employments	`employments`	`string[]`	A list of employment record objects. Format: {"company_name": "Greenhouse","title": "Engineer","start_date": "2001-09-15T00:00:00.000Z","end_date": "2004-05-15T00:00:00.000Z"}
Activity Feed Notes	`activityFeedNotes`	`string[]`	A list of activity feed objects. Format: {"body": "John Locke was moved into Recruiter Phone Screen for Accounting Manager on 03/27/2014 by Boone Carlyle","visibility": "admin_only"}. Visibility can be one of: admin_only, private or public
Job Ids	`jobIds`	`string[]`	Select a value from the drop down menu.

Action Authentication#

Greenhouse uses API keys for authentication. When you connect your Greenhouse account, Pipedream securely stores the keys so you can easily authenticate to Greenhouse APIs in both code and no-code steps.

In order to create a Harvest API key, a user must be granted the “Can manage ALL organization’s API Credentials” in the “Developer permission” section. That user can then go Configure >> Dev Center >> API Credential Management as described in Harvest API Introduction.

About Greenhouse#

Talent Acquisition suite built for structured hiring

More Ways to Connect Greenhouse + HTTP / Webhook#

Other Popular Integrations#

Send any HTTP Request with HTTP / Webhook API on New Candidate Application from Greenhouse API

Greenhouse + HTTP / Webhook