--- title: "X" description: "Let a playbook read your X posts, mentions and recent search results, and create, edit and delete posts as you, under your organization's own X app." url: "https://on.auto/integrations/x" last_updated: "2026-11-10T08:17:42Z" --- # X Read your posts, mentions and recent search results, and create, edit and delete posts, as yourself. An X connection gives a playbook's functions six operations of the X API, from X's own published document. It acts as you. Unlike every other sign-in Auto offers, it runs under **your organization's own OAuth client**: an app you register in X's developer portal, whose client ID and secret you give in Studio before you sign in. X bills the owner of that client for each call, per post created and per resource read, so the bill and the limits are your organization's, never shared with Auto's or anyone else's. Available on Auto Cloud and on self-hosted runtimes. * * * ## What a playbook can do with X * Read who you are at X. * Read a user's posts and your mentions. * Read the posts of the last seven days that a search matches. * Create a post, edit it, and delete it. It reads no direct messages and follows nobody. A post is text; the operations attach no media. The tools, as the connection lists them Tools that read: `getUsersMe`, `getUsersPosts`, `getUsersMentions` and `searchPostsRecent`. Tools that act: `createPosts` and `deletePosts`. * * * ## An example workflow Mentions, triaged the way your team does. A schedule trigger runs the workflow every two hours. A lookup function reads the mentions since the last run with `getUsersMentions`. A reasoning function sorts each one into a support question, a complaint, praise or noise, following the examples in its prompt, and drafts a reply for the first two kinds in the brand's voice. An interaction function asks the person on duty, through a Slack connection, to approve, change or drop each draft, and waits. Approved replies go out through `createPosts`, one interaction function run each, and the run's history in Studio keeps every mention, its class, the draft and what was posted. Nothing is posted that a person did not see. * * * ## How to connect X * **Sign in to X and allow posting as you, under your organization's own OAuth client.** Before you sign in, give the client ID and client secret of your organization's own OAuth client on the Studio page. The consent screen shows the permissions listed below. Then: 1. Ask your agent to connect X to Auto, or open **Settings**, **Agents**, **Connections** in [Auto Studio](https://studio.on.auto/) and choose X. 2. On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it. Give a key or a client secret there, never in a conversation with your agent. 3. Have your agent check one small read through the connection before a function depends on it. * * * ## What it needs * An X developer account and an app of your own in X's developer portal, of a confidential type (a Web App, or an Automated App or Bot) so that it has a client secret, with Studio's return address among its callback URLs. [X's developer apps page](https://docs.x.com/fundamentals/developer-apps) describes them. * A way to pay X: X charges the app's owner per request, as [its pricing](https://docs.x.com/x-api/getting-started/pricing) sets out. * Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection. ### Permissions Auto asks for * Read every post the X account can see, those of protected accounts among them. * Create, edit, repost and delete posts as the X account that connects. * Read the profiles of every account the X account can see, protected accounts among them. * Keep access to X when nobody is signed in. * * * ## Good to know X's access tokens last two hours, and Auto renews them with the refresh token X issues, so a scheduled workflow keeps working while the connection stands. Removing the connection revokes the tokens at X. Every call a function makes is billed by X to your app, so a workflow that searches often costs what X charges for it; the run's history shows each call. * * * [All integrations](https://on.auto/integrations/) · [LinkedIn](https://on.auto/integrations/linkedin) · [Buffer](https://on.auto/integrations/buffer) · [YouTube](https://on.auto/integrations/youtube) · [Bring in business data](https://on.auto/docs/cloud/connections) · [Give a function tools](https://on.auto/docs/guides/tools) · [Pricing](https://on.auto/pricing) · [X documentation](https://docs.x.com/fundamentals/developer-apps) ## Sitemap See the [full documentation and product sitemap](https://on.auto/sitemap.md) for related pages.