Send GET Request with HTTP / Webhook API on New Call Event from CallPage API

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

Trigger workflow on

New Call Event from the CallPage 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 CallPage 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 Call Event trigger
1. Connect your CallPage account
2. Configure timer
3. Select one or more Call Statuses
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 Call Event on CallPage

Description:Emit new event when there is a new call event.

Version:0.0.1

Key:callpage-new-call-event

View on GitHub

CallPage Overview#

The CallPage API enables automations centered around phone calls and lead management. Integrating this API with Pipedream allows you to create, update, and track calls, as well as manage users and leads. With Pipedream's serverless architecture, you can easily connect CallPage to other apps, triggering complex workflows from CallPage events or performing actions in CallPage in response to external triggers.

Trigger Code#

import callpage from "../../callpage.app.mjs";
import { CALL_STATUSES } from "../../common/constants.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  key: "callpage-new-call-event",
  name: "New Call Event",
  description: "Emit new event when there is a new call event.",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    callpage,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: 60,
      },
    },
    callStatuses: {
      type: "string[]",
      label: "Call Statuses",
      description: "Select the call statuses to trigger events for",
      options: CALL_STATUSES,
    },
  },
  methods: {
    _getLastDate() {
      return this.db.get("lastDate") || [];
    },
    _setLastDate(lastDate) {
      return this.db.set("lastDate", lastDate);
    },
    async startEvent(maxResults = false) {
      const lastDate = this._getLastDate();
      const response = this.callpage.paginate({
        fn: this.callpage.listEvents,
        maxResults,
        params: {
          date_from: lastDate,
          statuses: this.callStatuses,
        },
      });

      const responseArray = [];

      for await (const item of response) {
        responseArray.push(item);
      }

      if (responseArray.length) {
        this._setLastDate(Date.parse(responseArray[responseArray.length - 1].created_at));
      }

      for (const event of responseArray) {
        this.$emit(event, {
          id: event.id,
          summary: `New call event with ID: ${event.human_status}`,
          ts: Date.parse(event.created_at),
        });
      }
    },
  },
  hooks: {
    async deploy() {
      await this.startEvent(25);
    },
  },
  async run() {
    await this.startEvent();
  },
  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
CallPage	`callpage`	`app`	This component uses the CallPage app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Call Statuses	`callStatuses`	`string[]`	Select a value from the drop down menu:`{ "label": "New", "value": "new" }{ "label": "Scheduled", "value": "scheduled" }{ "label": "In Progress", "value": "in-progress" }{ "label": "Ringing", "value": "ringing" }{ "label": "Completed", "value": "completed" }{ "label": "Manager Failed", "value": "manager-failed" }{ "label": "User Failed", "value": "user-failed" }{ "label": "Failed", "value": "failed" }{ "label": "Cancelled", "value": "cancelled" }`

Trigger Authentication#

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

To retrieve your API key,

Navigate to your CallPage account and sign in
Go to “Settings” > “API settings”

About CallPage#

We are the #1 tool to generate more sales calls & leads from your website.

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 + CallPage#

Other Popular Integrations#

Create SMS with CallPage API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + CallPage

Try it

Create SMS with CallPage API on New Requests from HTTP / Webhook API

HTTP / Webhook + CallPage

Try it

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

HTTP / Webhook + CallPage

Try it

Send any HTTP Request with HTTP / Webhook API on New Call Event from CallPage API

CallPage + HTTP / Webhook

Try it

Send POST Request with HTTP / Webhook API on New Call Event from CallPage API

CallPage + HTTP / Webhook

Try it

Popular Triggers#

New Call Event from the CallPage API

Emit new event when there is a new call event.

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