Twitter Inbox Scraper
This automation exports the direct message conversations from your own X (Twitter) inbox. Each row contains the conversation URL, the type, the sender and recipient IDs, and the last message date.
Platform: X (Twitter) | Category: Search & Collect
Inputs#
This automation has no inputs. It reads the inbox of the connected account.
Outputs#
| Output | Type | Description |
|---|---|---|
| Conversation URL | Text | Twitter conversation URL |
| Conversation ID | Text | Twitter conversation ID |
| Conversation Type | Text | Twitter conversation type (one-to-one or group DM) |
| Sender ID | Text | Twitter sender profile ID |
| Recipient ID | Text | Twitter recipient profile ID |
| Last Message Date | Date | Last message sent date |
Why this automation is useful#
A busy inbox hides leads. Threads go cold without a record. This automation gives you a full list of your DM conversations in one CSV file.
The Last Message Date column supports follow-up discipline. Sort by that column to find threads that went silent. The Conversation URL column takes you back to each thread.
The Conversation Type column separates one-to-one threads from group DMs. This helps when you manage community conversations alongside sales threads.
Use cases#
- Recover cold DM leads. A freelancer exports the inbox every Friday. Sorting by Last Message Date surfaces threads silent for more than a week. Each stale thread gets a follow-up message the same day.
- Log DM conversations into a CRM. A sales rep exports the inbox every week. The CSV is imported into the CRM as conversation records. No prospect thread is lost between the platform and the pipeline.
- Archive client account inboxes. An agency that manages client accounts exports each inbox every week. The CSVs form a dated archive of conversation metadata. Client reports reference real thread counts and dates.
- Audit response discipline across a team. A business owner exports the company inbox every month. Comparing Last Message Date across threads shows which conversations aged without attention. The owner sets a response-time rule from real numbers.
- Separate group DMs from sales threads. A community manager filters the export by Conversation Type. Group DMs go to the community workflow. One-to-one threads go to the sales follow-up list.
How to use it#
- Connect your X (Twitter) account with the TexAu browser extension.
- Open Twitter Inbox Scraper in the TexAu Desktop app.
- Run the automation.
- Open the CSV in your export folder when the run ends.
The automation uses your active session. Do not use the account heavily in the browser during the run.
Limits and limitations#
- TexAu sets a default limit of 28800 executions per day and 3600 executions per hour for this automation.
- The export covers the inbox of the connected account only. It cannot read the inbox of another account.
- The export contains conversation metadata. It does not export the message text.
- X (Twitter) can change its layout or rate limits at any time. Results can vary between runs.
FAQ#
Q: How many times can I run this per day? A: TexAu sets a default limit of 28800 executions per day and 3600 executions per hour.
Q: Can X (Twitter) restrict my account? A: Yes, if you exceed the platform rate limits. TexAu adds random delays between actions. Keep to the default limits to reduce risk.
Q: Do I need a proxy? A: A proxy is not required for one account. Use one proxy per account when you run many accounts.
Q: What account do I need? A: A free X (Twitter) account is enough. No paid subscription is required.
Q: Does the automation dedupe results? A: This automation has no input. Repeated runs return the current inbox state. Clean your CSVs when you merge exports.
Q: Where do the results go? A: Results save as a CSV in your export folder. You can also find past runs in the History section of the app.
Q: Does it export the message text? A: No. It exports the conversation URL, the IDs, the type, and the last message date. Open the Conversation URL to read the messages.
Q: Can it read someone else's inbox? A: No. It reads only the inbox of the account connected through the browser extension.
Troubleshooting#
The automation asks me to connect the account again. The platform session expired. Reconnect the account with the TexAu browser extension. See Connect accounts with the TexAu browser extension.
The run fails with an invalid URL error. Copy the URL exactly as the Inputs table shows. The automation checks the URL format before it runs.
The CSV has fewer results than expected. The platform shows less data to your account than the total count suggests. Private or restricted profiles do not appear. This is normal platform behavior.
The automation stops before the run completes. You reached a rate limit window. Wait for the window to reset, then run the automation again. See Manage rate limits.
The same run fails several times. Note the exact error message from the app. Contact TexAu support and include this message and the automation name.
Related guides#
- All X (Twitter) automations
- Twitter Impressions Export
- Twitter Quote Retweets Export
- Twitter Profile Followed Topics Export
Platform: X (Twitter) | Category: Search & Collect