Create Time Tracking Report with Jibble API on New Action Created from Pushcut API

Pipedream makes it easy to connect APIs for Jibble, Pushcut and 2,400+ other apps remarkably fast.

Trigger workflow on

New Action Created from the Pushcut API

Next, do this

Create Time Tracking Report with the Jibble 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 Pushcut trigger and Jibble action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Action Created trigger
1. Connect your Pushcut account
2. Configure timer
3. Select a Type
Configure the Create Time Tracking Report action
1. Connect your Jibble account
2. Configure From
3. Configure To
4. Select a Group By
5. Select a Sub Group By
6. Optional- Select one or more Person IDs
7. Optional- Select one or more Project IDs
8. Optional- Select one or more Client IDs
9. Optional- Select one or more Activity IDs
10. Optional- Select one or more Group IDs
11. Optional- Select one or more Location IDs
12. Optional- Select one or more Schedule IDs
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 Action Created on Pushcut

Description:Emit new event when a new action is created.

Version:0.0.1

Key:pushcut-action-created

View on GitHub

Pushcut Overview#

The Pushcut API enables the automation of iOS notifications with custom actions, triggering events based on various conditions. On Pipedream, you can harness this functionality to create intricate workflows, combining Pushcut notifications with a multitude of services to act based on data from APIs, schedules, or other apps. Think of Pushcut as a bridge between the real world and your digital tasks, letting you know when to act and offering shortcuts to execute specific automations directly from your iOS devices.

Trigger Code#

import pushcut from "../../pushcut.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "pushcut-action-created",
  name: "New Action Created",
  description: "Emit new event when a new action is created.",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    pushcut,
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    actionType: {
      type: "string",
      label: "Type",
      description: "Type of new action to watch for",
      options: [
        "shortcut",
        "homekit",
      ],
    },
  },
  methods: {
    generateMeta(action) {
      return {
        id: action.id,
        summary: `${action.id}`,
        ts: Date.now(),
      };
    },
  },
  async run() {
    const actions = this.actionType === "shortcut"
      ? await this.pushcut.listShortcuts()
      : await this.pushcut.listHomekitScenes();
    for (const action of actions) {
      const meta = this.generateMeta(action);
      this.$emit(action, meta);
    }
  },
};

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
Pushcut	`pushcut`	`app`	This component uses the Pushcut app.
	`timer`	`$.interface.timer`
Type	`actionType`	`string`	Select a value from the drop down menu:`shortcuthomekit`

Trigger Authentication#

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

To generate your API Key,

Navigate to your Pushcut account and sign in
Go to “Account”
Click the “Add API Key” button

About Pushcut#

Automate Smart Home Workflow

Action#

Create Time Tracking Report on Jibble

Description:This is generic endpoint for getting time tracking reports. [See the documentation](https://docs.api.jibble.io/#3115af1a-24a6-4d19-a7e7-08d8c173bb85).

Version:0.0.1

Key:jibble-create-time-tracking-report

View on GitHub

Jibble Overview#

The Jibble API provides programmatic access to Jibble's time and attendance tracking features, allowing you to manage team timesheets, attendance, and work reports. Integrating the Jibble API with Pipedream opens up possibilities for automating routine tasks, syncing data across platforms, and triggering actions based on time tracking events. You can create workflows that respond to specific triggers like clock-ins and clock-outs, or schedule regular data syncs to maintain up-to-date records in other systems.

Action Code#

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

export default {
  name: "Create Time Tracking Report",
  description: "This is generic endpoint for getting time tracking reports. [See the documentation](https://docs.api.jibble.io/#3115af1a-24a6-4d19-a7e7-08d8c173bb85).",
  key: "jibble-create-time-tracking-report",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    from: {
      label: "From",
      type: "string",
      description: "The start date of the report. Format: YYYY-MM-DDTHH:mm:ssZ. Example: `2021-12-20T08:00:00.000Z`",
    },
    to: {
      label: "To",
      type: "string",
      description: "The end date of the report. Format: YYYY-MM-DDTHH:mm:ssZ. Example: `2021-12-20T08:00:00.000Z`",
    },
    groupBy: {
      label: "Group By",
      type: "string",
      description: "The field to group the report by.",
      options: options.GROUP_BY,
    },
    subGroupBy: {
      label: "Sub Group By",
      type: "string",
      description: "The field to sub group the report by.",
      options: options.SUB_GROUP_BY,
    },
    personIds: {
      propDefinition: [
        app,
        "personId",
      ],
      label: "Person IDs",
      type: "string[]",
      description: "The ID of the persons to create the report.",
      optional: true,
    },
    projectIds: {
      propDefinition: [
        app,
        "projectId",
      ],
      label: "Project IDs",
      type: "string[]",
      description: "The ID of the projects to create the report.",
      optional: true,
    },
    clientIds: {
      propDefinition: [
        app,
        "clientId",
      ],
      label: "Client IDs",
      type: "string[]",
      description: "The ID of the clients to create the report.",
      optional: true,
    },
    activityIds: {
      propDefinition: [
        app,
        "activityId",
      ],
      label: "Activity IDs",
      type: "string[]",
      description: "The ID of the activities to create the report.",
      optional: true,
    },
    groupIds: {
      propDefinition: [
        app,
        "groupId",
      ],
      label: "Group IDs",
      type: "string[]",
      description: "The ID of the groups to create the report.",
      optional: true,
    },
    locationIds: {
      propDefinition: [
        app,
        "locationId",
      ],
      label: "Location IDs",
      type: "string[]",
      description: "The ID of the locations to create the report.",
      optional: true,
    },
    scheduleIds: {
      propDefinition: [
        app,
        "scheduleId",
      ],
      label: "Schedule IDs",
      type: "string[]",
      description: "The ID of the schedules to create the report.",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      app,
      ...data
    } = this;
    const res = await app.createTimeTrackingReport(data, $);
    $.export("summary", "Time tracking successfully created.");
    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
Jibble	`app`	`app`	This component uses the Jibble app.
From	`from`	`string`	The start date of the report. Format: YYYY-MM-DDTHH:mm:ssZ. Example: `2021-12-20T08:00:00.000Z`
To	`to`	`string`	The end date of the report. Format: YYYY-MM-DDTHH:mm:ssZ. Example: `2021-12-20T08:00:00.000Z`
Group By	`groupBy`	`string`	Select a value from the drop down menu:`DateMemberClientProjectActivity`
Sub Group By	`subGroupBy`	`string`	Select a value from the drop down menu:`NoneDateMemberClientProjectActivity`
Person IDs	`personIds`	`string[]`	Select a value from the drop down menu.
Project IDs	`projectIds`	`string[]`	Select a value from the drop down menu.
Client IDs	`clientIds`	`string[]`	Select a value from the drop down menu.
Activity IDs	`activityIds`	`string[]`	Select a value from the drop down menu.
Group IDs	`groupIds`	`string[]`	Select a value from the drop down menu.
Location IDs	`locationIds`	`string[]`	Select a value from the drop down menu.
Schedule IDs	`scheduleIds`	`string[]`	Select a value from the drop down menu.

Action Authentication#

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

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