Start Scraping with Scrape-It.Cloud API on Ticket Closed (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for Scrape-It.Cloud, Zendesk and 2,400+ other apps remarkably fast.

Trigger workflow on

Ticket Closed (Instant) from the Zendesk API

Next, do this

Start Scraping with the Scrape-It.Cloud 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 Zendesk trigger and Scrape-It.Cloud action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Ticket Closed (Instant) trigger
1. Connect your Zendesk account
2. Select a Trigger Category ID
3. Optional- Configure Custom Subdomain
4. Optional- Select one or more Fields
5. Optional- Configure JSON Body
Configure the Start Scraping action
1. Connect your Scrape-It.Cloud account
2. Configure URL
3. Optional- Configure Headers
4. Optional- Configure Block Resources
5. Optional- Configure Block URLs
6. Optional- Configure Wait
7. Optional- Configure Wait For
8. Optional- Configure Screenshot
9. Optional- Configure JS Scenario
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#

Ticket Closed (Instant) on Zendesk

Description:Emit new event when a ticket has changed to closed status

Version:0.2.2

Key:zendesk-ticket-closed

View on GitHub

Zendesk Overview#

The Zendesk API enables seamless integration of Zendesk's customer service platform with your existing business processes and third-party applications. By leveraging this API with Pipedream, you can automate ticket tracking, sync customer data, escalate issues, and streamline communication across multiple channels. This can significantly increase efficiency, accelerate response times, and enhance the overall customer experience. Automations can range from simple notifications to complex workflows involving data transformation and multi-step actions across various services.

Trigger Code#

import common from "../common/ticket.mjs";

export default {
  ...common,
  name: "Ticket Closed (Instant)",
  key: "zendesk-ticket-closed",
  type: "source",
  description: "Emit new event when a ticket has changed to closed status",
  version: "0.2.2",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Closed Webhook";
    },
    getTriggerTitle() {
      return "Ticket Closed Trigger";
    },
    getTriggerConditions() {
      return {
        all: [
          {
            field: "update_type",
            value: "Change",
          },
          {
            field: "status",
            operator: "value",
            value: "closed",
          },
        ],
      };
    },
  },
};

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
Zendesk	`app`	`app`	This component uses the Zendesk app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
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.
Trigger Category ID	`categoryId`	`string`	Select a value from the drop down menu.
Custom Subdomain	`customSubdomain`	`string`	For Enterprise Zendesk accounts: optionally specify the subdomain to use. This will override the subdomain that was provided when connecting your Zendesk account to Pipedream. For example, if you Zendesk URL is https://examplehelp.zendesk.com, your subdomain is `examplehelp`
Fields	`fields`	`string[]`	Select a value from the drop down menu.
JSON Body	`jsonBody`	`string`	Custom JSON Body of the incoming payload. Setting `jsonBody` will overwrite the `fields` prop

Trigger Authentication#

Zendesk uses OAuth authentication. When you connect your Zendesk account, Pipedream will open a popup window where you can sign into Zendesk and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Zendesk API.

Pipedream requests the following authorization scopes when you connect your account:

triggers:writewebhooks:writereadtickets:writetickets:readusers:writeorganizations:readorganizations:write

About Zendesk#

Zendesk is award-winning customer service software trusted by 200K+ customers. Make customers happy via text, mobile, phone, email, live chat, social media.

Action#

Start Scraping on Scrape-It.Cloud

Description:Initiate the scraping process for a specific endpoint. [See the documentation here](https://scrape-it.cloud/docs/api-features/basic-request).

Version:0.0.1

Key:scrape_it_cloud-start-scraping

View on GitHub

Scrape-It.Cloud Overview#

The Scrape-It.Cloud API allows you to automate the extraction of data from websites. It can parse, scrape, and retrieve content without the need for manual intervention. With this API on Pipedream, you can build workflows that trigger on various events and use the scraped data for numerous applications like data analysis, lead generation, and content aggregation.

Action Code#

import app from "../../scrape_it_cloud.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "scrape_it_cloud-start-scraping",
  name: "Start Scraping",
  description: "Initiate the scraping process for a specific endpoint. [See the documentation here](https://scrape-it.cloud/docs/api-features/basic-request).",
  type: "action",
  version: "0.0.1",
  props: {
    app,
    url: {
      type: "string",
      label: "URL",
      description: "Specify the URL of the web page you would like to scrape.",
    },
    headers: {
      type: "object",
      label: "Headers",
      description: "Specify custom HTTP headers to be passed to the request. For example, in order to override the User-Agent header, use `User-Agent` as a key and `Teapot` as a value.",
      optional: true,
    },
    blockResources: {
      type: "boolean",
      label: "Block Resources",
      description: "By default Scrape-it.cloud do not block images and CSS in the scraped page. To speed up requests and block images and CSS set this parameter value to true.",
      optional: true,
    },
    blockUrls: {
      type: "string[]",
      label: "Block URLs",
      description: "If you want to block some resources except images and CSS, for example, analytics scripts you can add part of the urls to be blocked. Follow [Blocking URLs](https://scrape-it.cloud/docs/api-features/blocking-urls) page to get more information.",
      optional: true,
    },
    wait: {
      type: "integer",
      label: "Wait",
      description: "Some websites may use javascript frameworks that may require a few extra seconds to load their content. This parameters specifies the time in milliseconds to wait for the website. Recommended values are in the interval `5000` - `10000`.",
      optional: true,
    },
    waitFor: {
      type: "string",
      label: "Wait For",
      description: "Specify a CSS selector and the API will wait 30 seconds until the selector appears.",
      optional: true,
    },
    screenshot: {
      type: "boolean",
      label: "Screenshot",
      description: "If you want to get a screenshot of the page you want to scrape, set screenshot parameter value to `true`.",
      optional: true,
    },
    jsScenario: {
      type: "string[]",
      label: "JS Scenario",
      description: "If you want to do some acts on the pages you want to scrape, for example, go to the next one, set JavaScript scenario to API call. Follow [JavaScript Execution](https://scrape-it.cloud/docs/api-features/javascript-execution) page to get more information.",
      optional: true,
    },
  },
  methods: {
    scrape(args = {}) {
      return this.app.post({
        path: "/scrape",
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      url, headers, blockResources, blockUrls, wait, waitFor, screenshot, jsScenario,
    } = this;

    const response = await this.scrape({
      step,
      data: {
        url,
        headers: utils.parse(headers),
        block_resources: blockResources,
        block_urls: utils.parseArray(blockUrls),
        wait,
        wait_for: waitFor,
        screenshot,
        js_scenario: utils.parseArray(jsScenario)?.map(utils.parse),
      },
    });

    step.export("$summary", `Successfully scraped ${url}.`);

    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
Scrape-It.Cloud	`app`	`app`	This component uses the Scrape-It.Cloud app.
URL	`url`	`string`	Specify the URL of the web page you would like to scrape.
Headers	`headers`	`object`	Specify custom HTTP headers to be passed to the request. For example, in order to override the User-Agent header, use `User-Agent` as a key and `Teapot` as a value.
Block Resources	`blockResources`	`boolean`	By default Scrape-it.cloud do not block images and CSS in the scraped page. To speed up requests and block images and CSS set this parameter value to true.
Block URLs	`blockUrls`	`string[]`	If you want to block some resources except images and CSS, for example, analytics scripts you can add part of the urls to be blocked. Follow Blocking URLs page to get more information.
Wait	`wait`	`integer`	Some websites may use javascript frameworks that may require a few extra seconds to load their content. This parameters specifies the time in milliseconds to wait for the website. Recommended values are in the interval `5000` - `10000`.
Wait For	`waitFor`	`string`	Specify a CSS selector and the API will wait 30 seconds until the selector appears.
Screenshot	`screenshot`	`boolean`	If you want to get a screenshot of the page you want to scrape, set screenshot parameter value to `true`.
JS Scenario	`jsScenario`	`string[]`	If you want to do some acts on the pages you want to scrape, for example, go to the next one, set JavaScript scenario to API call. Follow JavaScript Execution page to get more information.