Twitter Direct Messages Export
Twitter Direct Messages Export extracts the messages from one direct message conversation on X (Twitter). The export includes message content, message dates, sender IDs, and the profile data of the other participant.
Platform: X (Twitter) | Category: Search & Collect
Inputs#
| Input | Type | Required | Description |
|---|---|---|---|
| Enter Twitter Profile or Conversation URL Here | Text | Yes | Profile URL or conversation URL of the thread to extract. Sample values: https://x.com/username or https://x.com/i/chat/4046975893-2057058647918981120 |
Outputs#
| Output | Type | Description |
|---|---|---|
| Input Profile URL | Text | The profile or conversation URL you entered |
| Conversation ID | Text | Twitter conversation ID |
| Conversation Type | Text | Conversation type: one-to-one or group DM |
| Message ID | Text | Twitter message ID |
| Message Date | Date | Date the message was sent |
| Message | Text | Text content of the message |
| Recipient ID | Text | Twitter profile ID of the recipient |
| Sender ID | Text | Twitter profile ID of the sender |
| Name | Text | Profile name of the other participant |
| Handle | Text | Profile handle |
| Bio | Text | Profile bio |
| Profile Thumbnail | Text | Twitter profile thumbnail URL |
| Profile Banner | Text | Twitter profile banner URL |
| Text | Email found in bio | |
| Website URLs | Text | Website URLs, comma-separated |
| Links in Bio | List | Links in bio, comma-separated |
| Location Search | Text | Profile location |
| Account Date | Date | Twitter account creation date |
| Follow Sent | Yes or no | Follow request sent (YES/NO) |
| Follower | Yes or no | Follows you (YES/NO) |
| Following | Yes or no | Profile you follow (YES/NO) |
| Followers Count | Number | Profile followers count |
| Following Count | Number | Twitter profile following count |
| Tweets Count | Number | Twitter profile tweets count |
| Blue Badge | Yes or no | Verified account (YES/NO) |
| Listed Count | Number | Number of lists the profile is on |
Why this automation is useful#
Direct message threads hold sales conversations, client instructions, and support history. Copying them by hand is slow. This automation exports one conversation per run and saves it as a CSV file.
Each row carries the message text, the send date, and the conversation ID. Profile fields describe the other participant. Follow state fields show whether the relationship is one-way or two-way.
The data supports CRM logging, client records, and lead research. Agencies can attach exports to client reports. Sales teams can move conversation context into their pipeline notes.
Use cases#
- Log sales DMs into the CRM. Export each prospect conversation after a deal closes or stalls. Attach the CSV to the deal record. Your team keeps full context when the account changes hands.
- Build a warm-lead list from DM conversations. Export threads with people who replied to your outreach. Filter the export by follower count and follow state. Move the best leads into your cold email tool for the next touch.
- Archive client scope discussions. Freelancers can export project-scope DMs before work starts. Keep the CSV with the contract. The record settles disputes about what the client approved.
- Hand support threads to a ticket system. Export complaint conversations that arrive by DM. Attach the CSV to the support ticket. The next agent reads the full history without account access.
- Mine objections from trial-user chats. Founders can export DM threads with trial users. Tag each objection in the CSV. Feed the answers into the sales page and the pitch deck.
How to use it#
- Connect your X (Twitter) account with the TexAu browser extension.
- Open Twitter Direct Messages Export in the TexAu Desktop app.
- Enter the profile URL or the conversation URL. Use the format
https://x.com/usernameorhttps://x.com/i/chat/4046975893-2057058647918981120. - 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 14400 executions per day and 1800 executions per hour for this automation.
- An active X (Twitter) session is required.
- The automation reads only the conversations of your connected account.
- X (Twitter) can change what direct message data is available at any time.
FAQ#
Q: How many conversations can I export per day? A: TexAu sets a default limit of 14400 executions per day and 1800 executions per hour. Each run extracts one conversation.
Q: Can X (Twitter) restrict my account for exporting direct messages? A: Yes, if you exceed 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. The account must have access to the conversation you want to export.
Q: Does the automation dedupe results? A: TexAu dedupes repeated runs of the same input. Keep your CSVs clean by not re-running the same input.
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: Can I export a group DM? A: Yes. The export includes a conversation type field. The field marks the thread as one-to-one or group DM.
Q: Can I read the private messages of another account? A: No. The automation reads only the conversations visible to your connected account.
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