Execute Stored Procedure with MySQL API on New Message Received from Line API

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

Trigger workflow on

New Message Received from the Line API

Next, do this

Execute Stored Procedure with the MySQL 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 Line trigger and MySQL 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 Received trigger
1. Connect your Line account
2. Configure Channel Access Token
Configure the Execute Stored Procedure action
1. Connect your MySQL account
2. Select a Stored Procedure
3. 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 Message Received on Line

Description:Emit new event for every received message in a channel. [See docs here](https://developers.line.biz/en/docs/messaging-api/building-bot/#page-title)

Version:0.0.2

Key:line-new-message-received

View on GitHub

Line Overview#

The Line API facilitates interaction with Line's messaging platform, enabling developers to send messages, manage user data, and leverage Line's rich social features within their applications. By using Pipedream, an integration platform, you can automate interactions with the Line API, connect to countless other services, and orchestrate complex workflows without managing servers.

Trigger Code#

import line from "../../line.app.mjs";
import sampleEmit from "./test-event.mjs";
import { axios } from "@pipedream/platform";

export default {
  key: "line-new-message-received",
  name: "New Message Received",
  description: "Emit new event for every received message in a channel. [See docs here](https://developers.line.biz/en/docs/messaging-api/building-bot/#page-title)",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  props: {
    line,
    db: "$.service.db",
    http: "$.interface.http",
    channelAccessToken: {
      propDefinition: [
        line,
        "channelAccessToken",
      ],
    },
  },
  hooks: {
    async activate() {
      try {
        await this.checkWebhook();
        await this.createWebhook();
        console.log("Webhook created successfully.");
        console.log("If you are not receiving webhooks, please confirm you have Use Webhooks enabled in your Line Developer Console:");
      } catch (error) {
        console.log(error);
        console.log("Please make sure you have enabled webhooks in your Line Developer Console:");
      }
      console.log("https://developers.line.biz/en/docs/messaging-api/building-bot/#setting-webhook-url");
    },
  },
  methods: {
    async _makeRequest(opts) {
      await axios(null, {
        ...opts,
        url: "https://api.line.me/v2/bot/channel/webhook/endpoint",
        headers: {
          Authorization: `Bearer ${this.channelAccessToken}`,
        },
      });
    },
    async checkWebhook() {
      await this._makeRequest();
    },
    async createWebhook() {
      await this._makeRequest({
        method: "put",
        data: {
          endpoint: this.http.endpoint,
        },
      });
    },
  },
  async run(event) {
    event.body.events.forEach((event) => {
      if (event.type === "message") {
        this.$emit(event, {
          id: event.message.id,
          summary: event.message.text,
          ts: event.timestamp,
        });
      }
    });
  },
  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
Line	`line`	`app`	This component uses the Line app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.interface.http`	This 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.
Channel Access Token	`channelAccessToken`	`string`	The access token of a group or room. Please refer to the Line doc here to get the channel access token

Trigger Authentication#

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

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

notify

About Line#

Line is a communication app that connects people, services, and information.

Action#

Execute Stored Procedure on MySQL

Description:Execute Stored Procedure. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/stored-programs-defining.html)

Version:2.0.5

Key:mysql-execute-stored-procedure

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.

Action Code#

import mysql from "../../mysql.app.mjs";

export default {
  key: "mysql-execute-stored-procedure",
  name: "Execute Stored Procedure",
  description: "Execute Stored Procedure. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/stored-programs-defining.html)",
  type: "action",
  version: "2.0.5",
  props: {
    mysql,
    storedProcedure: {
      propDefinition: [
        mysql,
        "storedProcedure",
      ],
    },
    values: {
      propDefinition: [
        mysql,
        "storedProcedureParameters",
      ],
    },
  },
  async run({ $ }) {
    const {
      storedProcedure,
      values,
    } = this;

    const response = await this.mysql.executeStoredProcedure({
      storedProcedure,
      values,
    });

    $.export("$summary", `Successfully executed stored procedure ${storedProcedure}`);

    const result =
      Array.isArray(response)
        ? response[0]
        : response;

    return result || {
      success: false,
    };
  },
};

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
MySQL	`mysql`	`app`	This component uses the MySQL app.
Stored Procedure	`storedProcedure`	`string`	Select a value from the drop down menu.
Parameters	`values`	`string[]`	Parameters for the stored procedure

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