Delete Row with MySQL API on New Collection Events from OpenSea API

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

Trigger workflow on

New Collection Events from the OpenSea API

Next, do this

Delete Row 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 OpenSea 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 Collection Events trigger
1. Connect your OpenSea account
2. Configure timer
3. Configure Contract Address
4. Select a Event Type
Configure the Delete Row action
1. Connect your MySQL account
2. Select a Table
3. Configure Where condition
4. Configure Values
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 Collection Events on OpenSea

Description:Emit new filtered events. [See docs](https://docs.opensea.io/reference/retrieving-asset-events)

Version:0.0.3

Key:opensea-new-collection-events

View on GitHub

OpenSea Overview#

The OpenSea API provides a plethora of endpoints that lets you tap into the rich world of NFTs. From fetching detailed asset information to looking up user-specific items, the possibilities for crafting custom Pipedream workflows are vast. This allows you to automate alerts, synchronize NFT collections with external databases, or even analyze market trends programmatically.

Trigger Code#

import opensea from "../../opensea.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  name: "New Collection Events",
  version: "0.0.3",
  key: "opensea-new-collection-events",
  description:
    "Emit new filtered events. [See docs](https://docs.opensea.io/reference/retrieving-asset-events)",
  dedupe: "greatest",
  type: "source",
  props: {
    opensea,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    contractAddress: {
      type: "string",
      label: "Contract Address",
      description: "Collection contract address",
    },
    eventType: {
      type: "string",
      options: [
        "sales",
        "listings",
      ],
      label: "Event Type",
      description: "OpenSea event type",
    },
  },
  methods: {
    getLastTimestamp() {
      return this.db.get("lastTimestamp");
    },
    setLastTimestamp(ts) {
      this.db.set("lastTimestamp", ts);
    },
  },
  async run() {
    const eventType = this.eventType === "sales"
      ? "successful"
      : "created";
    const lastTimestamp = this.getLastTimestamp();
    let cursor = null;
    do {
      const resp = await this.opensea.retrieveEvents({
        contract: this.contractAddress,
        eventType,
        occurredAfter: lastTimestamp,
        cursor,
      });
      resp.asset_events.forEach((event) => {
        this.$emit(event, {
          id: event.id,
          summary: `${event.asset.name} ${this.eventType} event`,
          ts: +new Date(event.created_date),
        });
      });
      if (!cursor && resp.asset_events.length > 0) {
        const ts = Math.floor(new Date(resp.asset_events[0].created_date).getTime() / 1000);
        this.setLastTimestamp(ts);
      }
      cursor = resp.next;
    } while (lastTimestamp && cursor);
  },
};

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
OpenSea	`opensea`	`app`	This component uses the OpenSea app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Contract Address	`contractAddress`	`string`	Collection contract address
Event Type	`eventType`	`string`	Select a value from the drop down menu:`saleslistings`

Trigger Authentication#

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

To connect your OpenSea account to Pipedream, request an API key from OpenSea here.

About OpenSea#

Discover, collect, and sell extraordinary NFTs. OpenSea is the world's first and largest NFT marketplace.

Action#

Delete Row on MySQL

Description:Delete an existing row. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/delete.html)

Version:2.0.5

Key:mysql-delete-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.

Action Code#

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

export default {
  key: "mysql-delete-row",
  name: "Delete Row",
  description: "Delete an existing row. [See the docs here](https://dev.mysql.com/doc/refman/8.0/en/delete.html)",
  type: "action",
  version: "2.0.5",
  props: {
    mysql,
    table: {
      description: "The table to delete a row from",
      propDefinition: [
        mysql,
        "table",
      ],
    },
    condition: {
      propDefinition: [
        mysql,
        "whereCondition",
      ],
    },
    values: {
      propDefinition: [
        mysql,
        "whereValues",
      ],
    },
  },
  async run({ $ }) {
    const {
      table,
      condition,
      values,
    } = this;

    const numberOfQuestionMarks = condition?.match(/\?/g)?.length;

    if (!numberOfQuestionMarks) {
      throw new Error("No valid condition provided. At least one question mark character ? must be provided.");
    }

    if (!Array.isArray(values)) {
      throw new Error("No valid values provided. The values property must be an array.");
    }

    if (values.length !== numberOfQuestionMarks) {
      throw new Error("The number of values provided does not match the number of question marks ? in the condition.");
    }

    const result = await this.mysql.deleteRows({
      table,
      condition,
      values,
    });

    $.export("$summary", `Successfully deleted ${result.affectedRows} row(s) from table ${table}`);

    return result;
  },
};

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.
Table	`table`	`string`	Select a value from the drop down menu.
Where condition	`condition`	`string`	In this expression you can write your own conditions (eg. `column1 = ? or column2 = ?`). Depending on the number of `?` symbols likewise you need to add the same number of values.
Values	`values`	`string[]`	This is the list of values that will match every `?` symbol in the where expression. If you want to build yourself the values (eg. `{{["string1", "string2"]}}`)

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.