Search Single Contact with Lusha API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Lusha, HTTP / Webhook and 3,000+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Search Single Contact with the Lusha 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 Lusha 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
6. Optional- Configure Summary
Configure the Search Single Contact action
1. Connect your Lusha account
2. Optional- Configure First Name
3. Optional- Configure Last Name
4. Optional- Configure Company Name
5. Optional- Configure Company Domain
6. Optional- Configure Email
7. Optional- Configure LinkedIn URL
8. Optional- Configure Refresh Job Info
9. Optional- Select a Filter By
10. Optional- Configure Reveal Emails
11. Optional- Configure Reveal Phones
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.2

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.2",
  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,
    summary: {
      propDefinition: [
        http,
        "summary",
      ],
    },
  },
  async run(event) {
    const summary = this.summary
      ? this.http.interpolateSummary(this.summary, event)
      : `${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.
Summary	`summary`	`string`	An optional summary. This will be emitted as the `summary` metadata for the event. Use dot notation to reference nested values. Example: `New item with ID: ${body.id}` or `User: ${body.user.name}`

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#

Search Single Contact on Lusha

Description:Search for a single contact using various filters. [See the documentation](https://docs.lusha.com/apis/index2/person/personcontroller_searchsinglecontact)

Version:0.0.1

Key:lusha-single-contact-search

View on GitHub

Lusha Overview#

The Lusha API provides programmatic access to Lusha's rich database, allowing you to retrieve business profiles and contact information. By integrating Lusha with Pipedream, you can automate the enrichment of lead data, sync contact information with your CRM, and enhance your sales or recruitment processes. The API enables you to pull details such as phone numbers, email addresses, and company data, turning them into actionable insights within your business workflows.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import { FILTER_BY_OPTIONS } from "../../common/constants.mjs";
import lusha from "../../lusha.app.mjs";

export default {
  key: "lusha-single-contact-search",
  name: "Search Single Contact",
  description: "Search for a single contact using various filters. [See the documentation](https://docs.lusha.com/apis/index2/person/personcontroller_searchsinglecontact)",
  version: "0.0.1",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    lusha,
    firstName: {
      type: "string",
      label: "First Name",
      description: "First name of the person",
      optional: true,
    },
    lastName: {
      type: "string",
      label: "Last Name",
      description: "Last name of the person",
      optional: true,
    },
    companyName: {
      type: "string",
      label: "Company Name",
      description: "The name of the company the person works at",
      optional: true,
    },
    companyDomain: {
      type: "string",
      label: "Company Domain",
      description: "The domain name of the company",
      optional: true,
    },
    email: {
      type: "string",
      label: "Email",
      description: "The email address of the person",
      optional: true,
    },
    linkedinUrl: {
      type: "string",
      label: "LinkedIn URL",
      description: "The LinkedIn URL of the person",
      optional: true,
    },
    refreshJobInfo: {
      type: "boolean",
      label: "Refresh Job Info",
      description: "Set to true to refresh and update the job details for the person. This ensures that outdated job information is replaced with the most recent data",
      optional: true,
    },
    filterBy: {
      type: "string",
      label: "Filter By",
      description: "Filters results based on specific contact details. By default, results will include contacts with at least one contact detail",
      optional: true,
      options: FILTER_BY_OPTIONS,
    },
    revealEmails: {
      type: "boolean",
      label: "Reveal Emails",
      description: "Whether to reveal email addresses in the response",
      optional: true,
    },
    revealPhones: {
      type: "boolean",
      label: "Reveal Phones",
      description: "Whether to reveal phone numbers in the response",
      optional: true,
    },
  },
  async run({ $ }) {
    try {
      const response = await this.lusha.searchSingleContact({
        $,
        params: {
          firstName: this.firstName,
          lastName: this.lastName,
          companyName: this.companyName,
          companyDomain: this.companyDomain,
          email: this.email,
          linkedinUrl: this.linkedinUrl,
          refreshJobInfo: this.refreshJobInfo,
          filterBy: this.filterBy,
          revealEmails: this.revealEmails,
          revealPhones: this.revealPhones,
        },
      });
      let summary = "";
      if (response.contact?.error?.name) {

        if (response.contact.error.name !== "EMPTY_DATA") {
          throw new Error(response.contact.error.message || response.contact.error.name);
        }
        summary = "No contact found";
      }

      if (response.contact.data?.personId) {
        summary = `Successfully found a contact with ID: ${response.contact.data.personId}`;
      }
      $.export("$summary", summary);

      return response.contact.data;
    } catch ({ response }) {
      throw new ConfigurationError(response?.data?.message);
    }
  },
};

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
Lusha	`lusha`	`app`	This component uses the Lusha app.
First Name	`firstName`	`string`	First name of the person
Last Name	`lastName`	`string`	Last name of the person
Company Name	`companyName`	`string`	The name of the company the person works at
Company Domain	`companyDomain`	`string`	The domain name of the company
Email	`email`	`string`	The email address of the person
LinkedIn URL	`linkedinUrl`	`string`	The LinkedIn URL of the person
Refresh Job Info	`refreshJobInfo`	`boolean`	Set to true to refresh and update the job details for the person. This ensures that outdated job information is replaced with the most recent data
Filter By	`filterBy`	`string`	Select a value from the drop down menu:`{ "label": "Only return contacts with phone numbers", "value": "phoneNumbers" }{ "label": "Only return contacts with email addresses", "value": "emailAddresses" }`
Reveal Emails	`revealEmails`	`boolean`	Whether to reveal email addresses in the response
Reveal Phones	`revealPhones`	`boolean`	Whether to reveal phone numbers in the response

Action Authentication#

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

Requests are authenticated by your API key. See docs

About Lusha#

B2B Lead Enrichment in a Click

More Ways to Connect Lusha + HTTP / Webhook#

Other Popular Integrations#

Find Company with Lusha API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Lusha

Try it

Find Company with Lusha API on New Requests from HTTP / Webhook API

HTTP / Webhook + Lusha

Try it

Find Contact with Lusha API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Lusha

Try it

Find Contact with Lusha API on New Requests from HTTP / Webhook API

HTTP / Webhook + Lusha

Try it

Find Company with Lusha API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Lusha

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