Send SMS Messages with InMobile API on New Message (Instant) from Discord API

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

Trigger workflow on

New Message (Instant) from the Discord 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 Discord 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 Message (Instant) trigger
1. Connect your Discord account
2. Configure Channels
3. Configure discordApphook
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 Message (Instant) on Discord

Description:Emit new event for each message posted to one or more channels in a Discord server

Version:1.0.3

Key:discord-new-message

View on GitHub

Discord Overview#

The Discord API interacts seamlessly with Pipedream, empowering you to craft customized automations and workflows for your Discord server. With this powerful integration, you can automate tasks like message posting, user management, and notifications, based on a myriad of triggers and actions from different apps. These automations can enhance the Discord experience for community moderators and members, by synchronizing with external tools, organizing community engagement, and streamlining notifications.

Trigger Code#

import discord from "../../discord.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  type: "source",
  key: "discord-new-message",
  name: "New Message (Instant)",
  description: "Emit new event for each message posted to one or more channels in a Discord server",
  version: "1.0.3",

  dedupe: "unique",
  props: {
    discord,
    channels: {
      type: "$.discord.channel[]",
      appProp: "discord",
      label: "Channels",
      description: "Select the channel(s) you'd like to be notified for",
    },
    // eslint-disable-next-line pipedream/props-label,pipedream/props-description
    discordApphook: {
      type: "$.interface.apphook",
      appProp: "discord",
      async eventNames() {
        return this.channels || [];
      },
    },
  },
  async run(event) {
    if (event.guildID != this.discord.$auth.guild_id) {
      return;
    }
    this.$emit(event, {
      id: event.id,
    });
  },
  sampleEmit,
};

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
Discord	`discord`	`app`	This component uses the Discord app.
Channels	`channels`	`$.discord.channel[]`	Select the channel(s) you'd like to be notified for
	`discordApphook`	`$.interface.apphook`

Trigger Authentication#

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

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

botemailidentifyguilds

About Discord#

Use this app to create a Discord source that emits messages from your guild to a Pipedream workflow.

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 } ]`