Start Automation Flow with Triggre API on New Row from MySQL API

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

Trigger workflow on

New Row from the MySQL API

Next, do this

Start Automation Flow with the Triggre 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 MySQL trigger and Triggre action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Row trigger
1. Connect your MySQL account
2. Configure timer
3. Select a Table
4. Optional- Select a Column
Configure the Start Automation Flow action
1. Connect your Triggre account
2. Configure Flow Name
3. Configure Flow Data
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 Row on MySQL

Description:Emit new event when you add a new row to a table. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/select.html)

Version:2.0.5

Key:mysql-new-row

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.

Trigger Code#

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

const { mysql } = common.props;

export default {
  ...common,
  key: "mysql-new-row",
  name: "New Row",
  description: "Emit new event when you add a new row to a table. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/select.html)",
  type: "source",
  version: "2.0.5",
  dedupe: "unique",
  props: {
    ...common.props,
    db: "$.service.db",
    column: {
      propDefinition: [
        mysql,
        "column",
        (c) => ({
          table: c.table,
        }),
      ],
      optional: true,
    },
  },
  hooks: {
    /**
     * If column prop is left blank, get the table's primary key to use for ordering and deduping.
     * */
    async deploy() {
      const { table } = this;
      let column = this.column;

      if (!column) {
        const keyData = await this.mysql.getPrimaryKey({
          table,
        });
        column = keyData[0].Column_name;
      }

      this._setColumn(column);

      await this.listTopRows(column);
    },
  },
  methods: {
    ...common.methods,
    _getColumn() {
      return this.db.get("column");
    },
    _setColumn(column) {
      this.db.set("column", column);
    },
    async listResults() {
      const column = this._getColumn();
      await this.listRowResults(column);
    },
    iterateAndEmitEvents(rows) {
      const column = this._getColumn();
      for (const row of rows) {
        const meta = this.generateMeta(row, column);
        this.$emit(row, meta);
      }
    },
    generateMeta(row, column) {
      return {
        id: row[column],
        summary: `New Row Added ${column}: ${row[column]}`,
        ts: Date.now(),
      };
    },
  },
};

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
MySQL	`mysql`	`app`	This component uses the MySQL app.
	`timer`	`$.interface.timer`
Table	`table`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Column	`column`	`string`	Select a value from the drop down menu.

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

About MySQL#

MySQL is an open-source relational database management system.

Action#

Start Automation Flow on Triggre

Description:Starts an automation flow within your Triggre application. [See the documentation](https://docs.triggre.com/lessons/how-to-create-an-incoming-web-api)

Version:0.0.1

Key:triggre-start-automation-flow

View on GitHub

Triggre Overview#

The Triggre API offers a gateway to interact with the Triggre platform, enabling you to automate processes, manage data, and integrate with other services. On Pipedream, you can harness this API to create powerful serverless workflows, connecting Triggre with numerous other apps to streamline operations, trigger actions based on events, and manipulate data in real-time. This empowers you to build custom, automated solutions that bridge the gap between Triggre and the rest of your tech stack.

Action Code#

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

export default {
  key: "triggre-start-automation-flow",
  name: "Start Automation Flow",
  description: "Starts an automation flow within your Triggre application. [See the documentation](https://docs.triggre.com/lessons/how-to-create-an-incoming-web-api)",
  version: "0.0.1",
  type: "action",
  props: {
    triggre,
    flowName: {
      propDefinition: [
        triggre,
        "flowName",
      ],
    },
    flowData: {
      propDefinition: [
        triggre,
        "flowData",
      ],
    },
  },
  async run({ $ }) {
    const response = await this.triggre.startAutomationFlow({
      $,
      flowName: encodeURI(this.flowName),
      flowNameWithUnderscores: this.flowName.replace(/ /g, "_"),
      data: this.flowData,
    });
    $.export("$summary", `Successfully started automation flow ${this.flowName}`);
    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
Triggre	`triggre`	`app`	This component uses the Triggre app.
Flow Name	`flowName`	`string`	The name of the automation flow to start
Flow Data	`flowData`	`object`	The data to pass to the automation flow

Action Authentication#

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

To retrieve your Application Environment, Username and Password,

Navigate to https://my.triggre.com and sign in
Click on one of your applications on the left
Some buttons will appear, from those, click on "Application settings"
Your are taken to your application's connection page, click on "View connection credentials" at the bottom.
Copy your application's environment, username and password from the table on the right.