My AI tool is connected to X but can't post. What can AI connectors actually do?

What happened

We connected an AI assistant to an X account so it could handle posting. We built the plan around that.

It turned out the connection was read-only. It could read bookmarks and messages. It couldn't publish anything.

The backup plan was to have the AI log in through a browser. That failed too. The account used Google sign-in, and Google blocks automated browsers from signing in.

So we switched to a social media scheduler that is allowed to post. That had its own limits. On the free plan it capped out at 10 scheduled posts shared across all channels, and it couldn't pin posts or post replies.

Why it happened

"Connected" doesn't mean "can do everything." Every connector has a list of actions, and that list is often much shorter than the app itself. Reading is common. Writing, posting or deleting is often missing or locked behind a separate permission.

The AI won't always tell you this upfront. Ask it to "post this" and it may try, fail, and then try a riskier route, like logging in through a browser.

Salesforce connectors work the same way. One may read records but not update them. Another may update records but not run flows. Plan around the actual list, not the logo.

The fix, step by step

1. Get the list of actions before you plan. Ask the AI: "List every action this connector can take. Read, create, update, delete, post." Then check the connector's docs.
2. Run one harmless test of the action you need. A test post on a test account, or an update to a sandbox record.
3. Check the sign-in method. Google or Microsoft sign-in will usually block browser automation. Plan for that.
4. Use the tool that's allowed to do the job. For us, that was a scheduler with real posting rights.
5. Read the plan limits. Post caps, channel caps, and missing features like replies and pinning.

How to check it worked

• Plant an action the connector can't do. Ask the AI to do it. It should say it can't, not try a workaround.
• Schedule one test post and confirm it actually went live.
• Write down the limits you found, so the next plan starts from them.