X (Twitter)

Ownership and availability#

You own the X account. Obelo manages OAuth 2.0 PKCE and stores refresh credentials server-side.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Before you connect#

• Access to the X account that will publish approved content
• The account must not be restricted from posting
• An Obelo workspace owner or admin completes OAuth

Connect an existing account#

1. Open the provider in Settings → Integrations for the intended website.
2. Sign in to the target X account
3. Approve Obelo's requested read, write, user, and offline access
4. Return to Obelo and verify the displayed account handle

If you need a new resource#

1. Create the brand's X account and complete its profile
2. Secure the account with recovery details and multi-factor authentication
3. Post once manually if X requires account activation before OAuth publishing

Permissions to check#

• tweet.read and users.read verify the publishing identity
• tweet.write publishes approved content; offline.access keeps scheduled publishing connected

Verify and troubleshoot#

After the account is active, return and reconnect with that exact X identity.

X did not return a usable publishing identity. Confirm the account is active and the requested permissions were approved.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access#

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.