Create Tweet with Twitter API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Create Tweet with the Twitter API

No credit card required

▶

Watch us build a workflow

7 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook 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 Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Create Tweet action
1. Connect your Twitter account
2. Configure Status
3. Optional- Configure In Reply To Status ID
4. Optional- Configure Auto Populate Reply Metadata
5. Optional- Configure Exclude Reply User Ids
6. Optional- Configure Attachment URL
7. Optional- Configure Media IDs
8. Optional- Configure Possibly Sensitive
9. Optional- Configure Latitude
10. Optional- Configure Longitude
11. Optional- Configure Place ID
12. Optional- Configure Display Coordinates
13. Optional- Configure Trim User
14. Optional- Configure Enable DM Commands
15. Optional- Configure Fail DM Commands
16. Optional- Configure Card URI
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

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#

Create Tweet on Twitter

Description:Create a new tweet. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/post-statuses-update)

Version:0.0.4

Key:twitter-create-tweet

View on GitHub

Action Code#

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

export default {
  key: "twitter-create-tweet",
  name: "Create Tweet",
  description: "Create a new tweet. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/post-statuses-update)",
  version: "0.0.4",
  type: "action",
  props: {
    twitter,
    status: {
      propDefinition: [
        twitter,
        "status",
      ],
    },
    inReplyToStatusId: {
      propDefinition: [
        twitter,
        "inReplyToStatusId",
      ],
    },
    autoPopulateReplyMetadata: {
      propDefinition: [
        twitter,
        "autoPopulateReplyMetadata",
      ],
    },
    excludeReplyUserIds: {
      propDefinition: [
        twitter,
        "excludeReplyUserIds",
      ],
    },
    attachmentUrl: {
      propDefinition: [
        twitter,
        "attachmentUrl",
      ],
    },
    mediaIds: {
      propDefinition: [
        twitter,
        "mediaIds",
      ],
    },
    possiblySensitive: {
      propDefinition: [
        twitter,
        "possiblySensitive",
      ],
    },
    lat: {
      propDefinition: [
        twitter,
        "lat",
      ],
    },
    long: {
      propDefinition: [
        twitter,
        "long",
      ],
    },
    placeId: {
      propDefinition: [
        twitter,
        "placeId",
      ],
    },
    displayCoordinates: {
      propDefinition: [
        twitter,
        "displayCoordinates",
      ],
    },
    trimUser: {
      propDefinition: [
        twitter,
        "trimUser",
      ],
    },
    enableDmcommands: {
      propDefinition: [
        twitter,
        "enableDmcommands",
      ],
    },
    failDmcommands: {
      propDefinition: [
        twitter,
        "failDmcommands",
      ],
    },
    cardUri: {
      propDefinition: [
        twitter,
        "cardUri",
      ],
    },
  },
  async run({ $ }) {
    const {
      status,
      inReplyToStatusId,
      autoPopulateReplyMetadata,
      excludeReplyUserIds,
      attachmentUrl,
      mediaIds,
      possiblySensitive,
      lat,
      long,
      placeId,
      displayCoordinates,
      trimUser,
      enableDmcommands,
      failDmcommands,
      cardUri,
    } = this;

    const params = {
      status,
      inReplyToStatusId,
      autoPopulateReplyMetadata,
      excludeReplyUserIds,
      attachmentUrl,
      media_ids: mediaIds,
      possiblySensitive,
      lat,
      long,
      placeId,
      displayCoordinates,
      trimUser,
      enableDmcommands,
      failDmcommands,
      cardUri,
    };
    Object.keys(params).forEach((k) => params[k] == "" && delete params[k]);
    const res = await this.twitter.createTweet({
      $,
      params,
    });
    $.export("$summary", "Successfully posted tweet");
    return res;
  },
};

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
Twitter	`twitter`	`app`	This component uses the Twitter app.
Status	`status`	`string`	The text of the status update. Note: In order to comply with Twitter’s terms of service, this text will have all @mentions removed. Please refer to our docs for more details.
In Reply To Status ID	`inReplyToStatusId`	`string`	The ID of an existing status that the update is in reply to. Note: This parameter will be ignored unless the author of the Tweet this parameter references is mentioned within the status text. Therefore, you must include `@username` , where `username` is the author of the referenced Tweet, within the update.
Auto Populate Reply Metadata	`autoPopulateReplyMetadata`	`boolean`	If set to true and used with `in_reply_to_status_id`, leading `@mentions` will be looked up from the original Tweet, and added to the new Tweet from there. This will append `@mentions` into the metadata of an extended Tweet as a reply chain grows, until the limit on `@mentions` is reached. In cases where the original Tweet has been deleted, the reply will fail.
Exclude Reply User Ids	`excludeReplyUserIds`	`string`	When used with `auto_populate_reply_metadata`, a comma-separated list of user ids which will be removed from the server-generated `@mentions` prefix on an extended Tweet. Note that the leading `@mention` cannot be removed as it would break the `in-reply-to-status-id` semantics. Attempting to remove it will be silently ignored.
Attachment URL	`attachmentUrl`	`string`	In order for a URL to not be counted in the status body of an extended Tweet, provide a URL as a Tweet attachment. This URL must be a Tweet permalink or Direct Message deep link. Arbitrary, non-Twitter URLs must remain in the status text. URLs passed to the `attachment_url` parameter not matching either a Tweet permalink or Direct Message deep link will fail at Tweet creation and cause an exception.
Media IDs	`mediaIds`	`string`	A comma-delimited list of `media_ids` to associate with the Tweet. You may include up to 4 photos or 1 animated GIF or 1 video in a Tweet.
Possibly Sensitive	`possiblySensitive`	`boolean`	If you upload Tweet media that might be considered sensitive content such as nudity or medical procedures, you must set this value to true. If this parameter is included in your request, it will override the user’s preferences.
Latitude	`lat`	`string`	The latitude of the location this Tweet refers to.
Longitude	`long`	`string`	The longitude of the location this Tweet refers to.
Place ID	`placeId`	`string`	A place in the world. These IDs can be retrieved from geo/reverse_geocode
Display Coordinates	`displayCoordinates`	`boolean`	Whether or not to put a pin on the exact coordinates a Tweet has been sent from.
Trim User	`trimUser`	`boolean`	When set to true, the response will include a user object including only the author's ID.
Enable DM Commands	`enableDmcommands`	`boolean`	When set to true, enables shortcode commands for sending Direct Messages as part of the status text to send a Direct Message to a user. When set to false, it turns off this behavior and includes any leading characters in the status text that is posted.
Fail DM Commands	`failDmcommands`	`boolean`	When set to true, causes any status text that starts with shortcode commands to return an API error. When set to false, allows shortcode commands to be sent in the status text and acted on by the API.
Card URI	`cardUri`	`string`	Associate an ads card with the Tweet using the card_uri value from any ads card response.

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 + HTTP / Webhook#

Other Popular Integrations#

Advanced Search with Twitter API on New Requests from HTTP / Webhook API

HTTP / Webhook + Twitter

Create Tweet with Twitter API on New Requests (Payload Only) from HTTP / Webhook API

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

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

Developers ♥ Pipedream

1-12of1000+apps by most popular

1
-
12
of
1000+
apps by most popular