Hi there,
as we know to send an image to Twitter you have to push it using an HTTP node… my problem is that I can’t create a connection every time I get " Error: Request failed with status code 401"
although the Twitter node itself is working and sends text tweets well.
any suggestions
Using the last n8n stable cloud version
n8n
December 9, 2024, 6:00am
2
It looks like your topic is missing some important information. Could you provide the following if applicable.
n8n version:
Database (default: SQLite):
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app):
Operating system:
I try a system called buffer to test my connection and it’s working well this means no any block on my free plan or my API credentials.
Now am asking about a problem in the cloud version.
could u please anyone test it and inform if this problem happened ot not
Am not sure from that but this is what am encounter now:
I think the problem is related to using Free plain on X developer, although am using other tool using the below info and send tweet with image !!
API key*
API secret *
Twitter username *
Access token *
Access token secret *
if any one have an explanation?
Ukly0
December 18, 2024, 1:11pm
7
I’ve been having the same problem for days, what tool are you using to upload the tweet with an image?
401 error is unauth error.
So probably you missing something or you need to refresh credential for new token
you need to use standard v1.1
the problem I use it and it’s working well in other system ( WordPress plugin)
could you please check this:
2 Likes
Ukly0
December 20, 2024, 12:18pm
12
Any update or alternative to upload an image to twitter from my workflow?
Following. Same issue here
what return in more details ?
have you try with oauth2.0 authentications ? Actually im using oauth2.0
have you try this end point? you need before upload and after create a tweet with the image id
thanks so much for ur support,
I use the same endpoint mentioned by u in the HTTP node to upload the image. but the problem in the connection itself.
the twitter node is working with oauth2.0 and I can tweet text with it only.
in your video i see oauth1
in case of using Oauth2 i get error 403