Launch Phantom with Phantombuster API on New Row from MySQL API

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

Trigger workflow on

New Row from the MySQL API

Next, do this

Launch Phantom with the Phantombuster 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 Phantombuster 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 Launch Phantom action
1. Connect your Phantombuster account
2. Select a Agent ID
3. Optional- Configure Arguments
4. Optional- Configure Save Arguments
5. Optional- Configure Bonus Argument
6. Optional- Configure Manual Launch
7. Optional- Configure Max Instance Count
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#

Launch Phantom on Phantombuster

Description:Adds an agent to the launch queue, [See the docs](https://hub.phantombuster.com/reference/post_agents-launch-1)

Version:0.0.1

Key:phantombuster-launch-phantom

View on GitHub

Phantombuster Overview#

Phantombuster is a tool that lets you automate interactions with web platforms to extract data, manage social media campaigns, and automate web actions. Using its API on Pipedream, you can seamlessly integrate these automation capabilities into complex workflows. Imagine orchestrating a symphony where Phantombuster plays the strings—pulling data from LinkedIn, sending tailored tweets, or automating lead generation—while Pipedream conducts, integrating these actions with other apps and services for a harmonious data-driven performance.

Action Code#

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

export default {
  type: "action",
  key: "phantombuster-launch-phantom",
  version: "0.0.1",
  name: "Launch Phantom",
  description: "Adds an agent to the launch queue, [See the docs](https://hub.phantombuster.com/reference/post_agents-launch-1)",
  props: {
    app,
    agentId: {
      propDefinition: [
        app,
        "agentId",
      ],
    },
    arguments: {
      type: "string",
      label: "Arguments",
      description: "Agent arguments. Must be a JSON string, e.g. `{\"key1\": \"Value 1\", \"key2\": \"Value 2\"}`",
      optional: true,
    },
    saveArguments: {
      type: "boolean",
      label: "Save Arguments",
      description: "If true, argument will be saved as the default launch options for the agent.",
      optional: true,
    },
    bonusArgument: {
      type: "string",
      label: "Bonus Argument",
      description: "Agent bonus argument. This bonus argument is single-use, it will only be used for the current launch. Must be a JSON string, e.g. `{\"key1\": \"Value 1\", \"key2\": \"Value 2\"}`",
      optional: true,
    },
    manualLaunch: {
      type: "boolean",
      label: "Manual Launch",
      description: "If set, the agent will be considered as `launched manually`.",
      optional: true,
    },
    maxInstanceCount: {
      type: "integer",
      label: "Max Instance Count",
      description: "If set, the agent will only be launched if the number of already running instances is below the specified number.",
      optional: true,
    },
  },
  async run ({ $ }) {
    const resp = await this.app.launchPhantom({
      $,
      data: {
        id: this.agentId,
        arguments: this.arguments,
        saveArguments: this.saveArguments,
        bonusArgument: this.bonusArgument,
        manualLaunch: this.manualLaunch,
        maxInstanceCount: this.maxInstanceCount,
      },
    });
    $.export("$summary", `Phantom has been launched succesfully. Container ID(${resp.containerId})`);
    return resp;
  },
};

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
Phantombuster	`app`	`app`	This component uses the Phantombuster app.
Agent ID	`agentId`	`string`	Select a value from the drop down menu.
Arguments	`arguments`	`string`	Agent arguments. Must be a JSON string, e.g. `{"key1": "Value 1", "key2": "Value 2"}`
Save Arguments	`saveArguments`	`boolean`	If true, argument will be saved as the default launch options for the agent.
Bonus Argument	`bonusArgument`	`string`	Agent bonus argument. This bonus argument is single-use, it will only be used for the current launch. Must be a JSON string, e.g. `{"key1": "Value 1", "key2": "Value 2"}`
Manual Launch	`manualLaunch`	`boolean`	If set, the agent will be considered as `launched manually`.
Max Instance Count	`maxInstanceCount`	`integer`	If set, the agent will only be launched if the number of already running instances is below the specified number.

Action Authentication#

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

Your API key resides in your Phantombuster Org settings page. This page is also accessible through your navbar's menu, under the label "Org settings". Please notice that for security reasons, you key will only be shown once, on creation. You better copy it in a safe place before refreshing or leaving the page.