Exact request sent to the run panel.
{
"source": "retrieve",
"template": {
"id": "x_dm_sender",
"slug": "x-dm",
"name": "X/Twitter DM Sender",
"categoryId": "SOCIAL_OUTREACH"
},
"inputs": {
"profileUrl": "",
"messageText": "",
"messageGoal": "networking",
"context": "",
"autoSend": true
},
"agentHint": "You are sending an X/Twitter direct message. Adapt to the actual UI you encounter.\n\n**TASK CONFIGURATION:**\n- Profile URL: \n- User's Message: \n- Message Goal: networking\n- Context: \n- Auto-send: true\n\n---\n\n## STEP 1: NAVIGATE TO PROFILE\n\n1. Go to \n2. Wait for profile to load\n3. If not logged in, STOP and report authentication required\n\n---\n\n## STEP 2: CHECK DM AVAILABILITY\n\n1. Look for message/DM icon on their profile\n2. **DM Status possibilities:**\n - DMs open: Can message directly\n - DMs closed: Cannot message (common on X)\n - Following required: Must follow to DM\n3. If DMs not available, STOP and report status\n\n---\n\n## STEP 3: ANALYZE THEIR PROFILE\n\n**For personalization:**\n- Bio and what they're known for\n- Recent tweets (themes, opinions)\n- Pinned tweet\n- Their communication style\n- What they engage with\n\n---\n\n## STEP 4: PREPARE MESSAGE\n\n### IF user provided messageText:\nUse this message exactly:\n```\n\n```\n\n**VALIDATION:**\n- X DMs have a 10,000 character limit\n- But brevity is X culture - keep it short\n- Optimal: 2-4 sentences\n\n### IF messageText is empty - GENERATE MESSAGE:\n\n**Generate a networking message that:**\n\n1. **References their tweets/work:**\n - A recent tweet or thread\n - Their known expertise\n - Something specific they said\n\n2. **Gets to the point quickly:**\n - X culture values directness\n - Don't waste their time\n - One clear ask\n\n3. **Matches their energy:**\n - Read their tweets for tone\n - Mirror their formality level\n\n4. **Format:**\n - 2-4 sentences ideal\n - Direct and clear\n - One question/ask max\n - No emojis unless they use them\n\n**GOOD:**\n\"Your thread on [topic] was great. Quick question: [specific question]. [Brief context about why you're asking]\"\n\n**BAD:**\nLong intros, generic praise, immediate sales pitch, multiple asks\n\n---\n\n## STEP 5: SEND OR PREVIEW\n\n1. Click message/DM button\n2. Wait for DM composer to open\n3. Type or paste message\n\n### IF true === true:\n4. Click send\n5. Wait for message to appear\n6. Verify delivery\n\n### IF true === false:\n4. Leave ready for review\n5. Report status\n\n---\n\n## STEP 6: REPORT RESULTS\n\n```json\n{\n \"success\": true|false,\n \"recipientUsername\": \"\",\n \"dmStatus\": \"open|closed|following_required\",\n \"messageText\": \"<the message used>\",\n \"messageSource\": \"provided|generated\",\n \"characterCount\": <number>,\n \"tweetReferenced\": \"<if any>\",\n \"status\": \"sent|dms_closed|ready_for_review|failed\",\n \"errorMessage\": \"<if failed>\"\n}\n```\n\n---\n\n## X DM REALITY CHECK\n\n- Many accounts have DMs closed\n- Expect high rate of \"can't message\" outcomes\n- Following someone may open DM access\n- Verified accounts more likely to have open DMs\n- Response rates vary wildly",
"userInput": "You are sending an X/Twitter direct message. Adapt to the actual UI you encounter.\n\n**TASK CONFIGURATION:**\n- Profile URL: \n- User's Message: \n- Message Goal: networking\n- Context: \n- Auto-send: true\n\n---\n\n## STEP 1: NAVIGATE TO PROFILE\n\n1. Go to \n2. Wait for profile to load\n3. If not logged in, STOP and report authentication required\n\n---\n\n## STEP 2: CHECK DM AVAILABILITY\n\n1. Look for message/DM icon on their profile\n2. **DM Status possibilities:**\n - DMs open: Can message directly\n - DMs closed: Cannot message (common on X)\n - Following required: Must follow to DM\n3. If DMs not available, STOP and report status\n\n---\n\n## STEP 3: ANALYZE THEIR PROFILE\n\n**For personalization:**\n- Bio and what they're known for\n- Recent tweets (themes, opinions)\n- Pinned tweet\n- Their communication style\n- What they engage with\n\n---\n\n## STEP 4: PREPARE MESSAGE\n\n### IF user provided messageText:\nUse this message exactly:\n```\n\n```\n\n**VALIDATION:**\n- X DMs have a 10,000 character limit\n- But brevity is X culture - keep it short\n- Optimal: 2-4 sentences\n\n### IF messageText is empty - GENERATE MESSAGE:\n\n**Generate a networking message that:**\n\n1. **References their tweets/work:**\n - A recent tweet or thread\n - Their known expertise\n - Something specific they said\n\n2. **Gets to the point quickly:**\n - X culture values directness\n - Don't waste their time\n - One clear ask\n\n3. **Matches their energy:**\n - Read their tweets for tone\n - Mirror their formality level\n\n4. **Format:**\n - 2-4 sentences ideal\n - Direct and clear\n - One question/ask max\n - No emojis unless they use them\n\n**GOOD:**\n\"Your thread on [topic] was great. Quick question: [specific question]. [Brief context about why you're asking]\"\n\n**BAD:**\nLong intros, generic praise, immediate sales pitch, multiple asks\n\n---\n\n## STEP 5: SEND OR PREVIEW\n\n1. Click message/DM button\n2. Wait for DM composer to open\n3. Type or paste message\n\n### IF true === true:\n4. Click send\n5. Wait for message to appear\n6. Verify delivery\n\n### IF true === false:\n4. Leave ready for review\n5. Report status\n\n---\n\n## STEP 6: REPORT RESULTS\n\n```json\n{\n \"success\": true|false,\n \"recipientUsername\": \"\",\n \"dmStatus\": \"open|closed|following_required\",\n \"messageText\": \"<the message used>\",\n \"messageSource\": \"provided|generated\",\n \"characterCount\": <number>,\n \"tweetReferenced\": \"<if any>\",\n \"status\": \"sent|dms_closed|ready_for_review|failed\",\n \"errorMessage\": \"<if failed>\"\n}\n```\n\n---\n\n## X DM REALITY CHECK\n\n- Many accounts have DMs closed\n- Expect high rate of \"can't message\" outcomes\n- Following someone may open DM access\n- Verified accounts more likely to have open DMs\n- Response rates vary wildly",
"urls": [],
"meta": {
"createdAt": "",
"userAgent": ""
},
"execution": {
"mode": "device",
"deviceIds": []
}
}
Add to Chrome