[{"data":1,"prerenderedAt":39},["ShallowReactive",2],{"$f1tcjfwdg7h9gs":3},{"href":4,"title":5,"description":6,"kind":7,"mark":8,"planned":9,"contributors":10,"provenance":8,"express":9,"html":11,"headings":12},"\u002Fdocs\u002Ftools\u002Fx","X","Posts on X (formerly Twitter) as your own account, through a Zero Human bridge and an X app your company registers.","integrates",null,false,[],"\u003Cp>X is a Zero Human bridge: an MCP server Zero Human hosts in front of X's own API. You connect it on \u003Cstrong>Tools\u003C\u002Fstrong> in the\nportal by signing in with X, through an X developer app your company registers. Each post is made as your account,\nand X bills its API to your own app, never to Zero Human.\u003C\u002Fp>\n\u003Ch2 id=\"what-a-member-can-do\">What a member can do\u003C\u002Fh2>\n\u003Cp>With X connected, a member can see which account it posts as, publish a post or a reply, and delete a post it made.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Tool\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003Cth>Reads or writes\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>account_get\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The account this connection posts as: its id, handle and name\u003C\u002Ftd>\n\u003Ctd>Reads\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>post_create\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Publishes a post as the account, optionally as a reply to another post\u003C\u002Ftd>\n\u003Ctd>Writes: a public post\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>post_delete\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Deletes one post the account made\u003C\u002Ftd>\n\u003Ctd>Writes: removes a post\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>What it writes is public: a post appears on the account as soon as \u003Ccode>post_create\u003C\u002Fcode> returns. X decides how long a post\nmay be for the account, 280 weighted characters for most, and refuses a longer one.\u003C\u002Fp>\n\u003Cp>It reads no timeline, mention, message or analytics, and uploads no image: a link in a post shows the page's own card.\u003C\u002Fp>\n\u003Cp>Name each X tool a task needs, such as \u003Ccode>x.post_create\u003C\u002Fcode>, or \u003Ccode>x\u003C\u002Fcode> for all three. A tool the task does not name is\nrefused, whatever the connection allows. A task that names a social slot's post action, rather than the tool, works\nwith X or with any other tool that fills that slot.\u003C\u002Fp>\n\u003Ch2 id=\"who-connects-it\">Who connects it\u003C\u002Fh2>\n\u003Cp>An X connection acts as \u003Cstrong>the X account that signed in\u003C\u002Fstrong> when it was connected, and posts only as that account. It\nhas no setting: the account is the sign-in's own.\u003C\u002Fp>\n\u003Cp>You connect it by signing in with X, through your company's own X app, with four permissions: \u003Ccode>tweet.read\u003C\u002Fcode>,\n\u003Ccode>tweet.write\u003C\u002Fcode> (to post), \u003Ccode>users.read\u003C\u002Fcode>, and \u003Ccode>offline.access\u003C\u002Fcode>, so the connection renews itself instead of lapsing\nafter two hours.\u003C\u002Fp>\n\u003Cp>A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the\none above. A connection on anything but a task also reaches the \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">chat\u003C\u002Fa> of every member it covers.\nConnect X \u003Cstrong>on the task that posts\u003C\u002Fstrong> unless you want members to post from chat too.\u003C\u002Fp>\n\u003Ch2 id=\"what-waits-for-you\">What waits for you\u003C\u002Fh2>\n\u003Cp>In a run, a post waits for you only when the task gates it, and a Marketing task that posts gates every post. To\napprove each post before it goes out, gate \u003Ccode>post_create\u003C\u002Fcode> (and \u003Ccode>post_delete\u003C\u002Fcode>); see\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>. In a chat, both ask you before they run, unless you chose\n\u003Cstrong>Always allow\u003C\u002Fstrong> for that member and tool. \u003Ccode>account_get\u003C\u002Fcode> only reads, and never waits.\u003C\u002Fp>\n\u003Ch2 id=\"setup\">Setup\u003C\u002Fh2>\n\u003Ch3 id=\"register-an-x-app\">Register an X app\u003C\u002Fh3>\n\u003Cp>X bills its API to the app that made each call, so the app is your company's own, on your own X developer account.\u003C\u002Fp>\n\u003Col>\n\u003Cli>In the \u003Ca href=\"https:\u002F\u002Fconsole.x.com\">X Developer Console\u003C\u002Fa>, create a project and an app, and add API credit.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User authentication settings:\u003C\u002Fstrong> turn on OAuth 2.0, with \u003Cstrong>App permissions:\u003C\u002Fstrong> Read and write, and \u003Cstrong>Type of\napp:\u003C\u002Fstrong> Web App (a confidential client).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Callback URI:\u003C\u002Fstrong> \u003Ccode>https:\u002F\u002Fportal.zerohuman.com\u002Fv1\u002Ftools\u002Foauth\u002Fcallback\u003C\u002Fcode> exactly, with no trailing slash. The\n\u003Cstrong>Add tool\u003C\u002Fstrong> form in the portal shows the right value. \u003Cstrong>Website URL:\u003C\u002Fstrong> your company's site.\u003C\u002Fli>\n\u003Cli>Copy the OAuth 2.0 \u003Cstrong>Client ID\u003C\u002Fstrong> and \u003Cstrong>Client Secret\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3 id=\"connect-it\">Connect it\u003C\u002Fh3>\n\u003Cp>Work in one browser window throughout: X returns to the portal in the window you started from.\u003C\u002Fp>\n\u003Col>\n\u003Cli>In the portal, on \u003Cstrong>Tools\u003C\u002Fstrong>, choose \u003Cstrong>Add tool\u003C\u002Fstrong>. \u003Cstrong>Layer:\u003C\u002Fstrong> Task, and \u003Cstrong>Bind on:\u003C\u002Fstrong> the task that posts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Kind:\u003C\u002Fstrong> MCP. \u003Cstrong>Tool type:\u003C\u002Fstrong> \u003Ccode>x\u003C\u002Fcode>. \u003Cstrong>MCP server URL:\u003C\u002Fstrong> \u003Ccode>https:\u002F\u002Fbridges.zerohuman.com\u002Fx\u002Fmcp\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Auth:\u003C\u002Fstrong> OAuth, with your app's Client ID and Client Secret.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Permissions:\u003C\u002Fstrong> choose \u003Ccode>tweet.read\u003C\u002Fcode>, \u003Ccode>users.read\u003C\u002Fcode> and \u003Ccode>offline.access\u003C\u002Fcode> from the list, and type \u003Ccode>tweet.write\u003C\u002Fcode>\nunder \u003Cstrong>Other\u003C\u002Fstrong>: X's own list of permissions leaves it out, though X grants it.\u003C\u002Fli>\n\u003Cli>Choose \u003Cstrong>Connect with OAuth\u003C\u002Fstrong>, check that the account on X's screen is the one that should post, and choose\n\u003Cstrong>Authorize app\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Check it.\u003C\u002Fstrong> Run a task that calls \u003Ccode>account_get\u003C\u002Fcode>. The run page shows the account's handle.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To disconnect X, delete the connection on \u003Cstrong>Tools\u003C\u002Fstrong>, or revoke the app under \u003Cstrong>Settings → Security and account\naccess → Apps and sessions\u003C\u002Fstrong> on X. \u003Cstrong>Reconnect\u003C\u002Fstrong> keeps the connection and has you sign in again.\u003C\u002Fp>\n\u003Ch2 id=\"limits-and-cost\">Limits and cost\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>X charges for each call, to your app.\u003C\u002Fstrong> X's API has been pay-per-use since early 2026: your app holds credit in\nthe X Developer Console, and each post takes some of it. A post that carries a link costs noticeably more than one\nthat does not. The current prices are on X's own pricing page, and they are X's to change. When the credit runs\nout, every post is refused until more is added.\u003C\u002Fp>\n\u003Cp>The bridge also limits each enterprise to 30 calls a minute, since every call costs money, and X's own rate limits\napply on top. X refuses a post that duplicates one the account just made.\u003C\u002Fp>\n\u003Cp>The bridge has no Zero Human charge of its own. Its calls happen inside runs, and your plan counts those runs as it\ncounts any other.\u003C\u002Fp>\n\u003Ch2 id=\"troubleshooting\">Troubleshooting\u003C\u002Fh2>\n\u003Cp>What a call returns shows on the run page. The quoted words are taken from each message, so you can search this page\nfor the words on your screen.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>What you see\u003C\u002Fth>\n\u003Cth>Why\u003C\u002Fth>\n\u003Cth>What to do\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>The run stops and asks you to sign in again\u003C\u002Ftd>\n\u003Ctd>The sign-in was revoked on X, or it was made without \u003Ccode>offline.access\u003C\u002Fcode> and lapsed\u003C\u002Ftd>\n\u003Ctd>Choose \u003Cstrong>Reconnect\u003C\u002Fstrong> and sign in again, with all four permissions\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The result says X "says the developer app behind this connection has no API credit left"\u003C\u002Ftd>\n\u003Ctd>Your app's credit ran out\u003C\u002Ftd>\n\u003Ctd>Add credit in the X Developer Console; the same post then works\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The result says X "says this sign-in may not do that"\u003C\u002Ftd>\n\u003Ctd>The sign-in lacks \u003Ccode>tweet.write\u003C\u002Fcode>, or the app's permissions are Read only\u003C\u002Ftd>\n\u003Ctd>Set the app to Read and write, then \u003Cstrong>Reconnect\u003C\u002Fstrong> with \u003Ccode>tweet.write\u003C\u002Fcode> typed under \u003Cstrong>Other\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The result says the post "duplicates one the account already made"\u003C\u002Ftd>\n\u003Ctd>X refuses the same text twice in a row\u003C\u002Ftd>\n\u003Ctd>Change the words\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The result says "this enterprise has made its limit of 30 calls"\u003C\u002Ftd>\n\u003Ctd>The bridge's own limit, which protects your credit\u003C\u002Ftd>\n\u003Ctd>Try again in a minute\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The run stops and says no X connection reaches it (\u003Ccode>tool_not_bound:x\u003C\u002Fcode>)\u003C\u002Ftd>\n\u003Ctd>X is not connected anywhere this run reaches\u003C\u002Ftd>\n\u003Ctd>Connect it on the task, or at a layer the run reaches\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>X's screen says something went wrong before you can authorise\u003C\u002Ftd>\n\u003Ctd>The app's \u003Cstrong>Callback URI\u003C\u002Fstrong> does not match, or OAuth 2.0 is off\u003C\u002Ftd>\n\u003Ctd>Set both as \u003Cstrong>Register an X app\u003C\u002Fstrong> shows\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n",[13,17,20,23,26,30,33,36],{"id":14,"text":15,"level":16,"planned":9},"what-a-member-can-do","What a member can do",2,{"id":18,"text":19,"level":16,"planned":9},"who-connects-it","Who connects it",{"id":21,"text":22,"level":16,"planned":9},"what-waits-for-you","What waits for you",{"id":24,"text":25,"level":16,"planned":9},"setup","Setup",{"id":27,"text":28,"level":29,"planned":9},"register-an-x-app","Register an X app",3,{"id":31,"text":32,"level":29,"planned":9},"connect-it","Connect it",{"id":34,"text":35,"level":16,"planned":9},"limits-and-cost","Limits and cost",{"id":37,"text":38,"level":16,"planned":9},"troubleshooting","Troubleshooting",1793444080222]