Send GET Request with HTTP / Webhook API on New SMS Received (Instant) from Plivo API

Pipedream makes it easy to connect APIs for HTTP / Webhook, Plivo and 2,400+ other apps remarkably fast.

Trigger workflow on

New SMS Received (Instant) from the Plivo API

Next, do this

Send GET Request with the HTTP / Webhook 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 Plivo trigger and HTTP / Webhook 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 Send GET Request action
1. Connect your HTTP / Webhook account
2. Configure HTTP Request Configuration
3. Optional- Configure Include Response Headers
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#

Send GET Request on HTTP / Webhook

Description:Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

Version:1.1.1

Key:http-get-request

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.

Action Code#

import customRequest from "../custom-request/custom-request.mjs";

export default {
  ...customRequest,
  key: "http-get-request",
  name: "Send GET Request",
  description: "Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.",
  type: "action",
  version: "1.1.1",
  props: {
    ...customRequest.props,
    /* eslint-disable-next-line pipedream/props-label,pipedream/props-description */
    httpRequest: {
      ...customRequest.props.httpRequest,
      default: {
        method: "GET",
      },
    },
  },
};

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
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.
HTTP Request Configuration	`httpRequest`	`http_request`
Include Response Headers	`includeHeaders`	`boolean`	Optionally export the full response headers