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

Pipedream makes it easy to connect APIs for X (Twitter), HTTP / Webhook and 2,500+ other apps remarkably fast.

Trigger workflow on

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

Next, do this

Create Tweet with the X (Twitter) 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 X (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 X (Twitter) account
2. Optional- Configure Text
3. Optional- Configure In Reply To Tweet (ID)
4. Optional- Configure Exclude Reply User IDs
5. Optional- Configure Media IDs
6. Optional- Configure Tagged User IDs
7. Optional- Configure Place ID
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

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
// 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 X (Twitter)

Description:Create a new tweet. [See the documentation](https://developer.twitter.com/en/docs/twitter-api/tweets/manage-tweets/api-reference/post-tweets)

Version:2.1.6

Key:twitter-create-tweet

View on GitHub

X (Twitter) Overview#

The Twitter API on Pipedream enables you to automate interactions with Twitter, from posting tweets to analyzing social media trends. Pipedream's serverless platform provides the tools to create workflows that trigger on specific Twitter activities, process data, and connect with countless other apps for extensive automation scenarios. With Pipedream's integration, you can listen for events such as new tweets, mentions, or followers, and execute actions like tweeting, retweeting, or even leveraging sentiment analysis to gauge public perception.

Action Code#

import app from "../../app/twitter.app.mjs";
import { ACTION_ERROR_MESSAGE } from "../../common/errorMessage.mjs";
import { defineAction } from "@pipedream/types";
const DOCS_LINK = "https://developer.twitter.com/en/docs/twitter-api/tweets/manage-tweets/api-reference/post-tweets";
export default defineAction({
    key: "twitter-create-tweet",
    name: "Create Tweet",
    description: `Create a new tweet. [See the documentation](${DOCS_LINK})`,
    version: "2.1.6",
    type: "action",
    props: {
        app,
        text: {
            type: "string",
            label: "Text",
            description: "Text of the Tweet being created. Required if `Media IDs` is not set.",
            optional: true,
        },
        inReplyToTweetId: {
            type: "string",
            label: "In Reply To Tweet (ID)",
            description: "Tweet ID of the Tweet being replied to. Please note that this prop needs to be set if `Exclude Reply User IDs` is also set.",
            optional: true,
        },
        excludeReplyUserIds: {
            type: "string[]",
            label: "Exclude Reply User IDs",
            description: "A list of User IDs to be excluded from the reply Tweet thus removing a user from a thread.",
            optional: true,
        },
        mediaIds: {
            type: "string[]",
            label: "Media IDs",
            description: "A list of Media IDs being attached to the Tweet. This is only required if `Tagged User IDs` is set.",
            optional: true,
        },
        taggedUserIds: {
            type: "string[]",
            label: "Tagged User IDs",
            description: "A list of User IDs being tagged in the Tweet with Media. If the user you're tagging doesn't have photo-tagging enabled, their names won't show up in the list of tagged users even though the Tweet is successfully created.",
            optional: true,
        },
        placeId: {
            type: "string",
            label: "Place ID",
            description: "Place ID being attached to the Tweet for geo location.",
            optional: true,
        },
    },
    async run({ $ }) {
        const { text, inReplyToTweetId, excludeReplyUserIds, mediaIds, placeId, taggedUserIds, } = this;
        const params = {
            $,
            data: {
                text,
                ...((inReplyToTweetId || excludeReplyUserIds) && {
                    reply: {
                        exclude_reply_user_ids: excludeReplyUserIds,
                        in_reply_to_tweet_id: inReplyToTweetId,
                    },
                }),
                ...((mediaIds || taggedUserIds) && {
                    media: {
                        media_ids: mediaIds,
                        tagged_user_ids: taggedUserIds,
                    },
                }),
                ...(placeId && {
                    geo: {
                        place_id: placeId,
                    },
                }),
            },
            fallbackError: ACTION_ERROR_MESSAGE,
        };
        const response = await this.app.createTweet(params);
        $.export("$summary", `Successfully posted tweet (ID ${response.data?.id})`);
        return response;
    },
});

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
X (Twitter)	`app`	`app`	This component uses the X (Twitter) app.
Text	`text`	`string`	Text of the Tweet being created. Required if `Media IDs` is not set.
In Reply To Tweet (ID)	`inReplyToTweetId`	`string`	Tweet ID of the Tweet being replied to. Please note that this prop needs to be set if `Exclude Reply User IDs` is also set.
Exclude Reply User IDs	`excludeReplyUserIds`	`string[]`	A list of User IDs to be excluded from the reply Tweet thus removing a user from a thread.
Media IDs	`mediaIds`	`string[]`	A list of Media IDs being attached to the Tweet. This is only required if `Tagged User IDs` is set.
Tagged User IDs	`taggedUserIds`	`string[]`	A list of User IDs being tagged in the Tweet with Media. If the user you're tagging doesn't have photo-tagging enabled, their names won't show up in the list of tagged users even though the Tweet is successfully created.
Place ID	`placeId`	`string`	Place ID being attached to the Tweet for geo location.

Action Authentication#

X (Twitter) uses OAuth authentication. When you connect your X (Twitter) account, Pipedream will open a popup window where you can sign into X (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 X (Twitter) API.

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

About X (Twitter)#

Formerly known as Twitter. From breaking news and entertainment to sports and politics, get the full story with all the live commentary. Use a X developer app you've created to send API requests.

More Ways to Connect X (Twitter) + HTTP / Webhook#

Other Popular Integrations#

Custom Request with HTTP / Webhook API on My Liked Tweets from Twitter API

X (Twitter) + HTTP / Webhook