← Ringcentral + Bandwidth integrations

Send SMS with Bandwidth APIon New Inbound Call (Instant) from Ringcentral API

Pipedream makes it easy to connect APIs for Bandwidth, Ringcentral and + other apps remarkably fast.

Trigger workflow on
New Inbound Call (Instant) from the Ringcentral API
Next, do this
Send SMS with the Bandwidth API
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a Ringcentral trigger and Bandwidth action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the New Inbound Call (Instant) trigger
    1. Connect your Ringcentral account
    2. Select a Extension
  3. Configure the Send SMS action
    1. Connect your Bandwidth account
    2. Configure To
    3. Configure From
    4. Configure Message
    5. Configure Messaging Application ID
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger


This integration uses pre-built, open source 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.


Description:Emits an event on each incoming call

Trigger Code

const common = require("../common/http-based");

module.exports = {
  key: "ringcentral-new-inbound-call",
  name: "New Inbound Call (Instant)",
  description: "Emits an event on each incoming call",
  version: "0.0.1",
  props: {
    extensionId: { propDefinition: [common.props.ringcentral, "extensionId"] },
  methods: {
    getSupportedNotificationTypes() {
      return new Set([
    generateMeta(data) {
      const {
        body: eventDetails,
      } = data;
      const {
        telephonySessionId: id,
      } = eventDetails;
      const {
        from: {
          phoneNumber: callerPhoneNumber,
      } = eventDetails.parties[0];

      const maskedCallerNumber = this.getMaskedNumber(callerPhoneNumber);
      const summary = `New inbound call from ${maskedCallerNumber}`;
      const ts = Date.parse(timestamp);

      return {
    isEventRelevant(event) {
      const { body: eventDetails } = event.body;
      const {
        status: { code: statusCode }
      } = eventDetails.parties[0];
      return statusCode === "Setup";

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.
RingcentralringcentralappThis component uses the Ringcentral app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
N/Ahttp$.interface.httpThis 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.
ExtensionextensionIdstringSelect a value from the drop down menu.

Trigger Authentication

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

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

About Ringcentral

Business communications platform


Description:Send an SMS message using Bandwidth's Messaging API

Action Code

const bandwidth = require("../../bandwidth.app.js");

module.exports = {
  key: "bandwidth-send-sms",
  name: "Send SMS",
  description: "Send an SMS message using Bandwidth's Messaging API",
  type: "action",
  version: "1.0.0",
  props: {
    messageTo: {
      propDefinition: [
    from: {
      propDefinition: [
    message: {
      propDefinition: [
    messagingApplicationId: {
      propDefinition: [
  async run () {
    const response = await this.bandwidth.sendSms(
    console.log("Status Code:", response.statusCode);
    console.log("Message ID:", response.result.id);
    return response;

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.

BandwidthbandwidthappThis component uses the Bandwidth app.

The number the message will be sent to, in E164 format ex +19195551234


The number the call or message event will come from, in E164 format ex +19195551234


The text message content

Messaging Application IDmessagingApplicationIdstring

The ID from the messaging application created in the Bandwidth Dashboard.

The application must be associated with the location that the from number lives on.

Action Authentication

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

Bandwidth.com requires the user's username:password pair to be encoded as part of the header. (docs)
The accountId is used as part of the url to make API requests. Ex: https://dashboard.bandwidth.com/api/accounts/{accountId}/

About Bandwidth

Enterprise Grade Voice, Messaging, and 911 Access

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.