# Multiple call twitter node according to results set

**URL:** <https://community.n8n.io/t/multiple-call-twitter-node-according-to-results-set/10345>\
**Category:** Questions\
**Tags:** node\
**Created:** [January 5, 2022, 9:43am UTC](https://community.n8n.io/t/multiple-call-twitter-node-according-to-results-set/10345 "2022-01-05T09:43:57Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\
**Post date:** [January 5, 2022, 4:21pm UTC](https://community.n8n.io/t/multiple-call-twitter-node-according-to-results-set/10345/8 "2022-01-05T16:21:54Z")

</div>

Oh no ☹, I am really sorry to hear that. If Twitter doesn’t grant you elevated access, it’s unfortunately not possible to use their API v1.1 endpoints used by the Twitter node.

That means until we have developed a node using Twitter’s v2 API you would have to use the HTTP Request node to talk to this Twitter API directly. A simple example workflow fetching Tweets would be available [here](http://community.n8n.io/t/twitter-oauth-immediately-errors/10156/4). Other endpoints are listed in their docs, e.g. [this one](https://developer.twitter.com/en/docs/twitter-api/tweets/manage-tweets/api-reference/post-tweets) for posting Tweets.

The credentials I’ve used to authenticate with Twitter here are OAuth1 credentials with the following values:

Authorization URL: `https://api.twitter.com/oauth/authorize`  
Access Token URL: `https://api.twitter.com/oauth/access_token`  
Request Token URL: `https://api.twitter.com/oauth/request_token`  
Consumer Key: The **API Key** shown in Twitter’s developer portal  
Consumer Secret: The **API Key Secret** shown in Twitter’s developer portal  
Signature Method: `HMAC-SHA1`

Let me know if you run into any trouble with this!

---

_[View the full topic](https://community.n8n.io/t/multiple-call-twitter-node-according-to-results-set/10345)._