Pipedream

Build Pipedream workflow automation for tweet search, profiles, trending tweets, HTTP triggers, and approved posts through TwexAPI.

Build a Pipedream Twitter integration for searches, profiles, trending tweets, and approved posts. TwexAPI supplies one REST API and one API key for every workflow.

Choose a webhook trigger for agent handoffs, a schedule trigger for recurring searches, or inline code steps when you need custom normalization.

Choose a Pipedream automation pattern

Split searches, webhook handoffs, follower exports, and approved writes into separate workflows. Smaller workflows expose errors and rate limits more clearly.

Prerequisites

• TwexAPI API key
• Pipedream account
• Optional connected accounts for Slack, Google Sheets, Airtable, or a database
• Optional MCP-capable agent connected to https://api.twexapi.io/mcp

Serverless API integration

Start every TwexAPI request at https://api.twexapi.io. Send the API key through the Authorization: Bearer header. Keep keys in Pipedream environment variables, not step exports or logs.

export TWEXAPI_API_KEY="YOUR_API_KEY"

Use GET /balance as the first authentication check. It verifies the API key without changing an X account.

Shared request helper

export default defineComponent({
  props: {
    twexapi: {
      type: "string",
      label: "TwexAPI API Key",
      secret: true,
    },
  },
  methods: {
    async twexapiRequest($, { method, path, body, params }) {
      const url = new URL(`https://api.twexapi.io${path}`);
      if (params) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== null) {
            url.searchParams.set(key, String(value));
          }
        });
      }

      const response = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${this.twexapi}`,
          "Content-Type": "application/json",
        },
        body: body ? JSON.stringify(body) : undefined,
      });

      if (!response.ok) {
        throw new Error(`TwexAPI request failed with HTTP ${response.status}`);
      }

      return response.json();
    },
  },
});

Starter actions

Search tweets code step

export default defineComponent({
  async run({ steps, $ }) {
    const response = await fetch("https://api.twexapi.io/twitter/advanced_search/page", {
      method: "POST",
      headers: {
        Authorization: `Bearer ${process.env.TWEXAPI_API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({
        searchTerms: ["AI agents lang:en"],
        sortBy: "Latest",
        nextCursor: "",
      }),
    });

    if (!response.ok) {
      throw new Error(`TwexAPI request failed with HTTP ${response.status}`);
    }

    return response.json();
  },
});

Webhook-first flow

1. Create an HTTP trigger in Pipedream.
2. Ask an MCP-capable agent to collect TwexAPI rows and return strict JSON.
3. POST the JSON to the Pipedream endpoint.
4. Normalize and dedupe rows in a code step.

JavaScript normalization step

export default defineComponent({
  async run({ steps }) {
    const payload = steps.trigger.event.body;

    return (payload.tweets || []).map((tweet) => ({
      id: tweet.tweet_id || tweet.id,
      url: tweet.public_url ?? `https://x.com/i/web/status/${tweet.tweet_id || tweet.id}`,
      author: tweet.author_username,
      text: tweet.text || tweet.full_text,
      created_at: tweet.created_at,
      route_used: payload.route_used,
      next_cursor: payload.next_cursor,
    }));
  },
});

Suggested MCP agent prompt:

Use Twexapi MCP to get quote tweets for tweet ID 1803006263529541838.
Return only JSON with route_used, source_tweet_id, has_more, next_cursor, and tweets.
Each tweet must include tweet_id, author_username, text, created_at, and public_url.
Do not call write endpoints.

Result handoff

Error handling

Route each status before exporting downstream rows.

Persist a page cursor only after downstream processing succeeds.

Recipes

Search tweets to Slack

1. Schedule the workflow on your reporting cadence.
2. Call POST /twitter/advanced_search/page.
3. Filter tweets by engagement threshold.
4. Send selected tweet text, author, and link to Slack.

Agent handoff to Google Sheets

1. HTTP trigger receives MCP handoff JSON.
2. Normalize tweet rows.
3. Upsert into Sheets by tweet_id.

Follower page to CRM

1. HTTP or scheduled step calls POST /v3/twitter/users/followers.
2. Normalize follower rows.
3. CRM upserts by user_id.
4. Data store retains next_cursor.

Testing checklist

• Confirm the trigger body is valid JSON.
• Use tweet_id or user_id as the dedupe key.
• Store next_cursor in Pipedream data stores for scheduled continuation.
• Keep TWEXAPI_API_KEY in environment variables only.
• Never log Bearer tokens in step output.

Next steps

• Make
• Zapier
• n8n
• Agent MCP Handoff
• API Reference