Twitter

Connect Rocketbots to Twitter.

Twitter is an American online news and social networking service on which users post and interact with messages known as "tweets". As of 2016, Twitter had more than 319 million monthly active users and is one of the top 10 most visited websites.

The Twitter Logo

For a detailed list of features against the other channels, you can take a look at the comparison table.

Setting Up Twitter

In order to connect Twitter to your Space, you will need the following:

Note that new developers must apply using their Twitter Account and wait for approval from Twitter.

Creating an Twitter App

First, you must create an App on Twitter for your Space to connect to. Head over to the Twitter App Dashboard and log in with your Twitter Developer Account.

Under the Twitter App Dashboard, press the "Create an App" button to create a new Twitter App. You should be prompted to fill in some information about your new Twitter App under the Application Details section.

Creating a Twitter App

Once you have filled in the required fields, accept their Terms and Conditions under the Developer Agreement section. Finally, press the "Create your Twitter Application" button to create your Twitter App.

Enabling Permissions

Now that you have created your Twitter App, there are some permissions you must enable. On the Twitter App Dashboard, select the "Permissions" tab. Under the "Permissions" tab, press the "Edit" button to start making changes.

From the Permissions area, select the "Read, write, and Access direct messages" option. Then press the "Update Settings" button at the bottom of the page to save your changes.

Setting up a Dev Environment

For the Rocketbots Platform to connect to your Twitter App, you must also create a Dev Environment on Twitter.

Navigate to the Twitter Dev Environments page and press the "Set up Dev Environment" button under the Account Activity API section to set up a Dev Environment.

You will have to input the Twitter App ID of the Twitter App you just created.

Once you have set up your Dev Environment, take note of your Dev Environment Label. You will need to later when connecting your Space to Twitter.

Connecting to Twitter

On the Rocketbots Platform, select the Telegram Logo under the Channel Connection menu. You will be prompted for the Channel Name, a Greeting Message, API Key and Secret Key, Access and Secret Tokens, and the Dev Environment Label.

Enter a suitable name for the new channel. Note that the Channel Name is private and will only be used within the Rocketbots Platform.

You may enter an optional Greeting Message. This will be shown when a new member of your audience first contacts you.

Keys and Tokens

To find the authorization Keys and Tokens for your Twitter App, navigate to the "Keys and Tokens" tab on the Twitter App Dashboard.

Under the Keys and Tokens tab, you should be able to find the Consumer Key and Consumer Token. Copy these into the API Key and Consumer Token fields respectively on the Platform.

Here, you can also find the Access Token and Access Token Secret. Copy these into their respective fields on the Rocketbots Platform as well.

Dev Environment Label

For the Dev Environment Label field, paste the Dev Environment Label of the Dev Environment you set up.

You can access the Twitter Dev Environments page if you have forgotten your Dev Environment Label.

Once you have filled in the required fields, go ahead and press the blue "Done" button to create the Space.

Any direct messages sent to your Twitter Account will now be received in your Space on the Rocketbots Platform.

Enabling Direct Messages

In order for your Twitter Account to receive direct messages from anyone, including accounts it does not follow, you must enable Direct Messages on your Twitter Account.

Navigate to your Twitter Account's Privacy and Safety options under Settings. Select the "Receive Direct Messages from anyone" option under "Direction Messages" in the "Safety" section.

Once you have enabled the direct messages option, press the "Save Changes" button at the bottom.