Run Node Code with Node API on New Media Processing Finished (Instant) from ContentGroove API

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

Trigger workflow on

New Media Processing Finished (Instant) from the ContentGroove 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 ContentGroove 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 Media Processing Finished (Instant) trigger
1. Connect your ContentGroove 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 Media Processing Finished (Instant) on ContentGroove

Description:Emit new event when a media is done processing by ContentGroove.

Version:0.0.1

Key:contentgroove-new-media-processing-finished-instant

View on GitHub

ContentGroove Overview#

The ContentGroove API offers functionality for managing and automating content-related tasks. Within Pipedream, you can harness this API to create workflows that trigger on various events, process data, and connect to other services. Think about automating content dissemination, analyzing audience engagement, or syncing content across platforms. With Pipedream's serverless architecture, these workflows can run on demand, on a schedule, or in response to specific events, providing a powerful way to streamline your content management processes.

Trigger Code#

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

export default {
  key: "contentgroove-new-media-processing-finished-instant",
  name: "New Media Processing Finished (Instant)",
  description: "Emit new event when a media is done processing by ContentGroove.",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    contentgroove,
    http: "$.interface.http",
    db: "$.service.db",
  },
  methods: {
    emitData(data) {
      this.$emit(data, {
        id: data.id,
        summary: `Media ${data.attributes.name} processed.`,
        ts: Date.parse(data.attributes.created_at),
      });
    },
  },
  hooks: {
    async deploy() {
      const { data } = await this.contentgroove.listProcessedMedia({
        params: {
          size: 25,
          sort: "-createdAt",
        },
      });

      data.reverse()
        .forEach((mediaItem) => this.emitData(mediaItem));
    },
    async activate() {
      const response = await this.contentgroove.createWebhook({
        data: {
          data: {
            attributes: {
              url: this.http.endpoint,
              subscribed_events: [
                "media.processing_finished",
              ],
            },
          },
        },
      });
      this.db.set("webhookId", response.data?.id);
    },
    async deactivate() {
      const webhookId = this.db.get("webhookId");
      await this.contentgroove.deleteWebhook(webhookId);
    },
  },
  async run({ body }) {
    const { payload: { data } } = body;
    this.emitData(data);
  },
};

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
ContentGroove	`contentgroove`	`app`	This component uses the ContentGroove app.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

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

About ContentGroove#

Create video highlights using generative AI.

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