Find Contacts with Clearbit API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Find Contacts with the Clearbit 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 Clearbit 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 trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Find Contacts action
1. Connect your Clearbit account
2. Configure Domain
3. Optional- Configure Title
4. Optional- Configure Email
5. Optional- Configure Role
6. Optional- Configure Seniority
7. Optional- Configure City
8. Optional- Configure State
9. Optional- Configure Country
10. Optional- Configure Name
11. Configure Query
12. Optional- Configure Max Results
13. Optional- Select a Suppression
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 on HTTP / Webhook

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Version:0.1.1

Key:http-new-requests

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
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
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#

Find Contacts on Clearbit

Description:Find people who work at a specific company. [See the docs here](https://dashboard.clearbit.com/docs#prospector-api)

Version:0.0.1

Key:clearbit-find-contacts

View on GitHub

Clearbit Overview#

Clearbit API offers robust data enrichment capabilities, allowing you to seamlessly integrate comprehensive business intelligence into your applications. By leveraging Clearbit, you can append real-time insights to your leads, automate personalized outreach, and gain a deeper understanding of your customers. With insights ranging from company profiles, contact details, to employment information, the possibilities to enhance your marketing, sales, and customer support efforts are vast.

Action Code#

import app from "../../clearbit.app.mjs";
import options from "../../common/options.mjs";

export default {
  key: "clearbit-find-contacts",
  name: "Find Contacts",
  description: "Find people who work at a specific company. [See the docs here](https://dashboard.clearbit.com/docs#prospector-api)",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    domain: {
      propDefinition: [
        app,
        "domain",
      ],
      description: "Domain of the company you want to search against.",
    },
    title: {
      label: "Title",
      type: "string",
      description: "Job title to filter by",
      optional: true,
    },
    email: {
      propDefinition: [
        app,
        "email",
      ],
      description: "Email to filter by",
      optional: true,
    },
    role: {
      label: "Role",
      type: "string",
      description: "Employment Role.",
      optional: true,
    },
    seniority: {
      label: "Seniority",
      type: "string",
      description: "Employment Seniority",
      optional: true,
    },
    city: {
      label: "City",
      type: "string",
      description: "City to filter by.",
      optional: true,
    },
    state: {
      label: "State",
      type: "string",
      description: "State to filter by.",
      optional: true,
    },
    country: {
      label: "Country",
      type: "string",
      description: "Country to filter by.",
      optional: true,
    },
    name: {
      label: "Name",
      type: "string",
      description: "Name of an individual to filter by.",
      optional: true,
    },
    query: {
      propDefinition: [
        app,
        "query",
      ],
    },
    maxResults: {
      propDefinition: [
        app,
        "maxResults",
      ],
    },
    suppression: {
      label: "Suppression",
      type: "string",
      description: "Set to eu to exclude records with country data in the EU. Set to eu_strict to exclude records with country data in the EU or with null country data.",
      optional: true,
      options: options.SUPPRESSION,
    },
  },
  async run({ $ }) {
    const params = {
      domain: this.domain,
      title: this.title,
      email: this.email,
      role: this.role,
      seniority: this.seniority,
      city: this.city,
      state: this.state,
      country: this.country,
      name: this.name,
      query: this.query,
      suppression: this.suppression,
    };
    const res = await this.app.paginate(
      $,
      this.maxResults || 100,
      this.app.findContacts,
      params,
    );
    $.export("$summary", `Found ${res.length} contact(s)`);
    return res;
  },
};

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
Clearbit	`app`	`app`	This component uses the Clearbit app.
Domain	`domain`	`string`	Domain of the company you want to search against.
Title	`title`	`string`	Job title to filter by
Email	`email`	`string`	Email to filter by
Role	`role`	`string`	Employment Role.
Seniority	`seniority`	`string`	Employment Seniority
City	`city`	`string`	City to filter by.
State	`state`	`string`	State to filter by.
Country	`country`	`string`	Country to filter by.
Name	`name`	`string`	Name of an individual to filter by.
Query	`query`	`string`	Search query string.
Max Results	`maxResults`	`integer`	Maximum results to be fetched. Defaults to `100`.
Suppression	`suppression`	`string`	Select a value from the drop down menu:`eueu_strict`

Action Authentication#

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

Copy your "secret API key" from your Clearbit account here and paste it below.

About Clearbit#

B2B Lead Data Enrichment, Qualification & Scoring

More Ways to Connect Clearbit + HTTP / Webhook#

Other Popular Integrations#

Company Name to Domain with Clearbit API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Clearbit

Try it

Company Name to Domain with Clearbit API on New Requests from HTTP / Webhook API

HTTP / Webhook + Clearbit

Try it

Domain lookup with Clearbit API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Clearbit

Try it

Domain lookup with Clearbit API on New Requests from HTTP / Webhook API

HTTP / Webhook + Clearbit

Try it

Find Companies with Clearbit API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Clearbit

Try it

Popular Triggers#

New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Try it

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

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

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it