List Events with Team Up API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

List Events with the Team Up 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 Team Up 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 trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the List Events action
1. Connect your Team Up account
2. Configure Calendar Key
3. Optional- Select one or more Sub-calendar IDs
4. Optional- Configure Query
5. Optional- Configure Start Date
6. Optional- Configure End Date
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 on HTTP / Webhook

Description: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.

Version:0.1.1

Key:http-new-requests

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
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "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.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
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 Events on Team Up

Description:Get a list of events based on search criteria [See docs here](https://apidocs.teamup.com/docs/api/0f9f896800ffe-get-events-collection-get-events-changed-search-events)

Version:0.0.1

Key:team_up-list-events

View on GitHub

Team Up Overview#

The Team Up API allows you to interact with your Team Up calendars programmatically, enabling the automation of event creation, updates, and deletion, as well as the retrieval of calendar data. By integrating the Team Up API with Pipedream, you can build workflows that trigger on specific events, automate tasks, and connect your calendar data with countless other services, bringing efficiency to team coordination and event management.

Action Code#

import app from "../../app/team_up.app.mjs";
import { defineAction } from "@pipedream/types";
import calendarKeyOptions from "../../common/calendarKeyOptions.mjs";
export const DOCS_LINK = "https://apidocs.teamup.com/docs/api/0f9f896800ffe-get-events-collection-get-events-changed-search-events";
export default defineAction({
    name: "List Events",
    description: `Get a list of events based on search criteria [See docs here](${DOCS_LINK})`,
    key: "team_up-list-events",
    version: "0.0.1",
    type: "action",
    props: {
        app,
        calendarKey: {
            propDefinition: [
                app,
                "calendarKey",
            ],
        },
        subcalendarId: {
            propDefinition: [
                app,
                "subCalendarIds",
                calendarKeyOptions,
            ],
            optional: true,
        },
        query: {
            type: "string",
            label: "Query",
            description: "Query string used to search for events. See the [Search Guide](https://calendar.teamup.com/kb/searching-teamup-calendar/) for supported query syntax and features.",
            optional: true,
        },
        startDate: {
            propDefinition: [
                app,
                "startDate",
            ],
            optional: true,
            description: "The start of the date range to list events from, in `YYYY-MM-DD` format. Default is `today`.",
        },
        endDate: {
            propDefinition: [
                app,
                "endDate",
            ],
            optional: true,
            description: "The end of the date range to list events from (inclusive), in `YYYY-MM-DD` format. Default is `today+1day`.",
        },
    },
    async run({ $ }) {
        const { calendarKey, subcalendarId, query, startDate, endDate, } = this;
        const params = {
            $,
            calendarKey,
            params: {
                subcalendarId,
                query,
                startDate,
                endDate,
            },
        };
        const data = await this.app.listEvents(params);
        $.export("$summary", `Successfully obtained ${data.events.length} events`);
        return data;
    },
});

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
Team Up	`app`	`app`	This component uses the Team Up app.
Calendar Key	`calendarKey`	`string`	The Calendar Key to use. See the TeamUp API Docs for more information.
Sub-calendar IDs	`subcalendarId`	`string[]`	Select a value from the drop down menu.
Query	`query`	`string`	Query string used to search for events. See the Search Guide for supported query syntax and features.
Start Date	`startDate`	`string`	The start of the date range to list events from, in `YYYY-MM-DD` format. Default is `today`.
End Date	`endDate`	`string`	The end of the date range to list events from (inclusive), in `YYYY-MM-DD` format. Default is `today+1day`.

Action Authentication#

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

Generate and copy your API Key from the Request Teamup API Key form.
Refer to Team Up's documentation to find your calendar key.

About Team Up#

It's more than a calendar. Organize things in colors, grids, lists, and custom fields. Connect dots easily among schedules, people and information.

More Ways to Connect Team Up + HTTP / Webhook#

Other Popular Integrations#

Create Event with Team Up API on New Requests from HTTP / Webhook API

HTTP / Webhook + Team Up