List Time Entries with Clockify API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

List Time Entries with the Clockify 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 Clockify 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 List Time Entries action
1. Connect your Clockify account
2. Select a Workspace
3. Select a User
4. Optional- Configure Description
5. Optional- Configure Start
6. Optional- Configure End
7. Optional- Select a Project
8. Optional- Select a Task
9. Optional- Select one or more Tags
10. Optional- Configure Project Required
11. Optional- Configure Task Required
12. Optional- Configure Hydrated
13. Optional- Configure In Progress
14. Optional- Configure Page
15. Optional- Configure Page Size
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#

List Time Entries on Clockify

Description:List all time entries in a Clockify workspace. [See the documentation](https://docs.clockify.me/#tag/Time-entry/operation/getTimeEntries)

Version:0.0.1

Key:clockify-list-time-entries

View on GitHub

Clockify Overview#

Clockify is a time tracking and timesheet app that provides a straightforward way to track work hours across projects. With the Clockify API on Pipedream, you can automate time tracking, create detailed reports, manage projects, and sync timesheet data with other apps. Using Pipedream, you can create workflows that trigger on events in Clockify or other apps, process the data, and perform actions like logging time automatically, sending notifications, or creating invoices based on tracked time.

Action Code#

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

export default {
  key: "clockify-list-time-entries",
  name: "List Time Entries",
  description: "List all time entries in a Clockify workspace. [See the documentation](https://docs.clockify.me/#tag/Time-entry/operation/getTimeEntries)",
  version: "0.0.1",
  type: "action",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  props: {
    clockify,
    workspaceId: {
      propDefinition: [
        clockify,
        "workspaceId",
      ],
    },
    userId: {
      propDefinition: [
        clockify,
        "memberIds",
        (c) => ({
          workspaceId: c.workspaceId,
        }),
      ],
      type: "string",
      label: "User",
      description: "Identifier of a user",
    },
    description: {
      type: "string",
      label: "Description",
      description: "Represents term for searching time entries by description",
      optional: true,
    },
    start: {
      type: "string",
      label: "Start",
      description: "Represents start date in yyyy-MM-ddThh:mm:ssZ format. Example: `2020-01-01T00:00:00Z`",
      optional: true,
    },
    end: {
      type: "string",
      label: "End",
      description: "Represents end date in yyyy-MM-ddThh:mm:ssZ format. Example: `2020-01-01T00:00:00Z`",
      optional: true,
    },
    projectId: {
      propDefinition: [
        clockify,
        "projectId",
        (c) => ({
          workspaceId: c.workspaceId,
        }),
      ],
      optional: true,
    },
    taskId: {
      propDefinition: [
        clockify,
        "taskId",
        (c) => ({
          workspaceId: c.workspaceId,
          projectId: c.projectId,
        }),
      ],
      optional: true,
    },
    tagIds: {
      propDefinition: [
        clockify,
        "tagIds",
        (c) => ({
          workspaceId: c.workspaceId,
        }),
      ],
      optional: true,
    },
    projectRequired: {
      type: "boolean",
      label: "Project Required",
      description: "Flag to set whether to only get time entries which have a project",
      optional: true,
    },
    taskRequired: {
      type: "boolean",
      label: "Task Required",
      description: "Flag to set whether to only get time entries which have a task",
      optional: true,
    },
    hydrated: {
      propDefinition: [
        clockify,
        "hydrated",
      ],
    },
    inProgress: {
      type: "boolean",
      label: "In Progress",
      description: "Flag to set whether to filter only in progress time entries",
      optional: true,
    },
    page: {
      propDefinition: [
        clockify,
        "page",
      ],
    },
    pageSize: {
      propDefinition: [
        clockify,
        "pageSize",
      ],
    },
  },
  async run({ $ }) {
    const response = await this.clockify.listTimeEntries({
      $,
      workspaceId: this.workspaceId,
      userId: this.userId,
      params: {
        "description": this.description,
        "start": this.start,
        "end": this.end,
        "project": this.projectId,
        "task": this.taskId,
        "tags": this.tagIds,
        "project-required": this.projectRequired,
        "task-required": this.taskRequired,
        "hydrated": this.hydrated,
        "in-progress": this.inProgress,
        "page": this.page,
        "page-size": this.pageSize,
      },
    });

    $.export("$summary", `Successfully listed ${response.length} time entries`);

    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
Clockify	`clockify`	`app`	This component uses the Clockify app.
Workspace	`workspaceId`	`string`	Select a value from the drop down menu.
User	`userId`	`string`	Select a value from the drop down menu.
Description	`description`	`string`	Represents term for searching time entries by description
Start	`start`	`string`	Represents start date in yyyy-MM-ddThh:mm:ssZ format. Example: `2020-01-01T00:00:00Z`
End	`end`	`string`	Represents end date in yyyy-MM-ddThh:mm:ssZ format. Example: `2020-01-01T00:00:00Z`
Project	`projectId`	`string`	Select a value from the drop down menu.
Task	`taskId`	`string`	Select a value from the drop down menu.
Tags	`tagIds`	`string[]`	Select a value from the drop down menu.
Project Required	`projectRequired`	`boolean`	Flag to set whether to only get time entries which have a project
Task Required	`taskRequired`	`boolean`	Flag to set whether to only get time entries which have a task
Hydrated	`hydrated`	`boolean`	If set to `true`, you'll get a hydrated response with additional information
In Progress	`inProgress`	`boolean`	Flag to set whether to filter only in progress time entries
Page	`page`	`integer`	The page number to return. Default is `1`
Page Size	`pageSize`	`integer`	The number of results to return. Default is `100`

Action Authentication#

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

About Clockify#

100% Free Time Tracking Software

More Ways to Connect Clockify + HTTP / Webhook#

Other Popular Integrations#

Add Members To Project with Clockify API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Clockify

Try it

Add Members To Project with Clockify API on New Requests from HTTP / Webhook API

HTTP / Webhook + Clockify

Try it

Add Task To Project with Clockify API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Clockify

Try it

Add Task To Project with Clockify API on New Requests from HTTP / Webhook API

HTTP / Webhook + Clockify

Try it

Create Project with Clockify API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Clockify

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