Base64 Decode String with Helper Functions API on New Deployment from Vercel API

Pipedream makes it easy to connect APIs for Helper Functions, Vercel and 2,400+ other apps remarkably fast.

Trigger workflow on

New Deployment from the Vercel API

Next, do this

Base64 Decode String with the Helper Functions 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 Vercel trigger and Helper Functions action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Deployment trigger
1. Connect your Vercel account
2. Configure timer
3. Optional- Select a Project
4. Optional- Select a State
5. Optional- Configure Max
Configure the Base64 Decode String action
1. Connect your Helper Functions account
2. Configure 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 Deployment on Vercel

Description:Emit new event when a deployment is created

Version:0.0.3

Key:vercel_token_auth-new-deployment

View on GitHub

Vercel Overview#

The Vercel API empowers developers to automate, manage, and interact with their Vercel projects and deployments directly through code. With the Vercel API on Pipedream, you can harness the power of serverless functions to create dynamic and responsive workflows. Automate deployment processes, sync deployment statuses with other tools, trigger notifications based on deployment events, or manage your domains and aliases—all within the seamless integration landscape of Pipedream.

Trigger Code#

import vercelTokenAuth from "../../vercel_token_auth.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "vercel_token_auth-new-deployment",
  name: "New Deployment",
  description: "Emit new event when a deployment is created",
  version: "0.0.3",
  type: "source",
  dedupe: "unique",
  props: {
    vercelTokenAuth,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    project: {
      propDefinition: [
        vercelTokenAuth,
        "project",
      ],
    },
    state: {
      propDefinition: [
        vercelTokenAuth,
        "state",
      ],
    },
    max: {
      propDefinition: [
        vercelTokenAuth,
        "max",
      ],
    },
  },
  hooks: {
    async deploy() {
      await this.processEvent(10);
    },
  },
  methods: {
    _getFrom() {
      return this.db.get("from");
    },
    _setFrom(from) {
      this.db.set("from", from);
    },
    generateMeta(deployment) {
      const {
        uid,
        name,
        state,
        created,
      } = deployment;
      return {
        id: uid,
        summary: `${name ?? uid} ${state}`,
        ts: created,
      };
    },
    async processEvent(max) {
      const params = {
        projectId: this.project,
        state: this.state,
      };
      let from = this._getFrom();
      if (from) {
        params.from = from;
      }
      const deployments = await this.vercelTokenAuth.listDeployments(params, max);
      for (const deployment of deployments) {
        if (!from || deployment.created > from) {
          from = deployment.created;
        }
        const meta = this.generateMeta(deployment);
        this.$emit(deployment, meta);
      }
      this._setFrom(from);
    },
  },
  async run() {
    await this.processEvent(this.max);
  },
};

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
Vercel	`vercelTokenAuth`	`app`	This component uses the Vercel app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Project	`project`	`string`	Select a value from the drop down menu.
State	`state`	`string`	Select a value from the drop down menu:`BUILDINGERRORINITIALIZINGQUEUEDREADYCANCELED`
Max	`max`	`integer`	Maximum number of results to return

Trigger Authentication#

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

Vercel encourages users to connect their account with Pipedream using Personal Access Tokens, which can be managed in your Vercel account here.

To learn more, refer to Vercel's documentation.

About Vercel#

Vercel is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration.

Action#

Base64 Decode String on Helper Functions

Description:Accepts a base64-encoded string, returns a decoded UTF-8 string

Version:0.1.1

Key:helper_functions-base64-decode-string

View on GitHub

Helper Functions Overview#

The Helper Functions app on Pipedream is a set of pre-built functions that streamline common tasks in your workflows. It acts like a Swiss Army knife for developers, providing essential tools such as format conversion, date manipulation, and text processing. By leveraging these functions, you can reduce the boilerplate code needed for routine operations, speeding up the development of intricate automations. The Helper Functions API can be a game changer when it comes to tasks like parsing dates in user-friendly formats, encoding and decoding data, or generating UUIDs, making them more efficient and less error-prone.

Action Code#

// legacy_hash_id: a_0Mio28
import helper_functions from "../../helper_functions.app.mjs";

export default {
  key: "helper_functions-base64-decode-string",
  name: "Base64 Decode String",
  description: "Accepts a base64-encoded string, returns a decoded UTF-8 string",
  version: "0.1.1",
  type: "action",
  props: {
    helper_functions,
    data: {
      type: "string",
    },
  },
  async run({ $ }) {
    const buffer = Buffer.from(this.data, "base64");
    $.export("data", buffer.toString("utf8"));
  },
};