← Stripe + LabsMobile integrations

Send SMS with LabsMobile API on New Failed Invoice Payment from Stripe API

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

Trigger workflow on
New Failed Invoice Payment from the Stripe API
Next, do this
Send SMS with the LabsMobile API
No credit card required
Intro to Pipedream
Watch us build a workflow
Watch us build a workflow
8 min
Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Adyen logo
Appcues logo
Bandwidth logo
Checkr logo
ChartMogul logo
Dataminr logo
Gopuff logo
Gorgias logo
LinkedIn logo
Logitech logo
Replicated logo
Rudderstack logo
SAS logo
Scale AI logo
Webflow logo
Warner Bros. logo
Adyen logo
Appcues logo
Bandwidth logo
Checkr logo
ChartMogul logo
Dataminr logo
Gopuff logo
Gorgias logo
LinkedIn logo
Logitech logo
Replicated logo
Rudderstack logo
SAS logo
Scale AI logo
Webflow logo
Warner Bros. logo

Developers Pipedream

Getting Started

This integration creates a workflow with a Stripe trigger and LabsMobile 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 Failed Invoice Payment trigger
    1. Connect your Stripe account
  3. 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
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. 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

Description:Emit new event for each new failed invoice payment
Version:0.1.1
Key:stripe-new-failed-invoice-payment

Stripe Overview

The Stripe API is a powerful tool for managing online payments, subscriptions, and invoices. With Pipedream, you can leverage this API to automate payment processing, monitor transactions, and sync billing data with other services. Pipedream's no-code platform allows for quick integration and creation of serverless workflows that react to Stripe events in real-time. For instance, you might automatically update customer records, send personalized emails after successful payments, or escalate failed transactions to your support team.

Trigger Code

import common from "../common/webhook-base.mjs";

export default {
  ...common,
  key: "stripe-new-failed-invoice-payment",
  name: "New Failed Invoice Payment",
  type: "source",
  version: "0.1.1",
  description: "Emit new event for each new failed invoice payment",
  methods: {
    ...common.methods,
    getEvents() {
      return [
        "invoice.payment_failed",
      ];
    },
  },
};

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.
LabelPropTypeDescription
StripestripeappThis component uses the Stripe app.
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.
N/Adb$.service.dbThis component uses $.service.db to maintain state between executions.

Trigger Authentication

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

Stripe uses API keys to authenticate requests (more info in their docs here).

To connect Pipedream to your Stripe account,

  1. Create a Stripe API key
  2. Click "Create Restricted Key"
  3. Enter the Restricted API key below.

To help ensure proper security, we recommend you create a Restricted key with scopes relevant to the specific operations you will use in Pipedream.

About Stripe

Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes.

Action

Description:Sends a new SMS message. [See the documentation](https://apidocs.labsmobile.com/)
Version:0.0.1
Key:labsmobile-send-sms

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.

LabelPropTypeDescription
LabsMobilelabsmobileappThis component uses the LabsMobile app.
Msisdnmsisdninteger[]

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.

Messagemessagestring

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.

Tpoatpoastring

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.

Subidsubidstring

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.

Labellabelstring

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. ...

Testtestboolean

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.

Ackurlackurlstring

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.

Shortlinkshortlinkboolean

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 URLclickurlstring

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.

Scheduledscheduledstring

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.

Longlongboolean

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.

CRTcrtstring

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 IDcrtIdstring

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 NamecrtNamestring

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 2ucs2boolean

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 Filternofilterboolean

If this field is present the platform won't apply the duplicate filter, so no message will be blocked by this filter.

Parametersparametersobject

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 + Stripe

Send SMS with LabsMobile API on New Abandoned Cart from Stripe API
Stripe + LabsMobile
 
Try it
Send SMS with LabsMobile API on Canceled Subscription from Stripe API
Stripe + LabsMobile
 
Try it
Send SMS with LabsMobile API on New Custom Webhook Events from Stripe API
Stripe + LabsMobile
 
Try it
Send SMS with LabsMobile API on New Customer from Stripe API
Stripe + LabsMobile
 
Try it
Send SMS with LabsMobile API on New Dispute from Stripe API
Stripe + LabsMobile
 
Try it
New Custom Webhook Events from the Stripe API

Emit new event on each webhook event

 
Try it
Canceled Subscription from the Stripe API

Emit new event for each new canceled subscription

 
Try it
New Abandoned Cart from the Stripe API

Emit new event when a customer abandons their cart.

 
Try it
New Customer from the Stripe API

Emit new event for each new customer

 
Try it
New Dispute from the Stripe API

Emit new event for each new dispute

 
Try it
Cancel a Payment Intent with the Stripe API

Cancel a payment intent. Once canceled, no additional charges will be made by the payment intent and any operations on the payment intent will fail with an error. For payment intents with status=requires_capture, the remaining amount_capturable will automatically be refunded. See the docs for more information

 
Try it
Cancel Or Reverse a Payout with the Stripe API

Cancel or reverse a payout. A payout can be canceled only if it has not yet been paid out. A payout can be reversed only if it has already been paid out. Funds will be refunded to your available balance. See the docs for more information

 
Try it
Capture a Payment Intent with the Stripe API

Capture the funds of an existing uncaptured payment intent. See the docs for more information

 
Try it
Confirm a Payment Intent with the Stripe API

Confirm that your customer intends to pay with current or provided payment method. Upon confirmation, Stripe will attempt to initiate a payment. See the docs for more information

 
Try it
Create a Customer with the Stripe API

Create a customer. See the docs for more information

 
Try it

Explore Other Apps

1
-
24
of
2,400+
apps by most popular

HTTP / Webhook
HTTP / Webhook
Get a unique URL where you can send HTTP or webhook requests
Node
Node
Anything you can do with Node.js, you can do in a Pipedream workflow. This includes using most of npm's 400,000+ packages.
Python
Python
Anything you can do in Python can be done in a Pipedream Workflow. This includes using any of the 350,000+ PyPi packages available in your Python powered workflows.
OpenAI (ChatGPT)
OpenAI (ChatGPT)
OpenAI is an AI research and deployment company with the mission to ensure that artificial general intelligence benefits all of humanity. They are the makers of popular models like ChatGPT, DALL-E, and Whisper.
Premium
Salesforce
Salesforce
Web services API for interacting with Salesforce
Premium
HubSpot
HubSpot
HubSpot's CRM platform contains the marketing, sales, service, operations, and website-building software you need to grow your business.
Premium
Zoho CRM
Zoho CRM
Zoho CRM is an online Sales CRM software that manages your sales, marketing, and support in one CRM platform.
Premium
Stripe
Stripe
Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes.
Shopify
Shopify
Shopify is a complete commerce platform that lets anyone start, manage, and grow a business. You can use Shopify to build an online store, manage sales, market to customers, and accept payments in digital and physical locations.
Premium
WooCommerce
WooCommerce
WooCommerce is the open-source ecommerce platform for WordPress.
Premium
Snowflake
Snowflake
A data warehouse built for the cloud
Premium
MongoDB
MongoDB
MongoDB is an open source NoSQL database management program.
Supabase
Supabase
Supabase is an open source Firebase alternative.
MySQL
MySQL
MySQL is an open-source relational database management system.
PostgreSQL
PostgreSQL
PostgreSQL is a free and open-source relational database management system emphasizing extensibility and SQL compliance.
Premium
AWS
AWS
Amazon Web Services (AWS) offers reliable, scalable, and inexpensive cloud computing services.
Premium
Twilio SendGrid
Twilio SendGrid
Send marketing and transactional email through the Twilio SendGrid platform with the Email API, proprietary mail transfer agent, and infrastructure for scalable delivery.
Amazon SES
Amazon SES
Amazon SES is a cloud-based email service provider that can integrate into any application for high volume email automation
Premium
Klaviyo
Klaviyo
Email Marketing and SMS Marketing Platform
Premium
Zendesk
Zendesk
Zendesk is award-winning customer service software trusted by 200K+ customers. Make customers happy via text, mobile, phone, email, live chat, social media.
Notion
Notion
Notion is a new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Slack
Slack
Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.
Microsoft Teams
Microsoft Teams
Microsoft Teams has communities, events, chats, channels, meetings, storage, tasks, and calendars in one place.
Schedule
Schedule
Trigger workflows on an interval or cron schedule.