Execute SQL Query with MySQL API on New Phone Call Missed Event from Trengo API

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

Trigger workflow on

New Phone Call Missed Event from the Trengo API

Next, do this

Execute SQL Query 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 Trengo 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 Phone Call Missed Event trigger
1. Connect your Trengo account
Configure the Execute SQL Query action
1. Connect your MySQL account
2. Configure SQL Query
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 Phone Call Missed Event on Trengo

Description:Emit new events when an phone call missed. [See the docs here](https://developers.trengo.com/docs/webhooks)

Version:0.0.1

Key:trengo-phone-call-missed

View on GitHub

Trengo Overview#

The Trengo API provides programmatic access to Trengo's multi-channel communication platform, allowing for the streamlining of customer interactions across various channels such as email, SMS, social media, and chat. By leveraging the Trengo API on Pipedream, you can automate customer support workflows, sync communication data with CRM systems, and trigger alerts or actions based on specific customer queries or events.

Trigger Code#

import common from "../common/common.mjs";

export default {
  key: "trengo-phone-call-missed",
  name: "New Phone Call Missed Event",
  description: "Emit new events when an phone call missed. [See the docs here](https://developers.trengo.com/docs/webhooks)",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  ...common,
  methods: {
    ...common.methods,
    getMeta(event) {
      return {
        id: Date.now(),
        ts: Date.now(),
        summary: `New phone call missed event: ${event?.body?.from} => ${event?.body?.to}`,
      };
    },
    getEvent() {
      return  "VOICE_CALL_MISSED";
    },
  },
};

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
Trengo	`app`	`app`	This component uses the Trengo app.
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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

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

You need a personal access token to access the API and to perform actions on your behalf. Your personal access token needs to be send trough an Authorization Bearer request. See docs.

About Trengo#

Customer service software

Action#

Execute SQL Query on MySQL

Description:Execute a custom MySQL query. See [our docs](https://pipedream.com/docs/databases/working-with-sql) to learn more about working with SQL in Pipedream.

Version:2.0.1

Key:mysql-execute-raw-query

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-raw-query",
  name: "Execute SQL Query",
  description: "Execute a custom MySQL query. See [our docs](https://pipedream.com/docs/databases/working-with-sql) to learn more about working with SQL in Pipedream.",
  type: "action",
  version: "2.0.1",
  props: {
    mysql,
    // eslint-disable-next-line pipedream/props-description
    sql: {
      type: "sql",
      auth: {
        app: "mysql",
      },
      label: "SQL Query",
    },
  },
  async run({ $ }) {
    const args = this.mysql.executeQueryAdapter(this.sql);
    const data = await this.mysql.executeQuery(args);
    $.export("$summary", `Returned ${data.length} ${data.length === 1
      ? "row"
      : "rows"}`);
    return data;
  },
};

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.
SQL Query	`sql`	`sql`

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.