X (Twitter) DM automation: turn likers, repliers and new followers into conversations

A like on X is the warmest signal a stranger will give you, and it is gone by tomorrow. So is a reply, and so is a new follow. Most founders watch these numbers go up and do nothing with them, because doing something means opening 200 profiles and typing 200 DMs.

This post is about automating that one step, and only that step, from your own X account. It covers what PumpGTM's X automation actually does, the limits it runs inside, and why we left follow bots and like bots out on purpose.

What "X account automation" should mean

There are two kinds of X automation. The first kind manufactures signals: auto-follow a few hundred accounts a day, unfollow the ones that do not follow back, auto-like keywords, drop a reply from a template. It grows a number. It does not grow a pipeline, and it is the pattern X restricts fastest.

The second kind responds to signals people already gave you. Someone liked your post about hiring signals. Someone replied. Someone followed you after reading a thread. Each of those is a person who chose to pay attention for a moment. The job is to start a conversation while the moment is warm.

PumpGTM does the second kind. It reads your posts, likes, replies and followers through X's official API and sends direct messages as you. It does not post, like, reply, follow or unfollow.

The three sources

You write a DM sequence once and attach it to a source.

1. Likers and repliers of one post. Paste the post URL or pick it from your recent posts. Everyone who likes it or replies to it enters the sequence as they show up, over the hours and days the post keeps travelling.
2. Every post you publish from now on. Attach the sequence to your account instead of a post. Each new post is watched automatically. This is the setting most founders end up on, because the follow-through no longer depends on remembering.
3. Every new follower. A follow is a person saying "I want to hear more from you." The sequence greets them within the hour, with a DM in your words.

If you already run the LinkedIn post engagers play, this is the same idea on X, with one difference: X has no connection request step, so the first message goes straight to the DM.

How the sequence works

• Up to five DMs. The first goes out when the person engages. Follow-ups wait one to thirty days each. Three days is the default and, in our own use, the right one.
• Personalization uses what X gives us: first name, full name, handle. No invented company or title fields, because X profiles do not carry them reliably.
• A reply cancels every remaining step for that person. You get a Slack notice and answer in X yourself. PumpGTM never drafts X replies for you.

Here is the shape we run on our own account:

Step	When	Message
1	Day 0	hey , glad you liked the post on hiring signals. what are you working on these days?
2	Day 3	no rush . if it helps, here is the two-line version of how we find buyers before they post a job.
3	Day 8	last one from me. if outbound is not a problem this quarter, ignore this and keep building.

Short, lowercase, one question. It reads like a DM because it is one.

The checks that protect your account and your reputation

• Thread check before the first DM. PumpGTM reads your existing conversation with each person. If you have ever spoken, they are skipped and marked in your activity log. The canned opener never lands inside a real conversation with a friend or a customer.
• Filters. Empty bios and accounts under 20 followers are skipped. Accounts with DMs closed are marked once and left alone.
• Pacing. A few DMs every few minutes with a random gap between them, and never more than 100 DMs a day per workspace. A post that gets 200 likes over two days gets worked over two days, not blasted in a minute. If X's own rate limits push back, PumpGTM waits.
• Official API only. You click Connect X and X itself asks you to allow PumpGTM to read your posts, likes and followers and send DMs as you. No password, no browser cookies, no extension. Revoke it from your X settings whenever you want.

Running it from your AI

PumpGTM is an MCP server. From Claude, Cursor or Codex you can say "DM everyone who likes this post with my intro sequence" and hand it the URL, or point it at your followers. The same thread check, filters and pacing apply. The 32 second version of how that looks on LinkedIn is in running a LinkedIn sales team with Claude.

What we did not build, and why

No auto-follow, no follow back, no auto-like, no auto-reply. Every one of those exists in other tools, and every one of them trades account safety and reputation for a vanity number. Followers you bought with a follow-unfollow loop do not answer DMs. A templated reply under someone's post is noticed by everyone except the person you wanted. The conversation is the only action that turns attention into a customer, so it is the only action we automate. If your GTM needs the manufactured kind of engagement, PumpGTM is the wrong tool and we would rather say so here than after you connect.

Where this sits in the bigger loop

X engagement is one intent signal among several. The same engine that runs your X DMs also finds companies hiring for the problem you solve, scores every lead before outreach, and runs the multi-touch LinkedIn sequence from your own account. The 4-step outbound playbook shows how those pieces fit. X is the channel where your content does the qualifying for you.

Questions founders ask about X DM automation

Can PumpGTM automatically follow back new followers on X? No. It DMs every new follower with your sequence, which is the part of following back that starts a conversation. Automatic follow and unfollow actions are not part of the product.

Will it DM people who already know me? No. Before the first message, PumpGTM reads your existing thread with that person and skips anyone you have ever spoken to.

How many DMs a day does it send? A few every few minutes with random gaps, capped at 100 a day per workspace, inside X's own rate limits.

Is this safe for my X account? It uses X's official API through a one-click authorization you can revoke at any time, sends only DMs, and never scrapes or uses your password. Nothing is guaranteed by X, but this is the pattern X allows.

Can I DM the likers of someone else's post? In the app you pick from your own recent posts. Through the MCP server you can hand it any post URL, with the same pacing and checks.

Does it write replies for me? No. When someone answers, the sequence stops and you are notified in Slack to reply in X yourself.