X

The X connector owns organic marketing work. It uses Oblive’s packaged direct provider for profiles, posts, replies, quotes, engagement, follows, Lists, Articles, analytics, and approved media uploads. It is separate from X Ads.

Before You Connect

The deployment administrator configures xOAuth.clientId and the exact callback URL registered with an X developer App using OAuth 2.0 Authorization Code with PKCE. Web Apps, Automated Apps, and Bots also set xOAuth.clientSecret; Native Apps and SPAs omit it. Without the local-stack generator, set X_OAUTH_CLIENT_ID, optional X_OAUTH_CLIENT_SECRET, and X_OAUTH_REDIRECT_URI on the backend.

When the secret is present, token exchange, refresh, and revocation use confidential-client Basic authentication. Without it, the same connector uses the public-client PKCE flow.

Choose:

• Read-only for discovery, conversation context, audiences, Lists, media status, and analytics.
• Full access for reviewed publishing, replies, quotes, moderation, engagement, follows, Lists, Articles, and media uploads.

Chat remains read-only. Consequential work runs as a Growth task through the action lifecycle.

Connect X

1. Open Integrations and select X.
2. Choose read-only or full access.
3. Select Continue to X and approve the requested permissions.
4. Return to Oblive and confirm that the integration reports ready.

The organization token stays encrypted in the backend. Workers receive a scoped gateway capability, not the token.

Organic Tool Surface

• Resolve the connected identity, other users, posts, mentions, and follower graphs.
• Search posts and inspect post engagers.
• Read available post analytics with fixed metric fields.
• Create original posts, replies, quotes, polls, and posts with uploaded media.
• Delete posts and manage likes, reposts, bookmarks, follows, and reply visibility.
• Read and manage Lists.
• Create Article drafts and publish reviewed drafts.
• Read media processing status.

There is no arbitrary X API path or unrestricted request-body tool.

Private Media

Growth task runs receive the x-media companion only when the integration has full access. The worker hashes one regular workspace file, uploads it to an invocation-owned private object key, and the backend verifies ownership, size, type, signature, and SHA-256 before proposal and execution.

The companion infers:

• JPEG, PNG, or WEBP as tweet_image;
• GIF as tweet_gif; and
• MP4 or MOV as tweet_video.

The resulting media ID can be used with x_create_post. Approval-required and uncertain outcomes stop the task for human handling instead of retrying the external effect.