WEIR
Get a key
Theme

Make.com Twitter Integration Discontinued: What Works Now

Make ended its X app in 2025, and the Make.com Twitter integration with it. Get new X posts into scenarios with a Weir monitor, a webhook and a Router.


Published · Updated · 7 min read

Cover image: New X posts, into Make

The Make.com Twitter integration is discontinued: Make removed its X app in 2025, so no scenario can watch X directly.

You can still read new X (Twitter) posts in Make. A Weir monitor finds them and posts them to your Custom webhook, and a Router sends each one where you want it. We run Weir.

Register your Make webhook address with Weir in one call:

curl -X POST https://api.weirapp.io/v1/webhooks \
  -H "Authorization: Bearer $WEIR_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"name": "Make", "url": "https://hook.eu1.make.com/your-webhook-id"}'

You need a Weir API key, a Make account, and a Google Sheet or a Slack workspace.

Step 1: Catch Weir's delivery with a Custom webhook

Start the scenario with the webhook, so you have an address to give Weir.

  1. Add the triggerIn a new scenario, add Webhooks, then Custom webhook. Create a webhook and copy its address.
  2. Turn on two optionsIn Advanced settings, set Get request headers and JSON pass-through to Yes.
  3. Register it with WeirIn the dashboard, open Webhooks, then Add a webhook. Paste the address and copy the whsec_ secret. It's shown once.
  4. Send the free testPress Run once in Make, then send the test call below.
curl -X POST https://api.weirapp.io/v1/webhooks/$WEBHOOK_ID/test \
  -H "Authorization: Bearer $WEIR_API_KEY"

Why JSON pass-through? Make's docs say it passes the body on "as a text string." Weir signs the exact bytes it sent, so your check needs that string, not parsed fields.

Make answers each delivery with a 200 and "Accepted" before your scenario runs. So Weir marks it delivered, even if a later module fails, and won't send it again.

Step 2: Check Weir's signature in a filter

Make's docs say sha256(text; [encoding]; [key]) returns an HMAC when you give it a key. That's Weir's scheme: HMAC-SHA256 over timestamp.eventId.rawBody, in hex.

Without this filter, the webhook address is your only secret. Anyone who learns it can push fake posts into your scenario.

First, read each header out of the headers array with map and first:

first(map(1.`__IMTHEADERS__`; "value"; "name"; "weir-signature"))
first(map(1.`__IMTHEADERS__`; "value"; "name"; "weir-timestamp"))
first(map(1.`__IMTHEADERS__`; "value"; "name"; "weir-event-id"))

Then put a filter on the link after the webhook, with two conditions joined by AND. In each pair of braces, drop in the matching header formula:

sha256({timestamp}.{event id}.{1.value}; hex; whsec_your_secret)
    Text operators: Equal to
{signature}

parseDate({timestamp}; X)
    Datetime operators: Later than
addMinutes(now; -5)

The second condition drops deliveries over five minutes old, as Weir's docs advise. Make's token table says X reads a Unix timestamp. Anyone who can edit the scenario can read your secret.

Press Run once and send the test again. If you see it pass the filter, your check works.

Step 3: Add a monitor, then split and route the posts

Create your monitor first, so Make can see real posts. In the Weir dashboard, pick a keyword search or an X account and choose your webhook. Or send this to POST /v1/monitors:

{
  "name": "Acme on X",
  "target": { "kind": "search", "query": "acme", "sources": ["x"] },
  "schedule": "daily",
  "webhookId": "<webhook id>"
}

Then add these modules after the filter:

  1. Parse JSONJSON string: the webhook's value. Leave Data structure empty.
  2. Load real postsPress Run once in Make, then Run now on the monitor's page. Make builds the structure from that delivery.
  3. IteratorArray: data.results from Parse JSON. Each post becomes its own bundle.
  4. RouterRoute 1 goes to Slack's Create a Message, filtered on author followersCount of 50,000 or more. Route 2 goes to Google Sheets Add a Row, with no filter.

A post can take both routes, so every post lands in the sheet and big accounts also ping Slack.

We ran a real search on 22 October 2026 and built a delivery from its three posts. The search cost 4 credits. Through the same logic, the posts routed like this:

→ search_x {"fromUsers": ["zapier", "make_hq"], "query": "-filter:nativeretweets", "onlyOriginal": true, "limit": 3}
← 3 posts · 4 credits (1 + 3 × 1)
Filter: signature ok, age ok → Parse JSON → Iterator: 3 bundles
  @zapier    96,987 followers  10 likes  → Slack + Sheets
  @zapier    96,987 followers  17 likes  → Slack + Sheets
  @make_hq   31,990 followers   0 likes  → Sheets

Both @zapier posts cleared the 50,000-follower floor, so they went to Slack and the sheet. The @make_hq post went to the sheet only.

Each run sends you one delivery with up to 25 new posts. If data.newResults is higher, the monitor results endpoint has the rest, free.

Why did Make discontinue the X (Twitter) app?

Make's X (Twitter) modules were discontinued over X's API policy requirements and pricing. Make says those stop it "providing a reasonable integration to our customers."

Date What Make said
3 Apr 2025 No new X scenarios
30 May 2025 Existing X scenarios stop working

After that, Make says old X scenarios stay visible but "will fail upon execution." For posting, it points to Buffer and Hootsuite.

Posting is out of scope here. Weir only reads public data, so it can't replace Make's old X posting modules.

What it costs

You pay Weir a credit per monitor run plus a credit per new X post. Deliveries and tests cost you nothing.

330credits a month for a daily watch finding 10 new posts a day
21credits for a full run of about 20 new posts
5,000free Weir credits every month
1,000Make credits a month on Make's Free plan

Make's pricing page says every module action uses credits, and the Router uses none. So each sheet row and Slack message costs you Make credits too. Weir's own rates are on the pricing page.

If it doesn't work

  • The filter stops Weir's test. Check JSON pass-through is on and you pasted the whole secret, whsec_ included. If it still fails, Make may be changing the body.
  • Weir logs a 410. Make turns off a webhook that has no scenario for over five days. Weir doesn't retry a 4xx.
  • Weir logs "Queue is full". That's a 400, so Weir won't retry it either. Make's queue size grows with your plan.
  • The age check fails. Your scenario handles its queue on a schedule. Let it run as soon as data arrives.
  • The same post twice. Delivery is at least once, and a retry keeps its weir-event-id.

When not to use Weir

  • You need to post or reply on X. Weir is read-only, so pick a tool with write access to your account.
  • You need posts within seconds. Your monitor runs hourly at best on paid tiers, and daily on the free tier.
  • Price per post matters most. TwitterAPI.io lists $0.15 per 1,000 tweets as of October 2026, less than Weir's smaller packs.
  • You want a guarantee. Weir isn't licensed by X, so access can change.

FAQ

Does Make still have a Twitter integration?

No. Make removed its X (formerly Twitter) app in 2025. Scenarios that used it stopped working on 30 May 2025. You can still bring X posts into Make through a Custom webhook.

Is there a Make X integration alternative for reading posts?

Yes: a webhook. Any service that watches X and posts to a URL can start your scenario. A Weir monitor watches a keyword or one account and sends only posts it hasn't sent before.

Can Make post to X through Weir?

No. Weir reads public X data and can't post, like or follow. Make's own notice suggests Buffer and Hootsuite for posting.

How often does Weir send new posts?

Once per monitor run. On a free account you can run daily or weekly, and paid tiers can run hourly. It's a schedule, not a live stream.

Sources

Keep reading