Delete a single record with Data Stores API on New Task Completed from iLovePDF API

Pipedream makes it easy to connect APIs for Data Stores, iLovePDF and 2,200+ other apps remarkably fast.

Trigger workflow on

New Task Completed from the iLovePDF API

Next, do this

Delete a single record with the Data Stores 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 iLovePDF trigger and Data Stores action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Task Completed trigger
1. Connect your iLovePDF account
2. Configure timer
3. Optional- Select a Tool
Configure the Delete a single record action
1. Connect your Data Stores account
2. Configure Data Store
3. Select a Key
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 Task Completed on iLovePDF

Description:Emit new event for each new task. [See the documentation](https://developer.ilovepdf.com/docs/api-reference#task)

Version:0.0.1

Key:ilovepdf-new-task-completed

View on GitHub

iLovePDF Overview#

The iLovePDF API lets you automate PDF processing tasks like merging, splitting, compressing, and converting PDFs to other formats. iLovePDF's robust functionality can be harnessed in Pipedream workflows, which may include handling PDFs generated from various triggers, processing them as needed, and connecting to other services for storage, data extraction, or further actions based on the transformed PDFs.

Trigger Code#

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

export default {
  key: "ilovepdf-new-task-completed",
  name: "New Task Completed",
  description: "Emit new event for each new task. [See the documentation](https://developer.ilovepdf.com/docs/api-reference#task)",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    ilovepdf,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    tool: {
      propDefinition: [
        ilovepdf,
        "tool",
      ],
      description: "If specified, events will only be emitted for tasks with this tool",
      optional: true,
    },
  },
  methods: {
    _setSavedItems(value) {
      this.db.set("tasks", value);
    },
    _getSavedItems() {
      return this.db.get("tasks") ?? [];
    },
    async getAndProcessItems() {
      const { token } = await this.ilovepdf.getAuthToken();

      const savedItems = this._getSavedItems();
      const tasks = await this.ilovepdf.listTasks({
        token,
        tool: this.tool,
      });

      tasks?.filter?.(({ task }) => !savedItems.includes(task)).forEach((task) => {
        const ts = Date.now();
        this.$emit(task, {
          id: task.task,
          summary: `New task (${task.tool}) - ${task.file_number} file${task.file_number == 1
            ? ""
            : "s"}`,
          ts,
        });
        savedItems.push(task.task);
      });

      this._setSavedItems(savedItems);
    },
  },
  hooks: {
    async deploy() {
      await this.getAndProcessItems();
    },
  },
  async run() {
    await this.getAndProcessItems();
  },
};

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
iLovePDF	`ilovepdf`	`app`	This component uses the iLovePDF app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Tool	`tool`	`string`	Select a value from the drop down menu:`compressmergesplitpdfjpgimagepdfunlockpagenumberwatermarkofficepdfrepairrotateprotectpdfavalidatepdfahtmlpdfextract`

Trigger Authentication#

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

Sign in to your iLovePDF developer account. Navigate to Projects, and you will find your Public Key and Secret Key under API Keys.

About iLovePDF#

iLovePDF is an online service to work with PDF files completely free and easy to use. Merge PDF, split PDF, compress PDF, office to PDF, and more.

Action#

Delete a single record on Data Stores

Description:Delete a single record in your [Pipedream Data Store](https://pipedream.com/data-stores/).

Version:0.0.8

Key:data_stores-delete-single-record

View on GitHub

Data Stores Overview#

Data Stores are a key-value store that allow you to persist state and share data across workflows. You can perform CRUD operations, enabling dynamic data management within your serverless architecture. Use it to save results from API calls, user inputs, or interim data; then read, update, or enrich this data in subsequent steps or workflows. Data Stores simplify stateful logic and cross-workflow communication, making them ideal for tracking process statuses, aggregating metrics, or serving as a simple configuration store.

Action Code#

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

export default {
  key: "data_stores-delete-single-record",
  name: "Delete a single record",
  description: "Delete a single record in your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.8",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    key: {
      propDefinition: [
        app,
        "key",
        ({ dataStore }) => ({
          dataStore,
        }),
      ],
      description: "Select the key for the record you'd like to delete, or enter one manually.",
    },
  },
  async run({ $ }) {
    const record = await this.dataStore.get(this.key);

    if (record) {
      await this.dataStore.delete(this.key);
      $.export("$summary", `Successfully deleted the record for key, \`${this.key}\`.`);
      return record;
    }

    $.export("$summary", `No record found for key, \`${this.key}\`. No data was deleted.`);
  },
};

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
Data Stores	`app`	`app`	This component uses the Data Stores app.
Data Store	`dataStore`	`data_store`	Select an existing Data Store or create a new one.
Key	`key`	`string`	Select a value from the drop down menu.