---
title: "Cue and X (Twitter) with Bolta"
description: "Use Cue with Bolta's X (Twitter) content workflow."
canonical_url: "https://bolta.ai/integrations/cue/x"
markdown_url: "https://bolta.ai/integrations/cue/x.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Cue and X (Twitter) with Bolta

Source: https://bolta.ai/integrations/cue/x
Last updated: 2026-11-21

Use Cue with Bolta's X (Twitter) content workflow.

## Summary

Give a Cue agent your weekly social drafting, and approve it in Bolta This page focuses on X (Twitter).

## Who this is for

- Teams connecting Cue and X (Twitter)
- Cue users who publish to X (Twitter)
- Operators automating a review-first publishing workflow

## Core capabilities

- Hand one agent a weekly job: draft next week's LinkedIn and X posts and save them for your review
- Ask the agent each morning what is waiting for your approval in Bolta
- Let a writing agent in a group chat pass finished copy to your Bolta agent to save as a draft
- Have the agent read last month's account analytics and suggest what to post more of
- Set up a recurring routine in Bolta by describing it once to the agent, then approve the plan
- Check which brands and connected accounts the agent can reach before it drafts anything
- Supported content concepts: tweets, threads, polls, spaces announcements.

## Limitations and boundaries

- Current X (Twitter) support depends on its API and the connected account's permissions.
- Confirm the integration's current authentication and scope requirements before deployment.
- Cue must be connected to a Bolta workspace that already has a X (Twitter) account linked; the integration cannot create that connection on its own.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## How Cue reaches X (Twitter)

Cue does not talk to X (Twitter) directly. It calls Bolta, and Bolta holds the connected X (Twitter) account, its tokens, and its publishing rules. That means one connection is maintained in one place rather than per tool, and the same draft, review, schedule, and publish states apply whether the work started in Cue or in the Bolta app.

## Where approval sits

Requests that arrive from Cue are subject to the same workspace approval settings as anything else. A drafted X (Twitter) post lands in the review queue rather than going straight out, unless the workspace has explicitly been configured otherwise. Connecting a tool widens who can create work; it does not widen who can publish it.

## Relevant links

- [Related page: /integrations/cue](https://bolta.ai/integrations/cue)
- [Related page: /integrations](https://bolta.ai/integrations)
- [Bolta pricing](https://bolta.ai/pricing)
