Add or update multiple records with Data Stores API on New Time Entry from TimeCamp API

Pipedream makes it easy to connect APIs for Data Stores, TimeCamp and 2,400+ other apps remarkably fast.

Trigger workflow on

New Time Entry from the TimeCamp API

Next, do this

Add or update multiple records with the Data Stores 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 TimeCamp trigger and Data Stores action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Time Entry trigger
1. Connect your TimeCamp account
2. Configure timer
Configure the Add or update multiple records action
1. Connect your Data Stores account
2. Configure Data Store
3. Configure Data
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 Time Entry on TimeCamp

Description:Emit new event on each created time entry.

Version:0.0.3

Key:timecamp-new-time-entry

View on GitHub

TimeCamp Overview#

TimeCamp's API unlocks the potential to automate and integrate time tracking data with a myriad of services and platforms. By leveraging Pipedream's capabilities, you can create custom workflows that respond to events in TimeCamp, such as new time entries, projects, or tasks. These workflows can then trigger actions in other apps, or even process and analyze time tracking data to provide insights and streamline operations.

Trigger Code#

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

export default {
  name: "New Time Entry",
  version: "0.0.3",
  key: "timecamp-new-time-entry",
  description: "Emit new event on each created time entry.",
  type: "source",
  dedupe: "unique",
  props: {
    timecamp,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      static: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  methods: {
    _getLastSyncDate() {
      return this.db.get("lastSyncDate");
    },
    _setLastSyncDate(lastSyncDate) {
      return this.db.set("lastSyncDate", lastSyncDate);
    },
    emitEvent(data) {
      this.$emit(data, {
        id: data.id,
        summary: `New time entry with id ${data.id}`,
        ts: Date.parse(data.add_date),
      });
    },
    async emitTimeEntries() {
      const lastSyncDate = this._getLastSyncDate();

      const timeEntries = await this.timecamp.getTimeEntries({
        params: {
          from: lastSyncDate,
          to: dayjs().format("YYYY-MM-DD"),
        },
      });

      timeEntries.reverse().forEach(this.emitEvent);
    },
  },
  hooks: {
    async deploy() {
      const lastSyncDate = dayjs().subtract(1, "month")
        .format("YYYY-MM-DD");

      this._setLastSyncDate(lastSyncDate);

      await this.emitTimeEntries();
    },
  },
  async run() {
    await this.emitTimeEntries();

    const lastSyncDate = dayjs().format("YYYY-MM-DD");

    this._setLastSyncDate(lastSyncDate);
  },
};

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
TimeCamp	`timecamp`	`app`	This component uses the TimeCamp app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`

Trigger Authentication#

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

To get your API token,

Sign in to your TimeCamp account
Click on your avatar in the upper-right corner
Select your name to navigate to your Profile’s settings

About TimeCamp#

TimeCamp helps you and your team to track time. Automatic time-tracking software that tracks websites and applications usage, projects and helps you understand how your time is spent.

Action#

Add or update multiple records on Data Stores

Description:Add or update multiple records to your [Pipedream Data Store](https://pipedream.com/data-stores/).

Version:0.0.6

Key:data_stores-add-update-multiple-records

View on GitHub

Data Stores Overview#

Data Stores are a key-value store that allow you to persist state and share data across workflows. You can perform CRUD operations, enabling dynamic data management within your serverless architecture. Use it to save results from API calls, user inputs, or interim data; then read, update, or enrich this data in subsequent steps or workflows. Data Stores simplify stateful logic and cross-workflow communication, making them ideal for tracking process statuses, aggregating metrics, or serving as a simple configuration store.

Action Code#

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

export default {
  key: "data_stores-add-update-multiple-records",
  name: "Add or update multiple records",
  description: "Add or update multiple records to your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.6",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    data: {
      label: "Data",
      type: "object",
      description: "Enter data you'd like to add as key-value pairs, or reference an object from a previous step using a custom expression (e.g., `{{steps.data.$return_value}}`). Note that any keys that are duplicated will get overwritten with the last value entered (so `[{jerry: \"constanza\", jerry: \"seinfeld\"}]` will get stored as `[{jerry: \"seinfeld\"}]`).",
    },
  },
  methods: {
    /**
     * Tries to convert a string to a JSON object or a primitive value.
     * @param {any} value Value to be converted
     * @returns The converted value
     */
    convertString(value) {
      // If type is already primitive non string, return it
      const primitives = [
        "boolean",
        "number",
      ];
      if (primitives.includes(typeof value)) {
        return value;
      }

      // Tries to convert string to possible other primitive types
      if (typeof value === "string") {
        // Convert boolean
        if (value.toLowerCase() === "true") {
          return true;
        }
        if (value.toLowerCase() === "false") {
          return false;
        }

        // Convert number
        if (!isNaN(value)) {
          return parseFloat(value);
        }
      }

      return this.app.evaluate(value);
    },
    /**
     * Add all the key-value pairs in the map object to be used in the data store
     * @param {*} data Data to be parsed
     * @param {Map} map Hashmap to be updated
     */
    populateHashMapOfData(data, map) {
      if (!Array.isArray(data) && typeof(data) === "object") {
        Object.keys(data).forEach((key) => map[key] = this.convertString(data[key]));
        return;
      }

      if (Array.isArray(data)) {
        for (const item of data) {
          this.populateHashMapOfData(item, map);
        }
      }
    },
    getHashMapOfData(data) {
      const map = {};
      this.populateHashMapOfData(data, map);
      return map;
    },
  },
  async run({ $ }) {
    if (typeof this.data === "string") {
      this.data = this.app.evaluate(this.data);
    }
    const map = this.getHashMapOfData(this.data);
    const keys = Object.keys(map);
    const promises = Object.keys(map).map((key) => this.dataStore.set(key, map[key]));
    await Promise.all(promises);
    if (keys.length === 0) {
      $.export("$summary", "No data was added to the data store.");
    } else {
      // eslint-disable-next-line multiline-ternary
      $.export("$summary", `Successfully added or updated ${keys.length} record${keys.length === 1 ? "" : "s"}`);
    }
    return map;
  },
};

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
Data Stores	`app`	`app`	This component uses the Data Stores app.
Data Store	`dataStore`	`data_store`	Select an existing Data Store or create a new one.
Data	`data`	`object`	Enter data you'd like to add as key-value pairs, or reference an object from a previous step using a custom expression (e.g., `{{steps.data.$return_value}}`). Note that any keys that are duplicated will get overwritten with the last value entered (so `[{jerry: "constanza", jerry: "seinfeld"}]` will get stored as `[{jerry: "seinfeld"}]`).