Delete Record with Knack API on New or Updated Workflow from Skyvern API

Pipedream makes it easy to connect APIs for Knack, Skyvern and 2,800+ other apps remarkably fast.

Trigger workflow on

New or Updated Workflow from the Skyvern API

Next, do this

Delete Record with the Knack 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 Skyvern trigger and Knack action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New or Updated Workflow trigger
1. Connect your Skyvern account
2. Configure timer
Configure the Delete Record action
1. Connect your Knack account
2. Configure Object Key
3. Configure Record ID
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 or Updated Workflow on Skyvern

Description:Emit new event when a workflow is created or updated in Skyvern.

Version:0.0.1

Key:skyvern-new-or-updated-workflow

View on GitHub

Trigger Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import skyvern from "../../skyvern.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  key: "skyvern-new-or-updated-workflow",
  name: "New or Updated Workflow",
  description: "Emit new event when a workflow is created or updated in Skyvern.",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    skyvern,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  methods: {
    _getLastDate() {
      return this.db.get("lastDate") || 0;
    },
    _setLastDate(lastDate) {
      this.db.set("lastDate", lastDate);
    },
    async emitEvent(maxResults = false) {
      const lastDate = this._getLastDate();

      const response = this.skyvern.paginate({
        fn: this.skyvern.listWorkflows,
        maxResults,
      });

      let responseArray = [];
      for await (const item of response) {
        if (Date.parse(item.modified_at) <= lastDate) break;
        responseArray.push(item);
      }

      if (responseArray.length) {
        this._setLastDate(responseArray[0].modified_at);
      }

      for (const item of responseArray.reverse()) {
        this.$emit(item, {
          id: `${item.modified_at}-${item.workflow_permanent_id}`,
          summary: `New Workflow ${item.version === 1
            ? "Created"
            : "Updated"}: ${item.title}`,
          ts: Date.parse(item.modified_at),
        });
      }
    },
  },
  hooks: {
    async deploy() {
      await this.emitEvent(25);
    },
  },
  async run() {
    await this.emitEvent();
  },
  sampleEmit,
};

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
Skyvern	`skyvern`	`app`	This component uses the Skyvern app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`

Trigger Authentication#

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

About Skyvern#

Automate Browser-Based Workflows with AI

Action#

Delete Record on Knack

Description:Delete a Record for a Knack object [(See docs here)](https://docs.knack.com/docs/object-based-delete)

Version:0.0.1

Key:knack-delete-record

View on GitHub

Knack Overview#

The Knack API allows for robust interactions with your Knack database, enabling automation of data entry, retrieval, updates, and deletion. With Pipedream, you can leverage these capabilities to create seamless workflows that react to events in real-time, sync data across platforms, and enhance your database management without manual intervention. Think less about CRUD operations and more about the magic of connecting your Knack data to the digital tools ecosystem.

Action Code#

import base from "../common/base.mjs";
import { recordId } from "../common/props.mjs";

export default {
  ...base,
  key: "knack-delete-record",
  name: "Delete Record",
  description:
    "Delete a Record for a Knack object [(See docs here)](https://docs.knack.com/docs/object-based-delete)",
  version: "0.0.1",
  type: "action",
  props: {
    ...base.props,
    recordId,
  },
  methods: {
    getBaseParams() {
      return {
        objectKey: this.objectKey,
        recordId: this.recordId,
      };
    },
  },
  async run({ $ }) {
    const response = await this.knack.deleteRecord($, this.getBaseParams());

    $.export("$summary", "Deleted record successfully");

    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Knack	`knack`	`app`	This component uses the Knack app.
Object Key	`objectKey`	`string`	The key of the object which this record belongs to. See the Knack API docs for more information.
Record ID	`recordId`	`string`	The ID of the record. See the Knack API docs for more information.

Action Authentication#

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

Object-based requests require at least two headers: an application ID - to identify to our servers the app whose records you are requesting - and an API key (which is specific to each app) to authenticate the request. See docs