@pipedream/twitter 0.3.11 → 1.1.0

package/actions/list-retweets/list-retweets.mjs

@@ -1,54 +0,0 @@
-import common from "../common.mjs";
-
-export default {
-  ...common,
-  key: "twitter-list-retweets",
-  name: "List Retweets",
-  description: "Return a collection of recent retweets of a tweet by ID parameter. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/get-statuses-retweets-id)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    ...common.props,
-    id: {
-      propDefinition: [
-        common.props.twitter,
-        "tweetID",
-      ],
-    },
-    count: {
-      propDefinition: [
-        common.props.twitter,
-        "count",
-      ],
-      optional: true,
-      default: 20,
-    },
-    maxRequests: {
-      propDefinition: [
-        common.props.twitter,
-        "maxRequests",
-      ],
-    },
-  },
-  async run({ $ }) {
-    const {
-      id,
-      count,
-      maxRequests,
-    } = this;
-
-    const params = {
-      $,
-      id,
-      count,
-      maxRequests,
-    };
-    const tweets = await this.paginate(this.twitter.getRetweets.bind(this), params);
-    const results = [];
-    for await (const tweet of tweets) {
-      results.push(tweet);
-    }
-    $.export("$summary", "Successfully retrieved retweets");
-    return results;
-  },
-};

package/actions/list-user-tweets/list-user-tweets.mjs

@@ -1,80 +0,0 @@
-import common from "../common.mjs";
-
-export default {
-  ...common,
-  key: "twitter-list-user-tweets",
-  name: "List User Tweets",
-  description: "Return a collection of the most recent tweets posted by a user. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/timelines/api-reference/get-statuses-user_timeline)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    ...common.props,
-    screenName: {
-      propDefinition: [
-        common.props.twitter,
-        "screenName",
-      ],
-      optional: true,
-    },
-    count: {
-      propDefinition: [
-        common.props.twitter,
-        "count",
-      ],
-      optional: true,
-      default: 20,
-    },
-    maxRequests: {
-      propDefinition: [
-        common.props.twitter,
-        "maxRequests",
-      ],
-    },
-    includeRetweets: {
-      propDefinition: [
-        common.props.twitter,
-        "includeRetweets",
-      ],
-    },
-    includeReplies: {
-      propDefinition: [
-        common.props.twitter,
-        "includeReplies",
-      ],
-    },
-  },
-  methods: {
-    ...common.methods,
-    shouldExcludeReplies(includeReplies) {
-      return includeReplies === "exclude";
-    },
-    shouldIncludeRetweets(includeRetweets) {
-      return includeRetweets !== "exclude";
-    },
-  },
-  async run({ $ }) {
-    const {
-      screenName,
-      count,
-      maxRequests,
-      includeRetweets,
-      includeReplies,
-    } = this;
-
-    const params = {
-      $,
-      screenName,
-      count,
-      maxRequests,
-      exclude_replies: this.shouldExcludeReplies(includeReplies),
-      include_rts: this.shouldIncludeRetweets(includeRetweets),
-    };
-    const tweets = await this.paginate(this.twitter.getUserTimeline.bind(this), params);
-    const results = [];
-    for await (const tweet of tweets) {
-      results.push(tweet);
-    }
-    $.export("$summary", "Successfully retrieved user tweets");
-    return results;
-  },
-};

package/actions/retweet/retweet.mjs

@@ -1,27 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-
-export default {
-  key: "twitter-retweet",
-  name: "Retweet a tweet",
-  description: "Retweets a specific tweet by ID. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/post-statuses-retweet-id)",
-  version: "0.0.3",
-  type: "action",
-  props: {
-    twitter,
-    tweetID: {
-      propDefinition: [
-        twitter,
-        "tweetID",
-      ],
-      description: "The numerical ID of the tweet you'd like to retweet",
-    },
-  },
-  async run({ $ }) {
-    const res = await this.twitter.retweet({
-      $,
-      tweetID: this.tweetID,
-    });
-    $.export("$summary", "Tweet successfully retweeted");
-    return res;
-  },
-};

package/actions/simple-search/simple-search.mjs

@@ -1,62 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-
-export default {
-  key: "twitter-simple-search",
-  name: "Simple Search",
-  description: "Return Tweets that matches your search criteria. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/search/api-reference/get-search-tweets)",
-  version: "0.0.8",
-  type: "action",
-  props: {
-    twitter,
-    q: {
-      propDefinition: [
-        twitter,
-        "q",
-      ],
-    },
-    resultType: {
-      propDefinition: [
-        twitter,
-        "resultType",
-      ],
-    },
-    includeRetweets: {
-      propDefinition: [
-        twitter,
-        "includeRetweets",
-      ],
-    },
-    includeReplies: {
-      propDefinition: [
-        twitter,
-        "includeReplies",
-      ],
-    },
-  },
-  async run({ $ }) {
-    const {
-      resultType,
-      enrichTweets,
-      includeReplies,
-      includeRetweets,
-      maxRequests,
-      count,
-    } = this;
-    let q = this.q;
-
-    // run paginated search
-    const res = await this.twitter.paginatedSearch({
-      $,
-      q,
-      resultType,
-      enrichTweets,
-      includeReplies,
-      includeRetweets,
-      maxRequests,
-      count,
-      limitFirstPage: false,
-    });
-    $.export("$summary", "Search completed successfully");
-    return res;
-  },
-};

package/actions/simple-search-in-list/simple-search-in-list.mjs

@@ -1,48 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-
-export default {
-  key: "twitter-simple-search-in-list",
-  name: "Simple Search in List",
-  description: "Return Tweets that match your search criteria in a specific list. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/accounts-and-users/create-manage-lists/api-reference/get-lists-statuses)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    twitter,
-    listId: {
-      propDefinition: [
-        twitter,
-        "list",
-      ],
-    },
-    query: {
-      propDefinition: [
-        twitter,
-        "q",
-      ],
-    },
-    includeRetweets: {
-      propDefinition: [
-        twitter,
-        "includeRetweets",
-      ],
-    },
-    includeEntities: {
-      type: "boolean",
-      label: "Entities",
-      description: "Include the 'entities' node, which offers a variety of metadata about the tweet in a discreet structure, including: user_mentions, urls, and hashtags",
-      default: false,
-    },
-  },
-  async run({ $ }) {
-    let tweets = await this.twitter.getPaginateListTweets({
-      listId: this.listId,
-      includeEntities: this.includeEntities,
-      includeRetweets: this.includeRetweets !== "exclude",
-    });
-    tweets = tweets.filter((tweet) => tweet?.full_text?.includes(this.query));
-    $.export("$summary", `${tweets.length} search ${tweets.length === 1
-      ? "result has"
-      : "results have"} been found.`);
-    return tweets;
-  },
-};

package/actions/unfollow-user/unfollow-user.mjs

@@ -1,48 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-import { ConfigurationError } from "@pipedream/platform";
-
-export default {
-  key: "twitter-unfollow-user",
-  name: "Unfollow User",
-  description: "Unfollow the user specified by ID or screen name parameter. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/accounts-and-users/follow-search-get-users/api-reference/post-friendships-destroy)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    twitter,
-    userId: {
-      propDefinition: [
-        twitter,
-        "userId",
-      ],
-      optional: true,
-    },
-    screenName: {
-      propDefinition: [
-        twitter,
-        "screenName",
-      ],
-      optional: true,
-    },
-  },
-  async run({ $ }) {
-    const {
-      userId,
-      screenName,
-    } = this;
-
-    if (!userId && !screenName) {
-      throw new ConfigurationError("This action requires either User ID or Screen Name. Please enter one or the other above.");
-    }
-
-    const params = {
-      user_id: userId,
-      screen_name: screenName,
-    };
-    const response = await this.twitter.unfollowUser({
-      params,
-      $,
-    });
-    $.export("$summary", "Successfully unfollowed user");
-    return response;
-  },
-};

package/actions/unlike-tweet/unlike-tweet.mjs

@@ -1,40 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-
-export default {
-  key: "twitter-unlike-tweet",
-  name: "Unike Tweet",
-  description: "Unike the tweet specified specified in the ID parameter. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/post-favorites-destroy)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    twitter,
-    id: {
-      propDefinition: [
-        twitter,
-        "tweetID",
-      ],
-    },
-    includeEntities: {
-      propDefinition: [
-        twitter,
-        "includeEntities",
-      ],
-    },
-  },
-  async run({ $ }) {
-    const {
-      id,
-      includeEntities,
-    } = this;
-
-    const params = {
-      $,
-      id,
-      includeEntities,
-    };
-
-    const res = this.twitter.unlikeTweet(params);
-    $.export("$summary", "Successfully unliked tweet");
-    return res;
-  },
-};

package/actions/upload-media/upload-media.mjs

@@ -1,122 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-import fs from "fs";
-import mime from "mime";
-import FormData from "form-data";
-
-export default {
-  key: "twitter-upload-media",
-  name: "Upload Media",
-  description: "Upload images or other media types to Twitter. Returns a `media_id_string` to be used with the Create Tweet action. [See the docs here](https://developer.twitter.com/en/docs/tutorials/uploading-media)",
-  version: "0.0.3",
-  type: "action",
-  props: {
-    twitter,
-    file: {
-      type: "string",
-      label: "File",
-      description: "The file to upload to Twitter, please provide a file from `/tmp`. To upload a file to `/tmp` folder, please follow the doc [here](https://pipedream.com/docs/code/nodejs/working-with-files/#writing-a-file-to-tmp)",
-    },
-    mediaType: {
-      type: "string",
-      label: "Media Type",
-      description: "The MIME type of the media being uploaded",
-      options() {
-        return Object.values(mime._types);
-      },
-    },
-    mediaCategory: {
-      type: "string",
-      label: "Media Category",
-      description: "The category that represents how the media will be used",
-      options: [
-        "amplify_video",
-        "tweet_gif",
-        "tweet_image",
-        "tweet_video",
-      ],
-    },
-  },
-  methods: {
-    async append($, fileSize, mediaId) {
-      const bufferLength = 1000000;
-      const theBuffer = new Buffer(bufferLength);
-      let offset = 0;
-      let segment = 0;
-      const fd = fs.openSync(this.file, "r");
-      while (offset < fileSize) {
-        const bytesRead = fs.readSync(fd, theBuffer, 0, bufferLength, null);
-        const mediaData = bytesRead < bufferLength
-          ? theBuffer.slice(0, bytesRead)
-          : theBuffer;
-        const data = new FormData();
-        data.append("command", "APPEND");
-        data.append("media_id", mediaId);
-        data.append("media_data", mediaData.toString("base64"));
-        data.append("segment_index", segment);
-        await this.twitter.uploadMedia({
-          data,
-          headers: {
-            "Content-Type": `multipart/form-data; boundary=${data._boundary}`,
-          },
-          $,
-        });
-        segment++;
-        offset += bufferLength;
-      }
-      fs.close(fd);
-    },
-  },
-  async run({ $ }) {
-    // INIT
-    const fileSize = (fs.statSync(this.file)).size;
-    const params = {
-      command: "INIT",
-      total_bytes: fileSize,
-      media_type: this.mediaType,
-      additional_owners: this.twitter.$auth.oauth_uid,
-    };
-    if (this.mediaCategory) {
-      params.media_category = this.mediaCategory;
-    }
-    const { media_id_string: mediaId } = await this.twitter.uploadMedia({
-      params,
-      $,
-    });
-
-    // APPEND
-    await this.append($, fileSize, mediaId);
-
-    // FINALIZE
-    let response;
-    response = await this.twitter.uploadMedia({
-      params: {
-        command: "FINALIZE",
-        media_id: mediaId,
-      },
-      $,
-    });
-
-    // STATUS
-    while (this.mediaCategory?.includes("video")) {
-      response = await this.twitter.uploadMedia({
-        params: {
-          command: "STATUS",
-          media_id: mediaId,
-        },
-        method: "GET",
-        $,
-      });
-      const { processing_info: info } = response;
-      if (info?.error) {
-        throw new Error(JSON.stringify(info.error));
-      }
-      if (info?.state === "succeeded") {
-        break;
-      }
-      setTimeout(() => {}, info.check_after_secs * 1000);
-    }
-
-    response && $.export("$summary", `Successfully uploaded media with Media ID ${mediaId}`);
-    return response;
-  },
-};

package/old.md

@@ -1,169 +0,0 @@
-<p align="center">
-
-<img width="124" height="100" src="/images/twitter/TwitterLogo.png">    
-</p>
-<h1 align="center"><strong>Twitter Workflow Automation</strong></h1>
-
-
-<p align="center">Patterns for processing streams of tweets and interacting with the Twitter API</p>
-
-<p align="center">
-    <a href="#example-workflows"><img width="30%" src="/images/twitter/ExampleWorkflow.png" alt="Getting Started"></a>
-    <a href="#twitter-event-sources"><img width="30%" src="/images/twitter/TwitterEventSources.png" alt="Example Worksflows"></a>
-    <a href="#sse-and-rest-apis"><img width="30%" src="/images/twitter/SSE_RESTAPI.png" alt="SSE + REST API"></a>
-</p>
-
-&nbsp;&nbsp;
-
-## Example Workflows
-Workflows are linear sequences of steps — just Node.js code —hosted and run by Pipedream.
-
-**You can copy the workflows below and run them in your Pipedream account** [**for free**](https://docs.pipedream.com/pricing/ ). They run code on new tweets and interact with the Twitter API in creative ways. You can modify or extend them in any way you'd like, [**running your own Node code**](https://docs.pipedream.com/workflows/steps/code/) or using [**pre-built functions**](https://docs.pipedream.com/workflows/steps/actions/) to connect to [**200+ integrated apps**](https://docs.pipedream.com/apps/all-apps/).
-
-On copy, you'll be asked to create a [**Twitter event source**](#twitter-event-sources) that triggers your workflow on new tweets matching your target search.
-
-A single Twitter source can trigger multiple workflows. If you already created a source you want to use as a trigger, click **Select Another Trigger** near the bottom-left of the source selector.
-
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-email-p_zACral/readme"><img alt="Twitter to Email" src="/images/twitter/T2Em.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/send-an-http-post-request-on-new-tweets-p_6lCRoN/readme"><img alt="Twitter to Webhook" src="/images/twitter/T2We.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-aws-sqs-p_vQCraZ/readme"><img alt="Twitter to AWS SQS" src="/images/twitter/T2AS.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-aws-eventbridge-event-bus-p_ZJCWpg/readme"><img alt="Twitter to AWS EventBridge" src="/images/twitter/T2AE.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-aws-lambda-p_wOCAdP/readme"><img alt="Twitter to AWS Lambda" src="/images/twitter/T2AL.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-telegram-p_QPC8JP/readme"><img alt="Twitter to Telegram" src="/images/twitter/T2Te.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@pravin/twitter-mentions-slack-p_dDCA5e/edit"><img alt="Twitter to Slack" src="/images/twitter/T2Sl.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-discord-p_MOCQ9Y/readme"><img alt="Twitter to Discord" src="/images/twitter/T2Ti.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-s3-p_KwCZGA/readme"><img alt="Twitter to S3" src="/images/twitter/T2S3.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-pipedream-sql-service-p_brCMA9/readme"><img alt="Twitter to SQ:" src="/images/twitter/T2Sq.png" width="45%"></a>
-</p>
-
-&nbsp;&nbsp;
-
-## Twitter Event Sources
-
-Pipedream [**event sources**](https://docs.pipedream.com/event-sources/) emit Twitter events in real time: tweets, follows, likes, and more. Sources can trigger [**Pipedream workflows**](#example-workflows), and can be accessed via [**SSE or REST APIs**](#apis).
-
-Click on a source below to get started.
-
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fsearch-twitter.js&amp;app=twitter"><img alt="Search Mention" src="/images/twitter/SM.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fmy-tweets.js&amp;app=twitter"><img alt="My Tweets" src="/images/twitter/MT.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fnew-follower-of-user.js&amp;app=twitter"><img alt="New Follower for User" src="/images/twitter/NFfU.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fnew-follower-of-me.js&amp;app=twitter"><img alt="My New Followers" src="/images/twitter/MNF.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fmy-liked-tweets.js&amp;app=twitter"><img alt="My Liked Tweets" src="/images/twitter/MLT.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Ftweets-liked-by-user.js&amp;app=twitter"><img alt="Tweets Liked by User" src="/images/twitter/TLbU.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fuser-tweets.js&amp;app=twitter"><img alt="New Tweets from User" src="/images/twitter/NTfU.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fnew-trends-by-geo.js&amp;app=twitter"><img alt="New Trends by Geo" src="/images/twitter/NTbG.png" width="45%"></a>
-</p>
-
-Let's see how sources work with an end-to-end example:**running code on new mentions**.
-
-Most Twitter bots react to other tweets. For example, you might want to reply to a user with a specific message every time they mention you. Or you may want to store every tweet with a specific hashtag in an Amazon S3 bucket.
-
-When you create a Twitter bot, you typically have to sign up for a Twitter developer account, create your own app, host it somewhere, and run code to poll for new tweets. This is a means to an end:**all you really want to do is run code on new tweets**.
-
-```js
-// Don't care how I get tweets
-for (const tweet of tweets) {
-    // Just want to run code
-}
-```
-
-Pipedream lets you create a stream of tweets you can process programmatically in seconds, avoiding the app setup entirely. These are called [**event sources**](https://docs.pipedream.com/event-sources/).
-
-Pipedream runs the code to poll for new tweets matching your search terms, emitting them as events you can run code on.
-
-<p align="center">
-    <img alt="pipeDream" src="/images/twitter/TwitterPipeDream.png">
-</p>
-
-Then, you can immediately process those tweets in a few different ways:
-
-+ Trigger a Pipedream workflow for each tweet, running hosted Node.js code in real time
-+ Subscribe to a private SSE stream, which also publishes tweets in real time
-+ Access tweets in batch using Pipedream's REST API
-
-To get started, [**create a new Twitter search source in the Pipedream UI**](https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fsearch-twitter.js&amp;app=twitter&amp;src=twitter.pipedream.com). Name the source, connect your Twitter account, and add your search term:
-
-<p align="center">
-    <kbd><img alt="Twitter Source in Pipedream UI" width="700" src="/images/twitter/twitter-source-in-ui.png"></kbd>
-</p>
-
-You can also visit [**https://pipedream.com/sources**](https://pipedream.com/sources) and click the **Create Source** button, then choose the **twitter/twitter-search.js** source from the modal that appears.
-
-Then, you can trigger a [**Pipedream workflow**](https://pipedream.com/new) — a serverless Node.js script — on every tweet:
-
-<p align="center">
-    <kbd><img alt="New workflow source" width="550" src="/images/twitter/new-workflow-source.png"></kbd>
-</p>
-
-
-They should work as is, but you can modify them in any way. For example, you can add a step to [**run any Node.js code**](https://docs.pipedream.com/workflows/steps/code/) or use [**pre-built functions**](https://docs.pipedream.com/workflows/steps/actions/) to send data to other destinations.
-
-
-&nbsp;&nbsp;
-
-## SSE and REST APIs
-
-Pipedream provides two other interfaces for accessing events produced by sources:
-
-+ A private SSE stream specific to your source
-+ A REST API
-
-This way, you can run an event source in Pipedream but access its events in your own application.
-
-### SSE
-
-SSE —[**Server-sent events**](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events)—defines a spec for how servers can send events directly to clients that subscribe to those events, similar to [**WebSockets**](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) and related server-to-client push technologies. If you listen for new items using SSE, **you can run any code in your own application, in real time, as soon as those items are added to the feed.**
-
-Streams are private by default. You authenticate by passing your Pipedream API key in the Authorization header:
-
-```js
-$ curl -H "Authorization: Bearer API_KEY" \
-
-    https://api.pipedream.com/sources/SOURCE_ID/sse
-```
-
-[**See the Pipedream SSE docs**](https://docs.pipedream.com/api/sse) for more information on authentication, example Node code, and other details on the interface.
-
-### REST API
-
-If you prefer to process tweets in batch, you can fetch them using [**Pipedream's REST API**](https://docs.pipedream.com/api/rest/):
-
-```js
-$ curl -H "Authorization: Bearer API_KEY" \
-
-    https://api.pipedream.com/v1/sources/SOURCE_ID/event_summaries?limit=1
-```
-
-Note the?limit=1query string. You can vary the number of events returned (most recent first) by setting this param.
-
-Please [**reach out**](https://docs.pipedream.com/support/) with any questions or feedback. We're happy to add other Twitter-specific developer resources to this list, and we'd love to hear what can be improved about event sources or the example workflows.
-    
-&nbsp;&nbsp;
-
-___
-
-<p align="center">
-Pipedream, Inc. — San Francisco, CA
-</p>
-<p align="center">
-<a href="https://twitter.com/PipedreamHQ">Twitter</a> | <a href="https://pipedream.com/community">Community</a> | <a href="https://docs.pipedream.com/">Docs</a> | <a href="https://pipedream.com/terms">Terms</a> |
-    <a href="https://pipedream.com/privacy">Privacy</a>
-</p>
-
-___