Run Node Code with Node API on Item Position Changed from Miro Developer App API

Pipedream makes it easy to connect APIs for Node, Miro Developer App and 2,400+ other apps remarkably fast.

Trigger workflow on

Item Position Changed from the Miro Developer App API

Next, do this

Run Node Code with the Node 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 Miro Developer App trigger and Node action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Item Position Changed trigger
1. Connect your Miro Developer App account
2. Configure timer
3. Optional- Configure Team ID
4. Select a Board ID
Configure the Run Node Code action
1. Connect your Node account
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#

Item Position Changed on Miro Developer App

Description:Emit new event when an item's position changes in a Miro Custom App.

Version:0.0.1

Key:miro_custom_app-item-position-changed

View on GitHub

Miro Developer App Overview#

The Miro Developer App API lets you extend the functionality of Miro, an online collaborative whiteboarding platform. On Pipedream, you can automate interactions with Miro boards, such as creating or updating content, and extracting data for reporting or integration purposes. This can streamline collaboration and project management by automating repetitive tasks and connecting Miro with other tools and services.

Trigger Code#

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

export default {
  ...common,
  key: "miro_custom_app-item-position-changed",
  name: "Item Position Changed",
  description: "Emit new event when an item's position changes in a Miro Custom App.",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    teamId: {
      propDefinition: [
        common.props.miro,
        "teamId",
      ],
    },
    boardId: {
      propDefinition: [
        common.props.miro,
        "boardId",
        ({ teamId }) => ({
          teamId,
        }),
      ],
    },
  },
  methods: {
    ...common.methods,
    _getPositions() {
      return this.db.get("positions") || {};
    },
    _setPositions(positions) {
      this.db.set("positions", positions);
    },
    generateMeta(item) {
      const ts = Date.parse(item.modifiedAt);
      return {
        id: `${item.id}-${ts}`,
        summary: `Item ${item.id} position changed`,
        ts,
      };
    },
  },
  async run() {
    const positions = this._getPositions();
    const newPositions = {};
    const items = this.paginate({
      resourceFn: this.miro.listItems,
      args: {
        boardId: this.boardId,
      },
    });
    for await (const item of items) {
      const position = JSON.stringify(item.position);
      if (positions[item.id] && positions[item.id] !== position) {
        const meta = this.generateMeta(item);
        this.$emit(item, meta);
      }
      newPositions[item.id] = position;
    }

    this._setPositions(newPositions);
  },
};

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
Miro Developer App	`miro`	`app`	This component uses the Miro Developer App app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Team ID	`teamId`	`string`	The `team_id` for which you want to retrieve the list of boards.
Board ID	`boardId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

Connecting a Miro app to Pipedream

With this connection you can build your own Miro App and connect it to Pipedream.

Follow the REST API app quickstart guide on Miro to create an app that can interact with your Miro team over the Miro REST API.

This will produce a unique Access Token for accessing your boards. Once you have finished those steps, paste that Access Token in to the field below.

About Miro Developer App#

The Visual Collaboration Platform for Every Team.

Action#

Run Node Code on Node

Description:Write custom Node.js code and use any of the 400k+ npm packages available. Refer to the [Pipedream Node docs](https://pipedream.com/docs/code/nodejs) to learn more.

Version:0.0.2

Key:node-run-node-code

View on GitHub

Node Overview#

Develop, run and deploy your Node.js code in Pipedream workflows, using it between no-code steps, with connected accounts, or integrate Data Stores and File Stores.

This includes installing NPM packages, within your code without having to manage a package.json file or running npm install.

Below is an example of installing the axios package in a Pipedream Node.js code step. Pipedream imports the axios package, performs the API request, and shares the response with subsequent workflow steps:

Action Code#

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

export default {
  name: "Run Node Code",
  version: "0.0.2",
  key: "node-run-node-code",
  description: "Write custom Node.js code and use any of the 400k+ npm packages available. Refer to the [Pipedream Node docs](https://pipedream.com/docs/code/nodejs) to learn more.",
  props: {
    node,
  },
  type: "action",
  methods: {},
  async run({
    steps, $,
  }) {
    // Return data to use it in future steps
    return steps.trigger.event;
  },
};