Add or update multiple records with Data Stores API on New Check-In By Teammate Created from Range API

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

Trigger workflow on

New Check-In By Teammate Created from the Range 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 800,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Range 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 Check-In By Teammate Created trigger
1. Connect your Range account
2. Configure Polling schedule
3. Select a User ID
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 Check-In By Teammate Created on Range

Description:Emit new event when a new check-in by teammate is created. [See the docs](https://www.range.co/docs/api#rpc-list-updates).

Version:0.0.1

Key:range-new-check-in-by-teammate-created

View on GitHub

Range Overview#

The Range API provides a platform for managing print shop operations, including job status tracking, quoting, invoicing, and scheduling. Leveraging Pipedream, users can automate workflows between Range and other apps, creating a seamless integration that boosts productivity. Whether it's syncing order details with a CRM, triggering notifications based on job status updates, or automating invoice creation, Pipedream acts as a conduit for connecting Range's print shop management capabilities with a myriad of other services.

Trigger Code#

import common from "../common/polling.mjs";
import constants from "../../common/constants.mjs";

export default {
  ...common,
  key: "range-new-check-in-by-teammate-created",
  name: "New Check-In By Teammate Created",
  description: "Emit new event when a new check-in by teammate is created. [See the docs](https://www.range.co/docs/api#rpc-list-updates).",
  type: "source",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    ...common.props,
    userId: {
      propDefinition: [
        common.props.app,
        "userId",
      ],
    },
  },
  methods: {
    ...common.methods,
    getResourcesFn() {
      return this.listUpdates;
    },
    getResourcesFnArgs() {
      const lastPublishedAt = this.getLastPublishedAt();

      const args = {
        params: {
          target_id: this.userId,
          count: constants.DEFAULT_LIMIT,
          ascending: false,
        },
      };

      if (!lastPublishedAt) {
        return args;
      }

      return {
        ...args,
        params: {
          ...args.params,
          after: lastPublishedAt,
        },
      };
    },
    getResourcesName() {
      return "updates";
    },
    generateMeta(resource) {
      const ts = Date.parse(resource.published_at);
      return {
        id: ts,
        ts,
        summary: `New Check-In at ${resource.published_at}`,
      };
    },
  },
};

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
Range	`app`	`app`	This component uses the Range app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling schedule	`timer`	`$.interface.timer`	How often to poll the Range API
User ID	`userId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

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

default

About Range#

The place for remote & hybrid teams to check in with each other

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"}]`).