Send GET Request with HTTP / Webhook API on New Task Completed from iLovePDF API

Pipedream makes it easy to connect APIs for HTTP / Webhook, iLovePDF and 2,400+ other apps remarkably fast.

Trigger workflow on

New Task Completed from the iLovePDF API

Next, do this

Send GET Request with the HTTP / Webhook 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 HTTP / Webhook 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 Send GET Request action
1. Connect your HTTP / Webhook account
2. Configure HTTP Request Configuration
3. Optional- Configure Include Response Headers
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#

Send GET Request on HTTP / Webhook

Description:Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

Version:1.1.1

Key:http-get-request

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Action Code#

import customRequest from "../custom-request/custom-request.mjs";

export default {
  ...customRequest,
  key: "http-get-request",
  name: "Send GET Request",
  description: "Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.",
  type: "action",
  version: "1.1.1",
  props: {
    ...customRequest.props,
    /* eslint-disable-next-line pipedream/props-label,pipedream/props-description */
    httpRequest: {
      ...customRequest.props.httpRequest,
      default: {
        method: "GET",
      },
    },
  },
};

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
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.
HTTP Request Configuration	`httpRequest`	`http_request`
Include Response Headers	`includeHeaders`	`boolean`	Optionally export the full response headers

Action Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

More Ways to Connect HTTP / Webhook + iLovePDF#

Other Popular Integrations#

Process Files with iLovePDF API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + iLovePDF

Try it

Process Files with iLovePDF API on New Requests from HTTP / Webhook API

HTTP / Webhook + iLovePDF

Try it

Process Files with iLovePDF API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + iLovePDF

Try it

Send any HTTP Request with HTTP / Webhook API on New Task Completed from iLovePDF API

iLovePDF + HTTP / Webhook

Try it

Send POST Request with HTTP / Webhook API on New Task Completed from iLovePDF API

iLovePDF + HTTP / Webhook

Try it

Popular Triggers#

New Task Completed from the iLovePDF API

Emit new event for each new task. See the documentation

Try it

New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Try it

New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it