Connecting an X account

Connect the X account to the correct Sequence brand. The connection is complete only after the platform authorisation finishes and the intended account returns to Sequence as Active.

Sign in to the X account the Sequence brand should publish from. Check the username carefully before granting access.

1. Select the workspace and brand that should own this connection.

2. In the sidebar, open Brand and select Channels. Under Add social account, choose X.

3. Read the connection explanation, including what posting to X and X stats cost in credits, and select Continue to X.

4. X shows the signed-in account and the permissions requested by the connection. Confirm the username, review the access, and authorise the app to finish connecting.

5. Return to Sequence. Under Connected Channels, confirm that the intended account appears and its connection is Active.

X charges for every post and every stats read, so posting to X and X stats use credits from your workspace's balance, the same credits that pay for AI features.

X stats are off by default. To see impressions and engagement for an X account's posts, turn on the X stats switch on that account's card in Channels. Each tweet is charged once, and its stats update for its first 7 days. Tweets posted directly on X count too. Turn the switch off at any time to stop the charges; stats already collected stay.

If the workspace does not have enough credits, Sequence holds back the X post and shows the reason before anything is sent. If credits run out while X stats are on, the stats switch off and the workspace owners and admins are notified.

If the wrong X account appears, cancel the authorisation, switch accounts on X, and start again. If the authorisation is denied or cancelled, no connection is created and you can safely repeat the flow.

If the provider window was closed before authorisation finished, or your browser blocked the pop-up, return to Channels and start the connection again. If Sequence shows a workspace limit or role message, resolve that message with your workspace administrator before retrying.