Social
X (Twitter) + your agents
Publish & reply on X.
Who uses this connection
- Content agent
- OAuth connect
What you paste (3)
X (Twitter)
Publish and reply on X.
Bearer token
X client ID
Your X OAuth2 app's client ID.
Client ID
X client secret
Your X OAuth2 app's client secret.
Client secret
How to get it
X (Twitter)
- 1Go to developer.x.com and sign in (or create an account).
- 2Open the developer / API settings and create a access token.
- 3Copy the access token and paste it here, then Save.
X client ID
- 1Go to developer.x.com and sign in (or create an account).
- 2Open the developer / API settings and create a ID.
- 3Copy the ID and paste it here, then Save.
X client secret
- 1Go to the provider's website and sign in (or create an account).
- 2Open the developer / API settings and create a client secret.
- 3Copy the client secret and paste it here, then Save.
What it can't do on its own
Your key is stored encrypted, per user, and read server-side only — just in time, for one action. It never reaches the browser and never reaches a model.
Anything outward-facing — sending, publishing, paying, changing an order — waits for your approval, and that gate lives on the server. Refusals land in the same append-only audit trail as the things that went through.
Put X (Twitter) to work.
Free 7-day trial with 500 credits. No credit card. Nothing goes out without your approval.