src ▸ task opened 0

Automate X (Twitter)

Turn the repetitive X (Twitter) work you do by hand (search a query, open a profile) into a workflow Writ runs for you, on your own account, on a schedule or on demand.

Automate X (Twitter) See how it works
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
X (Twitter) workflow
  1. 1
    search a query
  2. 2
    open a profile
  3. 3
    read posts and metrics
  4. 4
    export results

✓ Recorded once, then run for you

gap ▸ done by hand 01
01
why

Stop doing X (Twitter) by hand

The X (Twitter) tasks you repeat (search a query, open a profile, read posts and metrics) are exactly the kind of work a computer should do. But X (Twitter) only exposes part of it through an API, and the flow runs behind a login and dynamic pages. X's API tiers are paid and rate-limited; many read and monitoring workflows are simpler and cheaper in an authenticated browser.

Writ closes that gap. Record the X (Twitter) task once (or describe it to an AI session) and Writ runs it for you in a real browser, on your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

ops ▸ actions mapped 02
02
automate

X (Twitter) tasks Writ can run for you

Each of these is a real X (Twitter) action, captured into a workflow and run on your own account.

{ }search a query
{ }open a profile
{ }read posts and metrics
{ }export results

Workflows extract structured fields such as post text, likes, reposts, follower count along the way: typed data you can route anywhere.

build ▸ three routes 03
03
build

Three ways to build your X (Twitter) automation

Pick whichever fits the task. All three produce the same workflow Writ can run for you.

✦Record itDo the X (Twitter) task once in a real browser (search a query, then open a profile) and the recorder captures every step into a reusable workflow.
✦Describe it to AITell an AI session your goal on X (Twitter) in plain language; it drives the live page and builds the workflow for you, no recording needed.
✦Discover itLet API discovery watch X (Twitter)'s own network calls as you browse, then turn the underlying requests into a fast, headless workflow.

Built on the same engine as the recorder and workflows, with 30+ step types.

auth ▸ logged-in web 04
04
the hard web

Login, 2FA, and dynamic pages on X (Twitter)

The reason X (Twitter) is tedious to automate is the same reason most tools can't. Writ handles it.

Writ signs into your own X account through a Persona with 2FA and operates inside that authenticated session.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering
when ▸ it runs 05
05
when it runs

Run the X (Twitter) automation on your terms

On a schedule, on demand, or the instant something changes. You choose the trigger.

✦On a scheduleRun the X (Twitter) task every hour, every morning, or any cadence. No one has to remember to do it.
✦On demandTrigger a single run from the dashboard, a webhook, your code, or an AI agent, whenever you need it.
✦On a changeWatch X (Twitter) for new post from an account or follower-count change and fire the automation the instant it happens.
  1. 1
    Build the X (Twitter) workflow once

    Record the task, describe it to AI, or discover it from the network. Writ captures each step, including login and 2FA, into a workflow you can edit.

  2. 2
    Run it on your terms

    Run it on demand, on a schedule, or fire it from a Monitor when X (Twitter) changes. It runs on your own X (Twitter) account, in a real browser.

  3. 3
    Call it from anything

    The same workflow is a REST endpoint at /v1/x/run and an MCP tool, so your code, a no-code tool, or an AI agent can trigger the X (Twitter) automation too.

watch ▸ changes tracked 06
06
watch

Trigger the X (Twitter) automation on a change

Monitor X (Twitter) for new post from an account, follower-count change, engagement threshold and run your workflow the moment it happens.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes a trigger that runs your X (Twitter) automation in seconds. Monitor X (Twitter) ▸

venue ▸ local or cloud 07
07
run it

Free on your own machine, or on cloud

Local / BYO agent

No compute charge. The agent runs on your hardware, so it can reach X (Twitter) even from an intranet or VPN-only network, and your AI keys never leave your machine.

Writ cloud

Metered by running time at $0.12 per browser-hour, drawn from your plan’s included usage. No infrastructure to manage.

call ▸ endpoint too 08
08
callable

The same X (Twitter) automation is an API and an MCP tool

Automating X (Twitter) for yourself and calling it from software are the same workflow. Once you have it, publish it as a REST endpoint at/v1/x/run and a matching MCP tool, so your code or an AI agent can trigger the X (Twitter) task too.

X (Twitter) API X (Twitter) MCP tools
also ▸ same workflow 09
09
other ways

Other ways to work with X (Twitter)

X (Twitter) APICall X (Twitter) as a REST endpoint from your own software.Website to API X (Twitter) MCP toolsExpose X (Twitter) as MCP tools your agent can call.For AI agents Monitor X (Twitter)Watch X (Twitter) and act the instant it changes.Change detection WorkflowsHow recorded workflows run, with login, 2FA, and 30+ step types.Product
faq ▸ questions answered 10
10
faq

Automating X (Twitter): questions

How do I automate X (Twitter)?
Record the X (Twitter) task once in the recorder (search a query, open a profile, read posts and metrics) or describe your goal to an AI session. Writ turns it into a workflow it can run for you on a schedule or on demand, on your own X (Twitter) account. It usually takes minutes, not a backend project.
Is it allowed to automate X (Twitter) this way?
Use Writ on your own X account and on public content you have the right to access. Respect its Terms of Service. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Does X (Twitter) automation work behind login and 2FA?
Writ signs into your own X account through a Persona with 2FA and operates inside that authenticated session. Writ handles TOTP and mailbox-OTP two-factor through Personas, so the automation runs inside your own authenticated X (Twitter) session.
Can I run the X (Twitter) automation without writing code?
Yes. Recording and AI sessions need no code at all. If you do want to trigger it from software, the same workflow is a REST endpoint and an MCP tool, but that is optional.
Where does it run, and what does it cost?
Run it on your own machine with a local or BYO agent for no compute charge, useful when X (Twitter) is only reachable from your network or VPN. Or run it on metered cloud at $0.12 per browser-hour, drawn from your plan’s included usage. Start free.
rec ▸ ready ●

Automate X (Twitter) in minutes

Record it once, then let Writ run it for you: on a schedule, on demand, or on a change. Get started free.

Get started