Create Leave Request with Kenjo API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Create Leave Request with the Kenjo 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 Kenjo 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 Create Leave Request action
1. Connect your Kenjo account
2. Select a Employee ID
3. Select a Time Off Type ID
4. Configure From
5. Configure To
6. Optional- Select a Part of Day From
7. Optional- Select a Part of Day To
8. Optional- Configure Description
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#

Create Leave Request on Kenjo

Description:Creates a new leave request in Kenjo. [See the documentation](https://kenjo.readme.io/reference/post_time-off-requests).

Version:0.0.1

Key:kenjo-create-leave-request

View on GitHub

Action Code#

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

export default {
  key: "kenjo-create-leave-request",
  name: "Create Leave Request",
  description: "Creates a new leave request in Kenjo. [See the documentation](https://kenjo.readme.io/reference/post_time-off-requests).",
  version: "0.0.1",
  type: "action",
  props: {
    kenjo,
    employeeId: {
      propDefinition: [
        kenjo,
        "employeeId",
      ],
    },
    timeOffTypeId: {
      propDefinition: [
        kenjo,
        "timeOffTypeId",
      ],
    },
    from: {
      type: "string",
      label: "From",
      description: "The starting date of the time-off request in format `YYYY-MM-DD`",
    },
    to: {
      type: "string",
      label: "To",
      description: "The ending date of the time-off request in format `YYYY-MM-DD`",
    },
    partOfDayFrom: {
      type: "string",
      label: "Part of Day From",
      description: "The duration of the from date. 'StartOfDay' means that the from date is the entire day. 'HalfOfDay' means that the request starts to apply in the middle of the from day. If not specified, the default value will be 'StartOfDay'.",
      options: [
        "StartOfDay",
        "HalfOfDay",
      ],
      optional: true,
    },
    partOfDayTo: {
      type: "string",
      label: "Part of Day To",
      description: "The duration of the to date. 'EndOfDay' means that the to date is the entire day. 'HalfOfDay' means the request starts to apply in the middle of the to day. If not specified, the default value will be 'EndOfDay'.",
      options: [
        "HalfOfDay",
        "EndOfDay",
      ],
      optional: true,
    },
    description: {
      type: "string",
      label: "Description",
      description: "The description of the time-off request",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.kenjo.createLeaveRequest({
      $,
      data: {
        _userId: this.employeeId,
        _timeOffTypeId: this.timeOffTypeId,
        from: this.from,
        to: this.to,
        partOfDayFrom: this.partOfDayFrom,
        partOfDayTo: this.partOfDayTo,
        description: this.description,
      },
    });
    $.export("$summary", `Successfully created leave request with ID: ${response._id}`);
    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
Kenjo	`kenjo`	`app`	This component uses the Kenjo app.
Employee ID	`employeeId`	`string`	Select a value from the drop down menu.
Time Off Type ID	`timeOffTypeId`	`string`	Select a value from the drop down menu.
From	`from`	`string`	The starting date of the time-off request in format `YYYY-MM-DD`
To	`to`	`string`	The ending date of the time-off request in format `YYYY-MM-DD`
Part of Day From	`partOfDayFrom`	`string`	Select a value from the drop down menu:`StartOfDayHalfOfDay`
Part of Day To	`partOfDayTo`	`string`	Select a value from the drop down menu:`HalfOfDayEndOfDay`
Description	`description`	`string`	The description of the time-off request

Action Authentication#

Kenjo uses OAuth authentication. When you connect your Kenjo account, Pipedream will open a popup window where you can sign into Kenjo and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Kenjo API.

Pipedream requests the following authorization scopes when you connect your account:

About Kenjo#

HR Software for Deskless Teams

More Ways to Connect Kenjo + HTTP / Webhook#

Other Popular Integrations#

Create Attendance Entry with Kenjo API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Kenjo