Run Node Code with Node API on New my article from Dev.to API

Pipedream makes it easy to connect APIs for Node, Dev.to and 1,600+ other apps remarkably fast.

Trigger workflow on

New my article from the Dev.to API

Next, do this

Run Node Code with the Node API

No credit card required

▶

Watch us build a workflow

7 min

Watch now ➜

Trusted by 750,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Dev.to 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 New my article trigger
1. Configure Timer
2. Connect your Dev.to account
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#

New my article on Dev.to

Description:Emit new event for each new article published on your Dev.to account

Version:0.0.3

Key:dev_to-my-articles

View on GitHub

Dev.to Overview#

With the Dev.to API, you can build applications that:

Stand out from the crowd on Dev.to by customizing your profile page
Build a Dev.to extension that helps other developers be more productive
Develop a bot that helps moderation on Dev.to
Get notified whenever a new article is published on a certain topic
And much more!

Trigger Code#

import devTo from "../../dev_to.app.mjs";
import moment from "moment";
import common from "../common.mjs";

export default {
  name: "New my article",
  key: "dev_to-my-articles",
  description: "Emit new event for each new article published on your Dev.to account",
  type: "source",
  version: "0.0.3",
  props: {
    ...common.props,
    devTo,
  },
  dedupe: "greatest",
  async run({ $ }) {
    const data = await this.devTo.getMyArticles($, {
      params: {
        per_page: 1000,
        top: 1,
      },
    });

    data.forEach((event) => {
      this.$emit(event, {
        id: event.id,
        ts: moment(event.published_timestamp).valueOf(),
        summary: event.title,
      });
    });
  },
};

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
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Timer	`timer`	`$.interface.timer`	How often to poll Dev.to for new articles
Dev.to	`devTo`	`app`	This component uses the Dev.to app.

Trigger Authentication#

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

Generate an API key at https://dev.to/settings/account

About Dev.to#

Where programmers share ideas and help each other grow.

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

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;
  },
};