Add or update a single record with Data Stores API on New SMS Received (Instant) from Plivo API

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

Trigger workflow on

New SMS Received (Instant) from the Plivo API

Next, do this

Add or update a single record with the Data Stores API

No credit card required

▶

Watch us build a workflow

4 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 Plivo 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 SMS Received (Instant) trigger
1. Connect your Plivo account
2. Select a Phone Number
Configure the Add or update a single record action
1. Connect your Data Stores account
2. Configure Data Store
3. Select a Key
4. Configure Value
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 SMS Received (Instant) on Plivo

Description:Emit new event when a new SMS is received. [See the docs](https://www.plivo.com/docs/sms/api/message#send-a-message).

Version:0.0.1

Key:plivo-new-sms-received

View on GitHub

Plivo Overview#

The Plivo API taps into the power of cloud communication, allowing you to programmatically send SMS messages, make voice calls, and manage user verifications among other telephony functions. With Pipedream's serverless platform, you can easily integrate Plivo into workflows that automate these communication tasks, react to incoming messages or calls, and connect with numerous other apps for comprehensive automation solutions.

Trigger Code#

import common from "../common/webhook.mjs";
import constants from "../../common/constants.mjs";
import { v4 as uuid } from "uuid";

export default {
  ...common,
  key: "plivo-new-sms-received",
  name: "New SMS Received (Instant)",
  description: "Emit new event when a new SMS is received. [See the docs](https://www.plivo.com/docs/sms/api/message#send-a-message).",
  type: "source",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    ...common.props,
    phoneNumber: {
      propDefinition: [
        common.props.app,
        "phoneNumber",
      ],
    },
  },
  methods: {
    ...common.methods,
    listMessages(args = []) {
      return this.app.makeRequest({
        path: "messages.list",
        args,
      });
    },
    getResourcesFn() {
      return this.listMessages;
    },
    getResourcesFnArgs() {
      const messageTime = this.getLastMessageTime();
      return messageTime
        ? {
          limit: constants.DEFAULT_LIMIT,
          message_time__gt: messageTime,
        }
        : {
          limit: constants.DEFAULT_LIMIT,
        };
    },
    getPhoneNumber() {
      return this.phoneNumber;
    },
    generateMeta(resource) {
      if (resource.messageUuid) {
        return {
          id: resource.messageUuid,
          ts: Date.parse(resource.messageTime),
          summary: `History SMS received from ${resource.fromNumber}`,
        };
      }
      return {
        id: resource.MessageUUID,
        ts: Date.now(),
        summary: `New SMS received from ${resource.From}`,
      };
    },
    isResourceRelevant(resource) {
      return resource.messageDirection === constants.RESOURCE.MSG.DIRECTION.INBOUND
        && resource.messageState === constants.RESOURCE.MSG.STATUS.DELIVERED
        && resource.messageType === constants.RESOURCE.MSG.TYPE.SMS;
    },
    getApplicationName() {
      return `PipedreamInboundSMS${uuid()}`;
    },
  },
};

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
Plivo	`app`	`app`	This component uses the Plivo app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.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.
Phone Number	`phoneNumber`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

All requests to Plivo API are authenticated with BasicAuth using your AUTH ID and AUTH TOKEN. Your Plivo AUTH ID and AUTH TOKEN can be found when you login to your dashboard.

About Plivo#

SMS API and Voice API platform

Action#

Add or update a single record on Data Stores

Description:Add or update a single record in your [Pipedream Data Store](https://pipedream.com/data-stores/).

Version:0.0.9

Key:data_stores-add-update-record

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-record",
  name: "Add or update a single record",
  description: "Add or update a single record in your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.9",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    key: {
      propDefinition: [
        app,
        "key",
        ({ dataStore }) => ({
          dataStore,
        }),
      ],
      description: "Enter a key for the record you'd like to create or select an existing key to update.",
    },
    value: {
      propDefinition: [
        app,
        "value",
      ],
    },
  },
  async run({ $ }) {
    const {
      key,
      value,
    } = this;
    const exists = await this.dataStore.has(key);
    const parsedValue = this.app.parseValue(value);
    await this.dataStore.set(key, parsedValue);
    // eslint-disable-next-line multiline-ternary
    $.export("$summary", `Successfully ${exists ? "updated the record for" : "added a new record with the"} key, \`${key}\`.`);
    return {
      key,
      value: parsedValue,
    };
  },
};

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.
Key	`key`	`string`	Select a value from the drop down menu.
Value	`value`	`any`	Enter a string, object, or array.