List Webhook Subscriptions with Calendly API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

List Webhook Subscriptions with the Calendly 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 Calendly action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the List Webhook Subscriptions action
1. Connect your Calendly account
2. Select a scope
3. Configure organization_uri
4. Optional- Configure user_uri
5. Optional- Configure count
6. Optional- Configure page_token
7. Optional- Select a sort
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 Requests (Payload Only) on HTTP / Webhook

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

Version:0.1.1

Key:http-new-requests-payload-only

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";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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
N/A	`httpInterface`	`$.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.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

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#

List Webhook Subscriptions on Calendly

Description:Get a list of Webhook Subscriptions for an Organization or User with a UUID.

Version:0.1.4

Key:calendly_v2-list-webhook-subscriptions

View on GitHub

Calendly Overview#

The Calendly API lets you craft bespoke scheduling experiences within your apps or automate repetitive tasks involving your calendar. With this API, you can read event types, set up webhooks for new events, list invitees, or create and cancel invitation links programmatically. Pipedream's serverless platform takes the heavy lifting out of integrating Calendly with hundreds of other apps, enabling you to focus on creating workflows that save time, enhance productivity, and eliminate scheduling errors.

Action Code#

// legacy_hash_id: a_k6ij8Q
import { axios } from "@pipedream/platform";

export default {
  key: "calendly_v2-list-webhook-subscriptions",
  name: "List Webhook Subscriptions",
  description: "Get a list of Webhook Subscriptions for an Organization or User with a UUID.",
  version: "0.1.4",
  type: "action",
  props: {
    calendly_v2: {
      type: "app",
      app: "calendly_v2",
    },
    scope: {
      type: "string",
      description: "Filter the list by organization or user.",
      options: [
        "organization",
        "user",
      ],
    },
    organization_uri: {
      type: "string",
      description: "Indicates if the results should be filtered by organization, by entering an organization 's URI, such as `https://api.calendly.com/organizations/012345678901234567890`.",
    },
    user_uri: {
      type: "string",
      description: "Indicates if the results should be filtered by user, by entering a user's URI, such as `https://api.calendly.com/users/CAFHCZWDQLKQ73HX`. You can use the [Get User](https://developer.calendly.com/docs/api-docs/reference/calendly-api/openapi.yaml/paths/~1users~1me/get) endpoint to find a user's URI.",
      optional: true,
    },
    count: {
      type: "string",
      description: "The number of rows to return.",
      optional: true,
    },
    page_token: {
      type: "string",
      description: "The token to pass to get the next portion of the collection.",
      optional: true,
    },
    sort: {
      type: "string",
      description: "Order results by the specified field and direction. Accepts comma-separated list of {field}:{direction} values. Supported fields are: created_at. Sort direction is specified as: asc, desc.",
      optional: true,
      options: [
        "created_at:asc",
        "created_at:desc",
      ],
    },
  },
  async run({ $ }) {
  //See the API docs: https://developer.calendly.com/docs/api-docs/reference/calendly-api/openapi.yaml/paths/~1webhook_subscriptions/get

    if (!this.scope || !this.organization_uri) {
      throw new Error("Must provide scope, and organization_uri parameters.");
    }

    return await axios($, {
      url: "https://api.calendly.com/webhook_subscriptions",
      headers: {
        Authorization: `Bearer ${this.calendly_v2.$auth.oauth_access_token}`,
      },
      params: {
        scope: this.scope,
        user: this.user_uri,
        count: this.count,
        organization: this.organization_uri,
        page_token: this.page_token,
        sort: this.sort,
      },
    });
  },
};

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
Calendly	`calendly_v2`	`app`	This component uses the Calendly app.
scope	`scope`	`string`	Select a value from the drop down menu:`organizationuser`
organization_uri	`organization_uri`	`string`	Indicates if the results should be filtered by organization, by entering an organization 's URI, such as `https://api.calendly.com/organizations/012345678901234567890`.
user_uri	`user_uri`	`string`	Indicates if the results should be filtered by user, by entering a user's URI, such as `https://api.calendly.com/users/CAFHCZWDQLKQ73HX`. You can use the Get User endpoint to find a user's URI.
count	`count`	`string`	The number of rows to return.
page_token	`page_token`	`string`	The token to pass to get the next portion of the collection.
sort	`sort`	`string`	Select a value from the drop down menu:`created_at:asccreated_at:desc`

Action Authentication#

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

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

About Calendly#

Schedule meetings without the hassle. Never get double booked. Calendly works with your calendar to automate appointment scheduling.

More Ways to Connect Calendly + HTTP / Webhook#

Other Popular Integrations#

Send any HTTP Request with HTTP / Webhook API on New Invitee Action from Calendly (OAuth) API

Calendly + HTTP / Webhook