Create Customer with Chaser API on New event when the content of the URL changes. from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Create Customer with the Chaser 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 HTTP / Webhook trigger and Chaser action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New event when the content of the URL changes. trigger
1. Connect your HTTP / Webhook account
2. Configure Watching timer
3. Configure HTTP Request Configuration
4. Configure Emit body only
5. Configure Emit as array
Configure the Create Customer action
1. Connect your Chaser account
2. Configure External ID
3. Configure Company Name
4. Optional- Configure First Name
5. Optional- Configure Last Name
6. Optional- Configure Email Address
7. Optional- Configure Phone Number
8. Optional- Configure Additional Options
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 event when the content of the URL changes. on HTTP / Webhook

Description:Emit new event when the content of the URL changes.

Version:0.0.2

Key:http-watch-url

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.

Trigger Code#

import http from "../../http.app.mjs";
import hash from "object-hash";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "http-watch-url",
  name: "New event when the content of the URL changes.",
  description: "Emit new event when the content of the URL changes.",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  props: {
    http,
    timer: {
      type: "$.interface.timer",
      label: "Watching timer",
      description: "How often to watch the URL.",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    httpRequest: {
      type: "http_request",
      label: "HTTP Request Configuration",
      description: "HTTP Request Configuration",
      default: {
        method: "GET",
      },
    },
    emitBodyOnly: {
      label: "Emit body only",
      description: "If set as true the emitted item will contain only the response body, otherwise, it will include the request status code.",
      type: "boolean",
      default: true,
    },
    emitAsArray: {
      label: "Emit as array",
      description: "If the request responds with an array, this source will emit changes individually for each item of the array.",
      type: "boolean",
      default: false,
    },
  },
  methods: {
    getMeta(data, status) {
      if (this.emitBodyOnly) {
        return data;
      }
      return {
        data,
        status,
      };
    },
    emitArray(event, response) {
      if (!Array.isArray(response.data)) {
        return this.emitAny(event, response);
      }
      for (const item of response.data) {
        const meta = this.getMeta(item, response.status);
        this.emit(event, meta);
      }
    },
    emitAny(event, response) {
      const meta = this.getMeta(response.data, response.status);
      this.emit(event, meta);
    },
    emit(event, meta) {
      const ts = event.timestamp || Math.round(Date.now() / 1000);
      this.$emit(meta, {
        id: hash(meta),
        summary: `Requested at ${ts}`,
        ts,
      });
    },
  },
  async run(event) {
    const response = await this.httpRequest.execute();
    if (this.emitAsArray) {
      this.emitArray(event, response);
    } else {
      this.emitAny(event, response);
    }
  },
};

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
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.
Watching timer	`timer`	`$.interface.timer`	How often to watch the URL.
HTTP Request Configuration	`httpRequest`	`http_request`	HTTP Request Configuration
Emit body only	`emitBodyOnly`	`boolean`	If set as true the emitted item will contain only the response body, otherwise, it will include the request status code.
Emit as array	`emitAsArray`	`boolean`	If the request responds with an array, this source will emit changes individually for each item of the array.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

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

Action#

Create Customer on Chaser

Description:Creates a new customer in Chaser. [See the documentation](https://openapi.chaserhq.com/docs/static/index.html)

Version:0.0.1

Key:chaser-create-customer

View on GitHub

Chaser Overview#

The Chaser API enables users to automate their accounts receivable process efficiently, making it possible to manage and follow up on invoices programmatically. By integrating Chaser with Pipedream, users can automate invoice reminders, synchronize financial data with other business applications, and generate detailed accounts receivable reports. These capabilities help businesses improve their cash flow and minimize the time spent on manual follow-ups.

Action Code#

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

export default {
  key: "chaser-create-customer",
  name: "Create Customer",
  description: "Creates a new customer in Chaser. [See the documentation](https://openapi.chaserhq.com/docs/static/index.html)",
  version: "0.0.1",
  type: "action",
  props: {
    chaser,
    externalId: {
      type: "string",
      label: "External ID",
      description: "External ID of the customer",
    },
    companyName: {
      type: "string",
      label: "Company Name",
      description: "Company name of the customer",
    },
    firstName: {
      type: "string",
      label: "First Name",
      description: "First name of the customer",
      optional: true,
    },
    lastName: {
      type: "string",
      label: "Last Name",
      description: "Last name of the customer",
      optional: true,
    },
    emailAddress: {
      type: "string",
      label: "Email Address",
      description: "Email address of the customer",
      optional: true,
    },
    phoneNumber: {
      type: "string",
      label: "Phone Number",
      description: "Phone number of the customer",
      optional: true,
    },
    additionalOptions: {
      type: "object",
      label: "Additional Options",
      description:
        "Additional parameters to send in the request. [See the documentation](https://openapi.chaserhq.com/docs/static/index.html) for available parameters. Values will be parsed as JSON where applicable.",
      optional: true,
    },
  },
  async run({ $ }) {
    let additionalOptions = Object.fromEntries(
      Object.entries(this.additionalOptions ?? {}).map(([
        key,
        value,
      ]) => {
        // optional JSON parsing
        try {
          return [
            key,
            JSON.parse(value),
          ];
        } catch (e) {
          return [
            key,
            value,
          ];
        }
      }),
    );

    const response = await this.chaser.createCustomer({
      $,
      data: {
        external_id: this.externalId,
        company_name: this.companyName,
        contact_first_name: this.firstName,
        contact_last_name: this.lastName,
        contact_email_address: this.emailAddress,
        phone_number: this.phoneNumber,
        ...additionalOptions,
      },
    });
    $.export("$summary", `Successfully created customer (ID: ${response.data.id})`);
    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
Chaser	`chaser`	`app`	This component uses the Chaser app.
External ID	`externalId`	`string`	External ID of the customer
Company Name	`companyName`	`string`	Company name of the customer
First Name	`firstName`	`string`	First name of the customer
Last Name	`lastName`	`string`	Last name of the customer
Email Address	`emailAddress`	`string`	Email address of the customer
Phone Number	`phoneNumber`	`string`	Phone number of the customer
Additional Options	`additionalOptions`	`object`	Additional parameters to send in the request. See the documentation for available parameters. Values will be parsed as JSON where applicable.

Action Authentication#

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

To retrieve your API Keys (Host, Key and Secret)

Navigate to your Chaseraccount and sign in
Click the drop down on the top right
Go to “Organization settings” > “Integrations” > “Get API Keys”

About Chaser#

Credit check, monitor debtors, chase invoices via email and text, collect payments and recover debt - all in one place.

More Ways to Connect Chaser + HTTP / Webhook#

Other Popular Integrations#

Create Customer with Chaser API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Chaser

Try it

Create Customer with Chaser API on New Requests from HTTP / Webhook API

HTTP / Webhook + Chaser

Try it

Create Invoice with Chaser API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Chaser

Try it

Create Invoice with Chaser API on New Requests from HTTP / Webhook API

HTTP / Webhook + Chaser

Try it

Create Invoice with Chaser API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Chaser

Try it

Popular Triggers#

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