Make to Buffer to X stopped with "message is too long": the fix was one button
My Make scenario that posts to X stopped with the error “message is too long for Twitter”. The cause was not the scenario. Buffer still treated my X account as a free account.
The fix was one button in Buffer’s settings. I did not change anything in Make.
This post covers the setup, the error, the cause, and what I check now.
What it does
It is a small automation for an X account I run for my own work. Make sends each post to Buffer, and Buffer publishes it to X.
The account is on X Premium. X’s help center says a normal post is limited to 280 characters, and Premium allows longer posts of up to 25,000 characters.
The stack and the flow
The stack is Make, Buffer and X. The flow has two steps that matter here:
- Make builds the post text.
- Buffer – Create a status update sends it to the X channel.
Buffer then publishes it. The post text stays the same in both tools. The error came from the Buffer module, so the length check that stopped it was on Buffer’s side.
What it costs
My whole Make account runs on the Core plan, with 10,000 credits a month. The invoice is $10.59 (about ¥1,700) a month.
I do not yet know how many credits this one scenario uses. I also have not written down the Buffer plan price or the X Premium price.
The fix itself was a settings change in Buffer, not a change to the Make scenario.
What broke and how I fixed it
The scenario stopped at the Create a status update module in Make. The error message was “message is too long for Twitter”.
That looked like a Make problem at first. It was not. Make only passes the text along.
The cause: Buffer still saw a free account
I had connected the X account to Buffer before I subscribed to X Premium. Buffer kept that old connection. In Buffer, the channel was still labeled “X Free Profile”, which means a 280-character limit.
So X knew I was on Premium. Buffer did not. The limit that blocked the post came from Buffer’s side.
The fix: refresh the connection
I opened the channel settings in Buffer and pressed Refresh Connection. Then I approved the X permissions again.
After that, the channel label changed to “X Premium Profile”. Buffer showed the new limit as 25,000 characters. The next post went through.
I had an AI browser assistant (Claude in Chrome) open the settings page and press the button. You can do the same clicks by hand.
What I’d do differently
The rule is simple: when you change a plan on one tool, refresh the connection in every tool that talks to it. The plan change does not travel by itself.
Here is what I check now:
- Read the channel label. I look at the profile type that Buffer shows for the channel, not only at my X account.
- Refresh after any plan change. If I change my X plan, I press Refresh Connection in Buffer.
If you want to build something like this yourself, you can sign up for Make with my link. It gives you the Core plan free for the first month, and I earn a commission if you stay on a paid plan.
Last checked: November 14, 2026. Plan: Make Core. The 280 and 25,000 character limits are from X’s help center on that date.