# Sharing code across workflows

Pipedream provides two ways to share code across workflows:

  • Create an action. Actions are reusable steps. When you author an action, you can add it to your workflow like you would other actions, by clicking the + button below any step. Watch this video to learn how to publish actions.
  • Create your own npm package. If you need to run the same Node.js code in multiple workflows, you can publish that code as an npm package. We'll walk you through that process below.

# Publishing your own npm package

# The short version

  1. Follow this guide to publish your code as an npm package. You can see the code for an example package here, @dylburger/pd.
  2. In any workflow, you can require code provided by your package.
// require the random function from this example package
const { random } = require("@dylburger/pd");

# Step by step

This guide will walk you through how to create and publish an npm package. You can require the code from this package in any Pipedream workflow.

  1. Open the publishing guide from npm. Follow steps 1 - 7.
  2. Create an index.js file within your package's directory with the following contents:
function random() {
  return Math.random();

// Read https://www.sitepoint.com/understanding-module-exports-exports-node-js/
// for more information on this syntax
module.exports = {

The random function is just an example - you can keep this code or replace it with any function or code you'd like to use on Pipedream.

  1. You'll need to publish a public package to use it on Pipedream. Make sure to review your code for any sensitive information.
  2. Follow the instructions in the Publishing scoped public packages section of the npm guide to publish your package to npm's registry.
  3. In a Pipedream workflow, require the random function from the example, or run the other code provided by your package:
// require the random function
const { random } = require("@your-username/your-package");
  1. If you need to add more code to your package, add it to your index.js file, increment the version in your package.json file, and publish your package again.

Still have questions?

Please reach out if this doc didn't answer your question. We're happy to help!