Advanced Search with Twitter APIon New Attendee Check-In (Instant) from Eventbrite API

Pipedream makes it easy to connect APIs for Twitter, Eventbrite and + other apps remarkably fast.

Trigger workflow on

New Attendee Check-In (Instant) from the Eventbrite API

Next, do this

Advanced Search with the Twitter API

No credit card required

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New Attendee Check-In (Instant) trigger
1. Connect your Eventbrite account
2. Select a Organization
Configure the Advanced Search action
1. Connect your Twitter account
2. Configure Search Term
3. Optional- Select a Result Type
4. Optional- Select a Retweets
5. Optional- Select a Replies
6. Optional- Select a Language
7. Optional- Configure Locale
8. Optional- Configure Geocode
9. Optional- Configure Since ID
10. Optional- Configure Enrich Tweets
11. Optional- Configure Count (advanced)
12. Optional- Configure Max API Requests per Execution (advanced)
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, open source 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 Attendee Check-In (Instant) on Eventbrite

Description:Emits an event when an attendee checks in to an event

Version:0.0.1

Key:eventbrite-new-attendee-checkin

View on GitHub

Trigger Code#

const common = require("../common/webhook.js");

module.exports = {
  ...common,
  key: "eventbrite-new-attendee-checkin",
  name: "New Attendee Check-In (Instant)",
  description: "Emits an event when an attendee checks in to an event",
  version: "0.0.1",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getActions() {
      return "attendee.checked_in";
    },
    async getData(attendee) {
      const { event_id: eventId } = attendee;
      const event = await this.eventbrite.getEvent(eventId);
      return {
        attendee,
        event,
      };
    },
    generateMeta({ attendee }) {
      const { id, profile, created } = attendee;
      return {
        id,
        summary: profile.name,
        ts: Date.parse(created),
      };
    },
  },
};

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
Eventbrite	`eventbrite`	`app`	This component uses the Eventbrite app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between component invocations.
Organization	`organization`	`string`	Select a value from the drop down menu.
N/A	`http`	`$.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.

Trigger 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#

Action#

Advanced Search on Twitter

Description:Return Tweets that matches your search criteria.

Version:0.0.2

Key:twitter-advanced-search

View on GitHub

Action Code#

const twitter = require('../../twitter.app.js')
const moment = require('moment')
 
module.exports = {
  key: "twitter-advanced-search",
  name: "Advanced Search",
  description: "Return Tweets that matches your search criteria.", 
  version: "0.0.2",
  type: "action",
  props: {
    db: "$.service.db",
    twitter,
    q: { propDefinition: [twitter, "q"] },
    result_type: { propDefinition: [twitter, "result_type"] },
    includeRetweets: { propDefinition: [twitter, "includeRetweets"] },
    includeReplies: { propDefinition: [twitter, "includeReplies"] },
    lang: { propDefinition: [twitter, "lang"] },
    locale: { propDefinition: [twitter, "locale"] },
    geocode: { propDefinition: [twitter, "geocode"] },
    since_id: { propDefinition: [twitter, "since_id"] },
    enrichTweets: { propDefinition: [twitter, "enrichTweets"] },
    count: { propDefinition: [twitter, "count"] },
    maxRequests: { propDefinition: [twitter, "maxRequests"] },
  }, 
  async run(event) {
    const { lang, locale, geocode, result_type, enrichTweets, includeReplies, includeRetweets, since_id, maxRequests, count } = this
    let q = this.q, max_id, limitFirstPage

    if (!since_id) {
      limitFirstPage = true
    } else {
      limitFirstPage = false
    }
 
    // run paginated search
    return await this.twitter.paginatedSearch({ 
      q, 
      since_id, 
      lang, 
      locale, 
      geocode, 
      result_type, 
      enrichTweets, 
      includeReplies, 
      includeRetweets, 
      maxRequests,
      count,
      limitFirstPage,
    })
  },
}

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
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between component invocations.
Twitter	`twitter`	`app`	This component uses the Twitter app.
Search Term	`q`	`string`	Search for keywords `star wars`, screen names `@starwars`, or hashtags `#starwars`. You can also use Twitter's standard search operators.
Result Type	`result_type`	`string`	Select a value from the drop down menu:`{ "label": "Recent", "value": "recent" }{ "label": "Popular", "value": "popular" }{ "label": "Mixed", "value": "mixed" }`
Retweets	`includeRetweets`	`string`	Select a value from the drop down menu:`{ "label": "Include", "value": "include" }{ "label": "Exclude", "value": "exclude" }{ "label": "Only include retweets", "value": "only" }`
Replies	`includeReplies`	`string`	Select a value from the drop down menu:`{ "label": "Include", "value": "include" }{ "label": "Exclude", "value": "exclude" }{ "label": "Only include replies", "value": "only" }`
Language	`lang`	`string`	Select a value from the drop down menu.
Locale	`locale`	`string`	Specify the language of the query you are sending (only `ja` is currently effective). This is intended for language-specific consumers and the default should work in the majority of cases.
Geocode	`geocode`	`string`	Returns tweets by users located within a given radius of the given latitude/longitude. The location is preferentially taking from the Geotagging API, but will fall back to their Twitter profile. The parameter value is specified by `latitude,longitude,radius`, where radius units must be specified as either `mi` (miles) or `km` (kilometers). Note that you cannot use the near operator via the API to geocode arbitrary locations; however you can use this geocode parameter to search near geocodes directly.
Since ID	`since_id`	`string`	Returns results with an ID greater than (that is, more recent than) the specified ID. There are limits to the number of Tweets which can be accessed through the API. If the limit of Tweets has occured since the since_id, the since_id will be forced to the oldest ID available.
Enrich Tweets	`enrichTweets`	`boolean`	Enrich each tweet with epoch (milliseconds) and ISO8601 conversions of Twitter's `created_at` timestamp.
Count (advanced)	`count`	`integer`	The maximum number of tweets to return per API request (up to `100`)
Max API Requests per Execution (advanced)	`maxRequests`	`integer`	The maximum number of API requests to make per execution (e.g., multiple requests are required to retrieve paginated results). Note: Twitter rate limits API requests per 15 minute interval.

Action Authentication#

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

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

About Twitter#

From breaking news and entertainment to sports and politics, get the full story with all the live commentary.

More Ways to Connect Twitter + Eventbrite#

Other Popular Integrations#

Simple Search with Twitter API on New Attendee Check-In (Instant) from Eventbrite API

Advanced Search with Twitter APIon New Attendee Check-In (Instant) from Eventbrite API

Pipedream makes it easy to connect APIs for Twitter, Eventbrite and + other apps remarkably fast.

Developers ♥ Pipedream

1-12of500+apps by most popular

1
-
12
of
500+
apps by most popular