Create Note with Cloze API on New Row from MySQL API

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

Trigger workflow on

New Row from the MySQL API

Next, do this

Create Note with the Cloze 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 Cloze 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 Create Note action
1. Connect your Cloze account
2. Configure Unique ID
3. Configure Source
4. Optional- Configure Date
5. Optional- Configure From
6. Optional- Configure Subject
7. Configure Body
8. Optional- Configure Additional 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#

Create Note on Cloze

Description:Creates a note in Cloze. [See the documentation](https://api.cloze.com/api-docs/#!/Content/post_v1_createcontent).

Version:0.0.1

Key:cloze-create-note

View on GitHub

Cloze Overview#

The Cloze API enables you to access and manage your Cloze CRM data programmatically. In Pipedream, you can create powerful, serverless workflows that react to events or run on schedules to automate tasks involving Cloze data. You could synchronize contacts, track communication history, or trigger actions based on updates in Cloze. By leveraging Pipedream's capacity to connect to a myriad of services, you can create multi-step workflows that involve other apps to streamline your business processes and harness the full potential of CRM automation.

Action Code#

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

export default {
  key: "cloze-create-note",
  name: "Create Note",
  description: "Creates a note in Cloze. [See the documentation](https://api.cloze.com/api-docs/#!/Content/post_v1_createcontent).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    uniqueId: {
      type: "string",
      label: "Unique ID",
      description: "A unique identifier for this content record. This will often be the unique Id in an external system so that updates can be matched up with the record in Cloze.",
    },
    source: {
      type: "string",
      label: "Source",
      description: "The source that this content record originally came from (Eg. `todoist.com`). Must be a valid domain.",
    },
    date: {
      type: "string",
      label: "Date",
      description: "When the content should show up in the timeline. Can be a string or a UTC timestamp in ms since the epoch. Eg. `2021-01-01` or `1609459200000`.",
      optional: true,
    },
    from: {
      type: "string",
      label: "From",
      description: "From address for this content record (the address of the person created the record). This can be an email address, phone number, social handle or app link (Eg. `na16.salesforce.com:006j000000Pkp1d`)",
      optional: true,
    },
    subject: {
      type: "string",
      label: "Subject",
      description: "Subject of the communication record.",
      optional: true,
    },
    body: {
      type: "string",
      label: "Body",
      description: "Body text of the communication record.",
    },
    additionalData: {
      type: "object",
      label: "Additional Data",
      description: "Additional details for the note in JSON format. [See the documentation](https://api.cloze.com/api-docs/#!/Content/post_v1_createcontent).",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      app,
      uniqueId,
      date,
      from,
      source,
      subject,
      body,
      additionalData,
    } = this;

    const response = await app.addContentRecord({
      $,
      data: {
        uniqueid: uniqueId,
        date,
        style: "note",
        from,
        source,
        subject,
        body,
        ...additionalData,
      },
    });

    $.export("$summary", "Successfully created note.");

    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
Cloze	`app`	`app`	This component uses the Cloze app.
Unique ID	`uniqueId`	`string`	A unique identifier for this content record. This will often be the unique Id in an external system so that updates can be matched up with the record in Cloze.
Source	`source`	`string`	The source that this content record originally came from (Eg. `todoist.com`). Must be a valid domain.
Date	`date`	`string`	When the content should show up in the timeline. Can be a string or a UTC timestamp in ms since the epoch. Eg. `2021-01-01` or `1609459200000`.
From	`from`	`string`	From address for this content record (the address of the person created the record). This can be an email address, phone number, social handle or app link (Eg. `na16.salesforce.com:006j000000Pkp1d`)
Subject	`subject`	`string`	Subject of the communication record.
Body	`body`	`string`	Body text of the communication record.
Additional Data	`additionalData`	`object`	Additional details for the note in JSON format. See the documentation.

Action Authentication#

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

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