← HTTP / Webhook + Eventbrite integrations

Get Event Attendees with Eventbrite API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Eventbrite, HTTP / Webhook and 1000+ other apps remarkably fast.

Trigger workflow on
New Requests (Payload Only) from the HTTP / Webhook API
Next, do this
Get Event Attendees with the Eventbrite API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜

Trusted by 500,000+ developers from startups to Fortune 500 companies

Adyen logo
Brex logo
Carta logo
Checkr logo
Chameleon logo
DevRev logo
LinkedIn logo
Netflix logo
New Relic logo
OnDeck logo
Replicated logo
Scale AI logo
Teamwork logo
Warner Bros. logo
Xendit logo

Developers Pipedream

Getting Started

This integration creates a workflow with a HTTP / Webhook trigger and Eventbrite action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the New Requests (Payload Only) trigger
    1. Connect your HTTP / Webhook account
  3. Configure the Get Event Attendees action
    1. Connect your Eventbrite account
    2. Configure Event ID
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. 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

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

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.
LabelPropTypeDescription
N/AhttpInterface$.interface.httpThis 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 / WebhookhttpappThis 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

Description:Get event attendees for a specified event. [see docs here](https://www.eventbrite.com/platform/api#/reference/attendee/list/list-attendees-by-event)
Version:0.0.2
Key:eventbrite-get-event-attendees

Eventbrite Overview

With the Eventbrite API, you can build applications that:

  • Help event organizers sell tickets and promote their events
  • Allow eventgoers to find and buy tickets to events
  • Provide tools for event organizers to manage their events

Here are some examples of things you can build using the Eventbrite API:

  • A ticket sales and event promotion website or app
  • An event ticketing website or app
  • A event management tool for event organizers
  • A event search engine

Action Code

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

export default {
  key: "eventbrite-get-event-attendees",
  name: "Get Event Attendees",
  description: "Get event attendees for a specified event. [see docs here](https://www.eventbrite.com/platform/api#/reference/attendee/list/list-attendees-by-event)",
  version: "0.0.2",
  type: "action",
  props: {
    eventbrite,
    eventId: {
      propDefinition: [
        eventbrite,
        "eventId",
      ],
    },
  },
  methods: {
    async *attendeeStream($, params = {}) {
      let hasMoreItems;
      do {
        const {
          attendees,
          pagination = {},
        } = await this.eventbrite.getEventAttendees($, this.eventId, params);
        for (const attendee of attendees) {
          yield attendee;
        }

        hasMoreItems = !!pagination.has_more_items;
        params.continuation = pagination.continuation;
      } while (hasMoreItems);
    },
  },
  async run({ $ }) {
    const attendeeStream = await this.attendeeStream($);
    const attendees = [];
    for await (const attendee of attendeeStream) {
      attendees.push(attendee);
    }
    $.export("$summary", `Successfully fetched ${attendees.length} attendees`);
    return attendees;
  },
};

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.

LabelPropTypeDescription
EventbriteeventbriteappThis component uses the Eventbrite app.
Event IDeventIdinteger

Enter the ID of an event

Action Authentication

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

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

About Eventbrite

Eventbrite brings people together through live experiences. Discover events that match your passions, or create your own with online ticketing tools.

More Ways to Connect Eventbrite + HTTP / Webhook

Create Event with Eventbrite API on New Requests from HTTP / Webhook API
HTTP / Webhook + Eventbrite
 
Try it
Get Event Attendees with Eventbrite API on New Requests from HTTP / Webhook API
HTTP / Webhook + Eventbrite
 
Try it
Get Event Summary with Eventbrite API on New Requests from HTTP / Webhook API
HTTP / Webhook + Eventbrite
 
Try it
Create Event with Eventbrite API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + Eventbrite
 
Try it
Get Event Summary with Eventbrite API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + Eventbrite
 
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
New Attendee Check-In (Instant) from the Eventbrite API

Emit new event when an attendee checks in to an event

 
Try it
New Attendee Registered (Instant) from the Eventbrite API

Emit new event when an attendee registers for an event

 
Try it
Send any HTTP Request with the HTTP / Webhook API

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

 
Try it
Send GET Request with the HTTP / Webhook API

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send POST Request with the HTTP / Webhook API

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send PUT Request with the HTTP / Webhook API

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Return HTTP Response with the HTTP / Webhook API

Use with an HTTP Source that uses Return a custom response from your workflow as its HTTP Response

 
Try it