Send SMS Messages with InMobile API on New or Updated Row from MySQL API

Pipedream makes it easy to connect APIs for InMobile, MySQL and 2,900+ other apps remarkably fast.

Trigger workflow on

New or Updated Row from the MySQL API

Next, do this

Send SMS Messages with the InMobile 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 MySQL trigger and InMobile action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New or Updated Row trigger
1. Connect your MySQL account
2. Configure timer
3. Select a Table
4. Select a Order By
Configure the Send SMS Messages action
1. Connect your InMobile account
2. Configure Messages
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 or Updated Row on MySQL

Description:Emit new event when you add or modify a new row in a table. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/select.html)

Version:2.0.6

Key:mysql-new-or-updated-row

View on GitHub

MySQL Overview#

The MySQL application on Pipedream enables direct interaction with your MySQL databases, allowing you to perform CRUD operations—create, read, update, delete—on your data with ease. You can leverage these capabilities to automate data synchronization, report generation, and event-based triggers that kick off workflows in other apps. With Pipedream's serverless platform, you can connect MySQL to hundreds of other services without managing infrastructure, crafting complex code, or handling authentication.

Trigger Code#

import common from "../common/table.mjs";
import { v4 as uuidv4 } from "uuid";

const { mysql } = common.props;

export default {
  ...common,
  key: "mysql-new-or-updated-row",
  name: "New or Updated Row",
  description:
    "Emit new event when you add or modify a new row in a table. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/select.html)",
  type: "source",
  version: "2.0.6",
  dedupe: "unique",
  props: {
    ...common.props,
    db: "$.service.db",
    column: {
      propDefinition: [
        mysql,
        "column",
        (c) => ({
          table: c.table,
        }),
      ],
      label: "Order By",
      description:
        "A datetime column, such as 'date_updated' or 'last_modified' that is set to the current datetime when a row is updated.",
    },
  },
  hooks: {
    async deploy() {
      await this.listTopRows(this.column);
    },
  },
  methods: {
    ...common.methods,
    async listResults() {
      await this.listRowResults(this.column);
    },
    generateMeta(row) {
      return {
        id: uuidv4(),
        summary: `New Row Added/Updated ${row[this.column]}`,
        ts: Date.now(),
      };
    },
  },
};

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
MySQL	`mysql`	`app`	This component uses the MySQL app.
	`timer`	`$.interface.timer`
Table	`table`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Order By	`column`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

Connecting to Restricted Databases

Either enable the shared static IP for this account below, or configure a VPC to deploy any workflow in your workspace to a private network with a dedicated static IP. Learn more in our docs

SSL Setup

Configure SSL on your MySQL database by providing the CA (Certificate Authority), and choosing between Full Verification, Verify Certificate Authority (CA), or Skip Verification. Skipping verification is not recommended as this has serious security implications

About MySQL#

MySQL is an open-source relational database management system.

Action#

Send SMS Messages on InMobile

Description:Send one or more SMS messages using the InMobile API. [See the documentation](https://www.inmobile.com/docs/rest-api)

Version:0.0.1

Key:inmobile-send-sms-messages

View on GitHub

InMobile Overview#

The InMobile API affords you the ability to automate and integrate SMS messaging services into your business workflows. Through Pipedream, you can craft serverless workflows that leverage these capabilities to interact with customers, send alerts, and integrate with other services for a seamless communication ecosystem. Harnessing the power of the InMobile API on Pipedream lets you send messages, manage contacts, and track message delivery within custom workflows, without the fuss of server maintenance.

Action Code#

import app from "../../inmobile.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "inmobile-send-sms-messages",
  name: "Send SMS Messages",
  description: "Send one or more SMS messages using the InMobile API. [See the documentation](https://www.inmobile.com/docs/rest-api)",
  version: "0.0.1",
  type: "action",
  annotations: {
    readOnlyHint: false,
    destructiveHint: true,
    openWorldHint: true,
  },
  props: {
    app,
    messages: {
      type: "string[]",
      label: "Messages",
      description: `An array of message objects (1-250 messages). Each message object supports the following properties:

**Required Fields:**
- \`to\` (string): The msisdn (country code and number) to send to. Remember to include country code, e.g. \`4512345678\`
- \`text\` (string): The text message (1-10000 characters)
- \`from\` (string): The sender. Can be a 3-11 character text sender or up to 14 digit sender number

**Optional Fields:**
- \`countryHint\` (string): Country code for optimal phone number validation, e.g. \`44\` or \`GB\`
- \`messageId\` (string): Optional message ID to identify the message (1-50 characters, must be unique)
- \`respectBlacklist\` (boolean): Block message if target number is blacklisted. Default: \`true\`
- \`validityPeriodInSeconds\` (integer): Validity period (60-172800 seconds). Default: \`172800\` (48 hours)
- \`statusCallbackUrl\` (string): URL for delivery status callbacks
- \`sendTime\` (string): Schedule message for future sending, e.g. \`2024-12-31T14:50:23Z\` (UTC time)
- \`msisdnCooldownInMinutes\` (integer): Prevent sending to same number within period (60-43200 minutes)
- \`flash\` (boolean): Send as flash message (class0). Default: \`false\`
- \`encoding\` (string): Message encoding - \`gsm7\` (default, 160 chars), \`ucs2\` (70 chars), or \`auto\`

**Example:**
\`\`\`json
[
  {
    "to": "4512345678",
    "text": "Hello World",
    "from": "YourSender",
    "encoding": "gsm7"
  },
  {
    "to": "4587654321",
    "text": "Another message",
    "from": "YourSender",
    "flash": true
  }
]
\`\`\``,
    },
  },
  async run({ $ }) {
    const {
      app,
      messages,
    } = this;

    const response = await app.sendSms({
      $,
      data: {
        messages: utils.parseArray(messages),
      },
    });

    $.export("$summary", "Successfully sent SMS messages");
    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.

Label	Prop	Type	Description
InMobile	`app`	`app`	This component uses the InMobile app.
Messages	`messages`	`string[]`	An array of message objects (1-250 messages). Each message object supports the following properties: Required Fields: `to` (string): The msisdn (country code and number) to send to. Remember to include country code, e.g. `4512345678` `text` (string): The text message (1-10000 characters) `from` (string): The sender. Can be a 3-11 character text sender or up to 14 digit sender number Optional Fields: `countryHint` (string): Country code for optimal phone number validation, e.g. `44` or `GB` `messageId` (string): Optional message ID to identify the message (1-50 characters, must be unique) `respectBlacklist` (boolean): Block message if target number is blacklisted. Default: `true` `validityPeriodInSeconds` (integer): Validity period (60-172800 seconds). Default: `172800` (48 hours) `statusCallbackUrl` (string): URL for delivery status callbacks `sendTime` (string): Schedule message for future sending, e.g. `2024-12-31T14:50:23Z` (UTC time) `msisdnCooldownInMinutes` (integer): Prevent sending to same number within period (60-43200 minutes) `flash` (boolean): Send as flash message (class0). Default: `false` `encoding` (string): Message encoding - `gsm7` (default, 160 chars), `ucs2` (70 chars), or `auto` Example: `[ { "to": "4512345678", "text": "Hello World", "from": "YourSender", "encoding": "gsm7" }, { "to": "4587654321", "text": "Another message", "from": "YourSender", "flash": true } ]`