Update Prospect with Klenty API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Update Prospect with the Klenty 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 Klenty 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 Update Prospect action
1. Connect your Klenty account
2. Select a List
3. Select a Prospect
4. Optional- Configure Email
5. Optional- Configure First Name
6. Optional- Configure Company
7. Optional- Configure Full Name
8. Optional- Configure Last Name
9. Optional- Configure Middle Name
10. Optional- Configure Account
11. Optional- Configure Department
12. Optional- Configure Company Domain
13. Optional- Configure Title
14. Optional- Configure Location
15. Optional- Configure Phone
16. Optional- Configure Twitter Id
17. Optional- Configure Company Phone
18. Optional- Configure Company Email
19. Optional- Configure Linkedin URL
20. Optional- Configure City
21. Optional- Configure Country
22. Optional- Select a New List
23. Optional- Configure Tags
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#

Update Prospect on Klenty

Description:Updates an existing prospect's information in Klenty. [See the documentation](https://www.klenty.com/developers)

Version:0.0.2

Key:klenty-update-prospect

View on GitHub

Klenty Overview#

The Klenty API enables automation of your sales engagement by integrating with Pipedream. With this API, you can sync leads, automate email campaigns, and manage tasks without manual intervention, creating a seamless sales workflow. By leveraging Pipedream's serverless execution model, you can set up custom triggers, actions, and data transformations between Klenty and various other apps.

Action Code#

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

export default {
  key: "klenty-update-prospect",
  name: "Update Prospect",
  description: "Updates an existing prospect's information in Klenty. [See the documentation](https://www.klenty.com/developers)",
  version: "0.0.2",
  annotations: {
    destructiveHint: true,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    klenty,
    list: {
      propDefinition: [
        klenty,
        "list",
      ],
      withLabel: true,
    },
    prospect: {
      propDefinition: [
        klenty,
        "prospect",
        ({ list }) => ({
          listName: list.label,
        }),
      ],
      withLabel: true,
    },
    email: {
      propDefinition: [
        klenty,
        "email",
      ],
      optional: true,
    },
    firstName: {
      propDefinition: [
        klenty,
        "firstName",
      ],
      optional: true,
    },
    company: {
      type: "string",
      label: "Company",
      description: "The Prospect's company name.",
      optional: true,
    },
    fullName: {
      type: "string",
      label: "Full Name",
      description: "The Prospect's full name.",
      optional: true,
    },
    lastName: {
      type: "string",
      label: "Last Name",
      description: "The Prospect's last name.",
      optional: true,
    },
    middleName: {
      type: "string",
      label: "Middle Name",
      description: "The Prospect's middle name.",
      optional: true,
    },
    account: {
      type: "string",
      label: "Account",
      description: "The Prospect's Account field.",
      optional: true,
    },
    department: {
      type: "string",
      label: "Department",
      description: "The Prospect's Department field.",
      optional: true,
    },
    companyDomain: {
      type: "string",
      label: "Company Domain",
      description: "The Prospect's Company Domain field.",
      optional: true,
    },
    title: {
      type: "string",
      label: "Title",
      description: "The Prospect's Title field.",
      optional: true,
    },
    location: {
      type: "string",
      label: "Location",
      description: "The Prospect's Location field.",
      optional: true,
    },
    phone: {
      type: "string",
      label: "Phone",
      description: "The Prospect's Phone field.",
      optional: true,
    },
    twitterId: {
      type: "string",
      label: "Twitter Id",
      description: "The Prospect's Twitter Id field.",
      optional: true,
    },
    companyPhone: {
      type: "string",
      label: "Company Phone",
      description: "The Prospect's Company Phone field.",
      optional: true,
    },
    companyEmail: {
      type: "string",
      label: "Company Email",
      description: "The Prospect's Company Email field.",
      optional: true,
    },
    linkedinURL: {
      type: "string",
      label: "Linkedin URL",
      description: "The Prospect's Linkedin URL field.",
      optional: true,
    },
    city: {
      type: "string",
      label: "City",
      description: "The Prospect's City field.",
      optional: true,
    },
    country: {
      type: "string",
      label: "Country",
      description: "The Prospect's Country field.",
      optional: true,
    },
    newList: {
      propDefinition: [
        klenty,
        "list",
      ],
      label: "New List",
      description: "The list where the prospect is going.",
      optional: true,
    },
    tags: {
      type: "string[]",
      label: "Tags",
      description: "A list of tags.",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.klenty.updateProspect({
      $,
      prospectEmail: this.prospect.label,
      data: {
        Email: this.email,
        FirstName: this.firstName,
        Company: this.company,
        FullName: this.fullName,
        LastName: this.lastName,
        MiddleName: this.middleName,
        Account: this.account,
        Department: this.department,
        CompanyDomain: this.companyDomain,
        Title: this.title,
        Location: this.location,
        Phone: this.phone,
        TwitterId: this.twitterId,
        CompanyPhone: this.companyPhone,
        CompanyEmail: this.companyEmail,
        LinkedinURL: this.linkedinURL,
        City: this.city,
        Country: this.country,
        List: this.newList || this.list,
        Tags: this.tags && this.tags.toString().replace(/,/g, "|"),
      },
    });

    $.export("$summary", "Updated prospect successfully!");
    return response;
  },
};

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
Klenty	`klenty`	`app`	This component uses the Klenty app.
List	`list`	`string`	Select a value from the drop down menu.
Prospect	`prospect`	`string`	Select a value from the drop down menu.
Email	`email`	`string`	The prospect's email address.
First Name	`firstName`	`string`	The prospect's first name.
Company	`company`	`string`	The Prospect's company name.
Full Name	`fullName`	`string`	The Prospect's full name.
Last Name	`lastName`	`string`	The Prospect's last name.
Middle Name	`middleName`	`string`	The Prospect's middle name.
Account	`account`	`string`	The Prospect's Account field.
Department	`department`	`string`	The Prospect's Department field.
Company Domain	`companyDomain`	`string`	The Prospect's Company Domain field.
Title	`title`	`string`	The Prospect's Title field.
Location	`location`	`string`	The Prospect's Location field.
Phone	`phone`	`string`	The Prospect's Phone field.
Twitter Id	`twitterId`	`string`	The Prospect's Twitter Id field.
Company Phone	`companyPhone`	`string`	The Prospect's Company Phone field.
Company Email	`companyEmail`	`string`	The Prospect's Company Email field.
Linkedin URL	`linkedinURL`	`string`	The Prospect's Linkedin URL field.
City	`city`	`string`	The Prospect's City field.
Country	`country`	`string`	The Prospect's Country field.
New List	`newList`	`string`	Select a value from the drop down menu.
Tags	`tags`	`string[]`	A list of tags.

Action Authentication#

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

To get your API Key go to Settings > Integrations > Klenty API Key.
For username, use your email address used to log into Klenty.

About Klenty#

The Sales Engagement Platform that can help you send personalized emails and automated follow-ups at scale.

More Ways to Connect Klenty + HTTP / Webhook#

Other Popular Integrations#

Add Prospect to List with Klenty API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Klenty