X
Connect an X account so Robylon receives its X Chat DMs, @mentions and replies to its posts, answers them with AI or from your team, and starts workflows from X triggers.
Connect X (formerly Twitter) from Settings → Channels → All Channels by clicking X under Other Channels and signing in to X. Robylon then receives the account’s X Chat DMs, the posts that @mention it, and replies to its posts, and answers them in the unified inbox.
X sends each new message to Robylon as it happens, so nothing is polled. You do not need your own X developer account: Robylon connects through its own X app.
Connect an X account
Sign in to X in a pop-up window and approve access for Robylon.
Open the channel
Go to Settings → Channels → All Channels and click X under Other Channels.
Sign in to X
An X window opens. Sign in with the X account you want Robylon to answer for, and approve the permissions. Finish within 10 minutes: the sign-in link expires after that. Allow pop-ups for app.robylon.ai if nothing opens.
Check it is connected
The window shows Authentication Successful and closes. X moves to Connected Channels. Click it to see your accounts under Connected X Accounts, each listed by its @handle and X account ID.
Enter the X Chat passcode
If the account’s DMs need its X Chat passcode, Enter X Chat Passcode opens straight away. See Enter the X Chat passcode.
One X account can belong to one Robylon workspace at a time.
Permissions Robylon requests
X shows these permissions during sign-in.
| Permission | What Robylon uses it for |
|---|---|
tweet.read |
Read the posts that mention the account or reply to it. |
tweet.write |
Post replies. |
users.read |
Read the account’s profile and the profiles of customers who write to it. |
dm.read |
Read direct messages. |
dm.write |
Send direct messages. |
media.write |
Attach images and GIFs to reply posts. |
offline.access |
Stay connected without asking you to sign in again. |
The connection fails if users.read or offline.access is declined.
Connect more than one account
Open X from Connected Channels and click Add new X account, then sign in with the other account. Each sign-in adds one account and keeps the accounts already connected. Signing in again with an account that is already connected refreshes its access and keeps its settings.
Disconnect an account
Open X from Connected Channels, click the icon next to the account, and confirm. Robylon stops receiving the account’s messages and revokes its access on X, so you do not need to remove Robylon in your X settings. When you disconnect the last account, X moves back to Other Channels.
Enter the X Chat passcode
Robylon needs the account’s 4-digit X Chat passcode before it can read and answer DMs. X Chat messages are end-to-end encrypted, and the passcode unlocks the account’s encryption keys. Robylon uses the passcode once to unlock the keys and never stores it. Mentions and replies to posts work without it.
The passcode is the one set in the X app’s Chat settings. If Chat was never set up in the X app, set it up there first, then enter the passcode in Robylon.
Open the passcode window
Enter X Chat Passcode opens by itself after you connect an account that needs it. To open it later, go to Settings → Channels → All Channels, click X under Connected Channels, and click Enter Passcode on the account.
Enter the passcode
Type the 4 digits under Your X Passcode and click Unlock.
Until the passcode is entered, the account shows “Direct messages are paused until you enter the X Chat passcode.” and the X card shows a warning: “One or more accounts needs passcode”. DMs that arrive while DMs are paused do not appear in Robylon.
If you reset X Chat in the X app later, Robylon can no longer read new DMs and asks for the passcode again. Enter the new passcode with Enter Passcode.
Messages Robylon receives from X
Robylon receives 3 kinds of message for each connected account:
| Message | Where it appears |
|---|---|
| X Chat DMs | One chat per DM conversation. |
| Posts that @mention the account | One chat per post thread. |
| Replies to the account’s posts | One chat per post thread. |
A DM conversation and a post thread with the same customer are separate chats. A customer’s later replies in a post thread join that thread’s chat. The account’s own posts and DMs never start a chat.
Photos, GIFs and videos attached to a customer’s post appear in the chat, and Robylon keeps a copy so they stay visible if the post is deleted. From X Chat DMs, Robylon receives the message text only.
X chats belong to the Chat channel group, so they appear under X in the inbox Channel filter, in analytics, and in chat macros and assignment.
Each customer is identified by their X account, so a customer who changes their @handle stays the same user. Their name in Robylon is their X username.
Replies on X
Robylon answers in the same place the customer wrote: a DM chat gets an X Chat DM, and a mention or reply chat gets a reply post under the customer’s latest post in that thread.
| Reply post (mention or reply chat) | X Chat DM | |
|---|---|---|
| Text | Sent as plain text | Sent as plain text |
| Images | Up to 4 images or GIFs attached, up to 5 MB per image and 15 MB per GIF | Sent as links |
| Video, larger files, other files | Sent as links | Sent as links |
Robylon sends the whole reply and X applies its own character limit. If X rejects a reply, the message is marked failed in the chat with X’s error, and a workflow step that sent it fails.
Buttons and carousel buttons become a numbered list that starts with “Reply with a number:”. When the customer replies with a number, Robylon treats it as a click on that option. Carousel buttons that open a link are left out.
Status messages are not sent on X: the customer is not told when the chat is assigned, waiting for an agent, or closed.
Workflow triggers for X
Pick the X account in a workflow trigger, under X. Each trigger applies to one X account. See Triggers.
| Trigger | When it starts |
|---|---|
| When a DM is received | A customer sends the account an X Chat DM. |
| When the account is mentioned or replied to | A post @mentions the account or replies to one of its posts. |
| When a chat is handed over outside office hours | A chat is handed to your team outside office hours. |
| When a chat workflow terminates abruptly | A workflow running in an X chat stops unexpectedly. |
| When a chat workflow gets a no match | The workflow cannot match the customer’s message. |
| When a user becomes unresponsive during chat | The customer stops replying for the duration you set. |
A post thread starts at most one workflow. A later reply in a thread that already has a chat goes to the workflow still running there, or to the inbox, and does not start a new workflow. Chats that are handed over to your team or resolved also go to the inbox only.
Connecting does not make the AI reply. Messages are only answered automatically once a published workflow has an X trigger for the account. There are no X actions in the Integration block.
Connection errors
If sign-in fails, the X window shows Authentication Unsuccessful and closes, and no account is added. The usual causes:
| Cause | What to do |
|---|---|
| You took longer than 10 minutes to finish signing in. | Click X or Add new X account again and finish within 10 minutes. |
| You cancelled sign-in or declined access. | Connect again and approve access. |
You declined users.read or offline.access. |
Connect again and approve all permissions. |
| The X account is already connected to another Robylon workspace. | Disconnect it from that workspace first. An X account can belong to one workspace at a time. |
If the window does not open at all, allow pop-ups for app.robylon.ai in your browser.
Errors from Unlock in Enter X Chat Passcode:
| Message | What to do |
|---|---|
| Incorrect X Chat passcode | Check the 4-digit passcode in the X app’s Chat settings and try again. Each wrong attempt counts against X’s limit. |
| X account has no X Chat passcode backup | Chat is not set up for this account. Set it up in the X app, then enter the passcode. |
| X Chat is unavailable | Robylon could not reach X Chat. Try again later, and email support@robylon.ai if it keeps failing. |