Send SMS with LabsMobile API on New event when the content of the URL changes. from HTTP / Webhook API

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

Trigger workflow on

New event when the content of the URL changes. from the HTTP / Webhook API

Next, do this

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

Select this integration
Configure the New event when the content of the URL changes. trigger
1. Connect your HTTP / Webhook account
2. Configure Watching timer
3. Configure HTTP Request Configuration
4. Configure Emit body only
5. Configure Emit as array
Configure the Send SMS action
1. Connect your LabsMobile account
2. Configure Msisdn
3. Configure Message
4. Optional- Configure Tpoa
5. Optional- Configure Subid
6. Optional- Configure Label
7. Optional- Configure Test
8. Optional- Configure Ackurl
9. Optional- Configure Shortlink
10. Optional- Configure Click URL
11. Optional- Configure Scheduled
12. Optional- Configure Long
13. Optional- Configure CRT
14. Optional- Configure CRT ID
15. Optional- Configure CRT Name
16. Optional- Configure UCS 2
17. Optional- Configure No Filter
18. Optional- Configure Parameters
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 event when the content of the URL changes. on HTTP / Webhook

Description:Emit new event when the content of the URL changes.

Version:0.0.2

Key:http-watch-url

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.

Trigger Code#

import http from "../../http.app.mjs";
import hash from "object-hash";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "http-watch-url",
  name: "New event when the content of the URL changes.",
  description: "Emit new event when the content of the URL changes.",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  props: {
    http,
    timer: {
      type: "$.interface.timer",
      label: "Watching timer",
      description: "How often to watch the URL.",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    httpRequest: {
      type: "http_request",
      label: "HTTP Request Configuration",
      description: "HTTP Request Configuration",
      default: {
        method: "GET",
      },
    },
    emitBodyOnly: {
      label: "Emit body only",
      description: "If set as true the emitted item will contain only the response body, otherwise, it will include the request status code.",
      type: "boolean",
      default: true,
    },
    emitAsArray: {
      label: "Emit as array",
      description: "If the request responds with an array, this source will emit changes individually for each item of the array.",
      type: "boolean",
      default: false,
    },
  },
  methods: {
    getMeta(data, status) {
      if (this.emitBodyOnly) {
        return data;
      }
      return {
        data,
        status,
      };
    },
    emitArray(event, response) {
      if (!Array.isArray(response.data)) {
        return this.emitAny(event, response);
      }
      for (const item of response.data) {
        const meta = this.getMeta(item, response.status);
        this.emit(event, meta);
      }
    },
    emitAny(event, response) {
      const meta = this.getMeta(response.data, response.status);
      this.emit(event, meta);
    },
    emit(event, meta) {
      const ts = event.timestamp || Math.round(Date.now() / 1000);
      this.$emit(meta, {
        id: hash(meta),
        summary: `Requested at ${ts}`,
        ts,
      });
    },
  },
  async run(event) {
    const response = await this.httpRequest.execute();
    if (this.emitAsArray) {
      this.emitArray(event, response);
    } else {
      this.emitAny(event, response);
    }
  },
};

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
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.
Watching timer	`timer`	`$.interface.timer`	How often to watch the URL.
HTTP Request Configuration	`httpRequest`	`http_request`	HTTP Request Configuration
Emit body only	`emitBodyOnly`	`boolean`	If set as true the emitted item will contain only the response body, otherwise, it will include the request status code.
Emit as array	`emitAsArray`	`boolean`	If the request responds with an array, this source will emit changes individually for each item of the array.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Send SMS on LabsMobile

Description:Sends a new SMS message. [See the documentation](https://apidocs.labsmobile.com/)

Version:0.0.1

Key:labsmobile-send-sms

View on GitHub

LabsMobile Overview#

LabsMobile API enables seamless SMS messaging for various applications, perfect for notifications, authentication, or marketing. Through Pipedream, you can integrate LabsMobile with countless services and trigger SMS workflows using HTTP requests, scheduled jobs, or event-based setups. Pipedream's serverless platform simplifies these processes, allowing you to focus on building efficient, scalable messaging pipelines.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import { parseObject } from "../../common/utils.mjs";
import labsmobile from "../../labsmobile.app.mjs";

export default {
  key: "labsmobile-send-sms",
  name: "Send SMS",
  description: "Sends a new SMS message. [See the documentation](https://apidocs.labsmobile.com/)",
  version: "0.0.1",
  type: "action",
  props: {
    labsmobile,
    msisdn: {
      type: "integer[]",
      label: "Msisdn",
      description: "Parameter that includes a mobile number recipient. The number must include the country code without '+' ó '00'. Each customer account has a maximum number of msisdn per sending. See the terms of your account to see this limit.",
    },
    message: {
      type: "string",
      label: "Message",
      description: "The message to be sent. The maximum message length is 160 characters. Only characters in the GSM 3.38 7bit alphabet, found at the end of this document, are valid. Otherwise you must send `ucs2` parameter.",
    },
    tpoa: {
      type: "string",
      label: "Tpoa",
      description: "Sender of the message. May have a numeric (maximum length, 14 digits) or an alphanumeric (maximum capacity, 11 characters) value. The messaging platform assigns a default sender if this parameter is not included. By including the sender's mobile number, the message recipient can easily respond from their mobile phone with the \"Reply\" button. The sender can only be defined in some countries due to the restrictions of the operators. Otherwise the sender is a random numeric value.",
      optional: true,
    },
    subid: {
      type: "string",
      label: "Subid",
      description: "Message ID included in the ACKs (delivery confirmations). It is a unique delivery ID issued by the API client. It has a maximum length of 20 characters.",
      optional: true,
    },
    label: {
      type: "string",
      label: "Label",
      description: "Identifies the message for statistical purposes. WebSMS and other applications use this field to organize and record the message. Maximum capacity of 255 characters. Typical information contained in this field: user that has sent the message, application or module, etc. ...",
      optional: true,
    },
    test: {
      type: "boolean",
      label: "Test",
      description: "If the value is `true`, the message will be considered a test. It will not be sent to the GSM network and, therefore, will not be received on any mobile devices. However, these messages are accessible using online search tools. This parameter is intended to enable performing integration tests without an associated cost. Operator and handset confirmations will not be received.",
      optional: true,
    },
    ackurl: {
      type: "string",
      label: "Ackurl",
      description: "URL to which the corresponding delivery confirmation notifications will be sent. In the preferences section of WebSMS application you can set the default value for ackurl for all cases without having to send this parameter in each sending.",
      optional: true,
    },
    shortlink: {
      type: "boolean",
      label: "Shortlink",
      description: "If this field is present in the message and has a value of `true` the first URL would be replace by a short link of LabsMobile (format: http://lm0.es/XXXXX). The statistics of visits can be seen in WebSMS application or can be received in an url with the parameter clickurl.",
      optional: true,
    },
    clickurl: {
      type: "string",
      label: "Click URL",
      description: "URL to which the corresponding click confirmation notifications will be sent if the parameter shortlink is enabled. In the preferences section of WebSMS application you can set the default value for clickurl for all cases without having to send this parameter in each sending.",
      optional: true,
    },
    scheduled: {
      type: "string",
      label: "Scheduled",
      description: "The message will be sent at the date and time indicated in this field. If this field has not been specified, the message will be sent immediately. Format: YYYY-MM-DD HH:MM:SS. **IMPORTANT: the value of this field must be expressed using GMT time.**",
      optional: true,
    },
    long: {
      type: "boolean",
      label: "Long",
      description: "If this field is present in the message and has a value of `true`, the message field may contain up to 459 characters. Each 153 characters will be considered a single message (in terms of charges) and the recipient will receive one, concatenated message. **IMPORTANT: This option is only available in some countries due to the restrictions of the operators.**",
      optional: true,
    },
    crt: {
      type: "string",
      label: "CRT",
      description: "If this field is present in the message, it will be considered a certified SMS message. An email with the delivery certificate in an attachment will be sent to the address contained in this parameter. **IMPORTANT: This option is only implemented in some countries.**",
      optional: true,
    },
    crtId: {
      type: "string",
      label: "CRT ID",
      description: "If the message is a certified SMS message this field will be set as the tax identification number of the sender company or organization. You would see this value in the certificate in PDF format.",
      optional: true,
    },
    crtName: {
      type: "string",
      label: "CRT Name",
      description: "If the message is a certified SMS message this field will be set as the name of the sender company or organization. You would see this value in the certificate in PDF format.",
      optional: true,
    },
    ucs2: {
      type: "boolean",
      label: "UCS 2",
      description: "If this field is present in the message the message can contain any character in the UCS-2 alphabet. In this case the capacity of the message is 70 characters and can be sent concatenated to a maximum of 500 characters.",
      optional: true,
    },
    nofilter: {
      type: "boolean",
      label: "No Filter",
      description: "If this field is present the platform won't apply the duplicate filter, so no message will be blocked by this filter.",
      optional: true,
    },
    parameters: {
      type: "object",
      label: "Parameters",
      description: "This field contains values to replace parameters in the text of the message. The message can contain one or more parameters (with the following format: **%name%**, **%fieldn%**, etc.). It is necessary to specify the value of each parameter for each of the recipients or establish a default value. Example: **{\"parameters\": [{\"name\": {\"msisdn\":\"12015550123\", \"value\":\"John\"}}, {\"name\": {\"msisdn\":\"default\", \"value\":\"Client\"}}]}**",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      labsmobile,
      msisdn,
      parameters,
      crtId,
      crtName,
      ...data
    } = this;

    const response = await labsmobile.sendSMS({
      $,
      data: {
        recipient: parseObject(msisdn).map((item) => ({
          msisdn: item,
        })),
        parameters: parameters && parseObject(parameters),
        crt_id: crtId,
        crt_name: crtName,
        ...data,
      },
    });

    if (response.code != "0") {
      throw new ConfigurationError(response.message);
    }

    $.export("$summary", `Successfully sent SMS with Id: ${response.subid}`);
    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
LabsMobile	`labsmobile`	`app`	This component uses the LabsMobile app.
Msisdn	`msisdn`	`integer[]`	Parameter that includes a mobile number recipient. The number must include the country code without '+' ó '00'. Each customer account has a maximum number of msisdn per sending. See the terms of your account to see this limit.
Message	`message`	`string`	The message to be sent. The maximum message length is 160 characters. Only characters in the GSM 3.38 7bit alphabet, found at the end of this document, are valid. Otherwise you must send `ucs2` parameter.
Tpoa	`tpoa`	`string`	Sender of the message. May have a numeric (maximum length, 14 digits) or an alphanumeric (maximum capacity, 11 characters) value. The messaging platform assigns a default sender if this parameter is not included. By including the sender's mobile number, the message recipient can easily respond from their mobile phone with the "Reply" button. The sender can only be defined in some countries due to the restrictions of the operators. Otherwise the sender is a random numeric value.
Subid	`subid`	`string`	Message ID included in the ACKs (delivery confirmations). It is a unique delivery ID issued by the API client. It has a maximum length of 20 characters.
Label	`label`	`string`	Identifies the message for statistical purposes. WebSMS and other applications use this field to organize and record the message. Maximum capacity of 255 characters. Typical information contained in this field: user that has sent the message, application or module, etc. ...
Test	`test`	`boolean`	If the value is `true`, the message will be considered a test. It will not be sent to the GSM network and, therefore, will not be received on any mobile devices. However, these messages are accessible using online search tools. This parameter is intended to enable performing integration tests without an associated cost. Operator and handset confirmations will not be received.
Ackurl	`ackurl`	`string`	URL to which the corresponding delivery confirmation notifications will be sent. In the preferences section of WebSMS application you can set the default value for ackurl for all cases without having to send this parameter in each sending.
Shortlink	`shortlink`	`boolean`	If this field is present in the message and has a value of `true` the first URL would be replace by a short link of LabsMobile (format: http://lm0.es/XXXXX). The statistics of visits can be seen in WebSMS application or can be received in an url with the parameter clickurl.
Click URL	`clickurl`	`string`	URL to which the corresponding click confirmation notifications will be sent if the parameter shortlink is enabled. In the preferences section of WebSMS application you can set the default value for clickurl for all cases without having to send this parameter in each sending.
Scheduled	`scheduled`	`string`	The message will be sent at the date and time indicated in this field. If this field has not been specified, the message will be sent immediately. Format: YYYY-MM-DD HH:MM:SS. IMPORTANT: the value of this field must be expressed using GMT time.
Long	`long`	`boolean`	If this field is present in the message and has a value of `true`, the message field may contain up to 459 characters. Each 153 characters will be considered a single message (in terms of charges) and the recipient will receive one, concatenated message. IMPORTANT: This option is only available in some countries due to the restrictions of the operators.
CRT	`crt`	`string`	If this field is present in the message, it will be considered a certified SMS message. An email with the delivery certificate in an attachment will be sent to the address contained in this parameter. IMPORTANT: This option is only implemented in some countries.
CRT ID	`crtId`	`string`	If the message is a certified SMS message this field will be set as the tax identification number of the sender company or organization. You would see this value in the certificate in PDF format.
CRT Name	`crtName`	`string`	If the message is a certified SMS message this field will be set as the name of the sender company or organization. You would see this value in the certificate in PDF format.
UCS 2	`ucs2`	`boolean`	If this field is present in the message the message can contain any character in the UCS-2 alphabet. In this case the capacity of the message is 70 characters and can be sent concatenated to a maximum of 500 characters.
No Filter	`nofilter`	`boolean`	If this field is present the platform won't apply the duplicate filter, so no message will be blocked by this filter.
Parameters	`parameters`	`object`	This field contains values to replace parameters in the text of the message. The message can contain one or more parameters (with the following format: %name%, %fieldn%, etc.). It is necessary to specify the value of each parameter for each of the recipients or establish a default value. Example: {"parameters": [{"name": {"msisdn":"12015550123", "value":"John"}}, {"name": {"msisdn":"default", "value":"Client"}}]}

Action Authentication#

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

LabsMobile requires their users enter their LabsMobile email and password (or API token) in order to connect to their API. For more info, refer to LabsMobile’s documentation.

To retrieve your API token,

Navigate to your LabsMobile and sign in
Go to “Support” > “API parameters”

About LabsMobile#

LabsMobile.com is a leading provider of SMS communication services. We help any company or organization of any sector, size and country to have better and more efficient communications.

More Ways to Connect LabsMobile + HTTP / Webhook#

Other Popular Integrations#

Send SMS with LabsMobile API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + LabsMobile

Try it

Send SMS with LabsMobile API on New Requests from HTTP / Webhook API

HTTP / Webhook + LabsMobile

Try it

Popular Triggers#

New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Try it

New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it