CrewAI Integration

Post to X from a
CrewAI crew

Give one agent a tweeting tool and your crew can write, review, and publish to X on its own. It calls the OpenTweet API, so there is no X developer account, no OAuth, and no per-post billing.

Get your API key

7-day free trial. No X developer account needed.

What your crew can do on X

Assign these as tools and let each agent use only what its role needs.

Post now

A single tool call from any agent publishes a tweet immediately.

Schedule

The crew can plan ahead and queue posts for the best times.

Threads

Turn a long task output into a connected thread in one call.

Media

Attach images or let OpenTweet generate visuals for the post.

Role separation

Only the publisher agent holds the posting tool. Writers just draft.

No X API

No developer account, no OAuth, no token refresh in your crew.

A tweeting tool in a few lines

Define a custom CrewAI tool that POSTs to the OpenTweet API and hand it to your publisher agent. No X developer portal, no OAuth handshake.

import httpx
from crewai.tools import tool

@tool("Post to X")
def post_to_x(text: str) -> str:
    """Publish a tweet to X (Twitter) and return a confirmation."""
    httpx.post(
        "https://opentweet.io/api/v1/posts",
        headers={"Authorization": "Bearer ot_your_api_key"},
        json={"text": text, "publish_now": True},
        timeout=30,
    ).raise_for_status()
    return "Tweet published"

# Give the tool to the agent that should publish
publisher = Agent(
    role="X Publisher",
    goal="Post approved tweets to X",
    tools=[post_to_x],
)

Want the full toolset? Connect the OpenTweet MCP server for all 30 tools.

Perfect for

Content crews

A researcher, a writer, an editor, and a publisher agent that ships the approved tweet through OpenTweet.

Newsroom bots

Agents pull stories, summarize them, and post the best ones to a faceless news account 24/7.

Launch announcements

A crew watches your changelog and drafts, reviews, and posts release notes automatically.

Multi-account operators

Route different crews to different X accounts through one OpenTweet key.

Frequently asked questions

How do I make a CrewAI agent post to Twitter?

Define a custom CrewAI tool that POSTs to the OpenTweet API and assign it to the agent that should publish. When that agent runs its task, it calls the tool and the tweet goes live. No X developer account or OAuth is needed.

Do I need my own X (Twitter) API credentials?

No. Most CrewAI Twitter examples stall because they require raw X API keys, a developer application, and OAuth. OpenTweet gives you one bearer key that replaces the whole X auth flow, so your crew posts without the X API.

Can one agent write and another post?

Yes, that is the natural CrewAI pattern. A writer agent drafts the tweet, an editor agent reviews it, and a publisher agent that holds the posting tool ships it. Each agent only gets the tools it needs.

Can the crew schedule tweets or post threads?

Yes. The OpenTweet API accepts a schedule time, thread arrays, and media, so you can add separate tools for post now, schedule, and thread. You can also connect the OpenTweet MCP server to expose all 30 tools at once.

What does it cost to run a CrewAI posting agent?

OpenTweet is a flat $11.99/month and absorbs the underlying X cost at normal posting volumes. There is no per-post fee and no link-post surcharge, unlike the pay-per-use X API.

Let your crew ship to X

Connect X, copy your key, and add the posting tool to your publisher agent today.

Start your 7-day free trial