RUN FROM A SPREADSHEET TEMPLATE

Send X messages from a spreadsheet

Use a Google Sheet to send a tailored X message to each account.

RUNS INYour signed-in browser

SETUPOne target or a Google Sheet

WHAT YOU GET03 PARTS

01One message per Sheet row
02Account context used
03Send status for each row

SET UP YOUR RUN

Add the details. Check the result. Run it.

No code needed.

Choose your starting list

Run once for one target, or repeat it for every row in a Google Sheet.

Google Sheet

Choose the Sheet with one target per row.

EXPECTED COLUMNSprofile_url, name (optional), message_text (optional), context (optional)

No sheet selected. Choose one from Google Drive.

Sign in to choose a Sheet

Your run stays disabled until the Sheet is connected.

Tell rtrvr what to use

Required details are marked. The example text shows the expected format.

Message goal (if not in sheet)

Message direction

Used when the message_text cell is empty. rtrvr drafts from the row and profile.

Choose where it runs

Cloud uses a fresh managed browser. The extension uses the sites you are already signed into.

Your browser is required. This template needs a site where you are signed in.

Choose a connected browser

Open the rtrvr extension and sign in with the same account, then choose your browser here.

Get the extension

Sign in to connect

Install the Chrome extension.
Sign in on this page and in the extension with the same account.
Choose the connected browser before starting the task.

Start this task in Free Mode in Cloud or your connected Chrome. Cookie sync, schedules, and triggers require a subscription. Compare plans →

Free usage, ads, and data terms

Free Mode includes supported AI models and Cloud browser time for tasks you start in the extension or Cloud dashboard. No AI API key or paid AI subscription is required. Sponsored cards and a daily fair-use allowance apply. Your account shows the current allowance and reset time. When you reach it, wait for the reset, use your own AI provider, or choose a paid plan. Your provider may charge for its usage.

One schedule that runs once a day or less often, in the Cloud or in your Chrome, is included, paid from the daily allowance. More schedules, faster schedules, triggers, cookie sync, API runs, rtrvr's agent over MCP, and WhatsApp tasks require a paid plan. Browser tools that let your own AI drive your Chrome over MCP are free on every plan. Data enrichment and managed proxies can use credits separately.

On the free plan, Cloud API calls made with an API key, the MCP Cloud tools (cloud_agent, cloud_scrape, and agent or scrape when they run in Cloud), and WhatsApp tasks need a paid plan, as does running rtrvr's agent in your Chrome through API or MCP. Free Mode covers the tasks you start in the extension or Cloud dashboard. On a paid plan, API, MCP, and WhatsApp runs use credits for the resources they consume.

Free Mode involves sponsored content in both the Chrome extension and Cloud, as described in the Terms and Privacy Notice.

Using your own AI provider avoids model-credit charges and the Free Mode allowance. Cloud resources and managed services may still use credits. Sponsored cards still appear on the free plan. Paid plans offer ad-free runs.

ONE MORE STEP

Add the required details to continue.

WHAT HAPPENS NEXT

From setup to finished result.

01
rtrvr opens the right sites. It uses Cloud or the signed-in browser you chose.
02
The browser does the job. You can follow the run and step in if a site asks for help.
03
You get the result. The output above is the shape to expect.

ADVANCEDRequest JSONOptional

Exact request sent to the run panel.

REQUEST.JSON

{
  "source": "retrieve",
  "template": {
    "id": "bulk_x_dm",
    "slug": "bulk-x-dm",
    "name": "Bulk X/Twitter DM Sender",
    "categoryId": "SOCIAL_SCALE"
  },
  "inputs": {
    "sheetUrl": "",
    "messageGoal": "networking",
    "messageTemplate": "",
    "__inputSource": "sheet"
  },
  "agentHint": "You are sending bulk X/Twitter DMs. Adapt completely to the actual UI you encounter.\n\n**TASK CONFIGURATION:**\n- Sheet URL: \n- Message Goal: networking\n- Message Template: \n\n---\n\n## STEP 1: LOAD SHEET DATA\n\n1. Navigate to \n2. Read all rows\n3. **Expected columns:**\n   - profile_url (REQUIRED)\n   - name (optional)\n   - message_text (optional - overrides generation)\n   - context (optional)\n4. Count valid rows for progress tracking\n\n---\n\n## STEP 2: PROCESS EACH ROW\n\nFor each valid row:\n\n### A. NAVIGATE TO PROFILE\n1. Go to the X profile_url from this row\n2. Wait for profile to fully load\n3. **Check profile status:**\n   - Profile exists? If not, log and continue\n   - Protected account? Note for DM access\n   - Account suspended? Log and continue\n\n### B. CHECK DM AVAILABILITY - CRITICAL\n**X DMs are often closed. Check carefully:**\n1. Look for message/DM icon or option on profile\n2. **Possible states:**\n   - DMs open: Message button/icon visible and clickable\n   - DMs closed: No message option (very common)\n   - Following required: May need to follow first\n   - Protected: Requires follow approval first\n3. **If DMs not available:**\n   - Log \"DMs closed\" with username\n   - Continue to next profile immediately\n   - This is EXPECTED for many accounts\n\n### C. ANALYZE THEIR PROFILE (if DMs open)\n**Gather context:**\n- Display name and handle\n- Bio content\n- Recent tweets (themes, topics, tone)\n- Pinned tweet\n- Follower count\n\n### D. PREPARE MESSAGE\n\n**IF message_text column has content:**\nUse it exactly.\n\n**VALIDATION:**\n- X DMs have 10,000 char limit but shorter is better\n- Optimal: 2-4 sentences, under 500 chars\n- If over reasonable length: Consider truncating or warn\n\n**ELSE generate message:**\n- Goal: networking\n- Template: \"\"\n- Row context: [if provided]\n- Profile personalization required\n\n**X DM culture:**\n- Be DIRECT - X users value brevity\n- Reference their tweets/work specifically\n- One clear purpose per message\n- Don't be formal/corporate\n- Get to the point in first sentence\n\n### E. SEND MESSAGE\n1. Access DM composer\n2. Enter message\n3. Send\n4. Verify message appears in conversation\n5. Log result\n\n### F. RATE LIMITING\n- Wait 30-60 seconds between DMs\n- X has rate limits on DM sends\n- **If rate limited:** Pause, report progress, wait or stop\n\n---\n\n## STEP 3: GENERATE COMPLETION REPORT\n\n```json\n{\n  \"totalRows\": <number>,\n  \"processed\": <number>,\n  \"sent\": <number>,\n  \"dmsClosed\": <number>,\n  \"protectedAccounts\": <number>,\n  \"failed\": <number>,\n  \"results\": [\n    {\n      \"rowIndex\": <number>,\n      \"profileUrl\": \"\",\n      \"username\": \"\",\n      \"dmsOpen\": true|false,\n      \"isProtected\": false,\n      \"messageSource\": \"sheet|generated\",\n      \"messagePreview\": \"\",\n      \"characterCount\": <number>,\n      \"status\": \"sent|dms_closed|protected|not_found|failed\",\n      \"error\": \"\"\n    }\n  ]\n}\n```\n\n---\n\n## IMPORTANT: EXPECT HIGH SKIP RATE\n\n**Many X accounts have DMs closed.**\n- This is normal, not an error\n- Skip rate of 50%+ is common\n- Track dmsClosed count for user\n- Don't treat closed DMs as failures",
  "userInput": "You are sending bulk X/Twitter DMs. Adapt completely to the actual UI you encounter.\n\n**TASK CONFIGURATION:**\n- Sheet URL: \n- Message Goal: networking\n- Message Template: \n\n---\n\n## STEP 1: LOAD SHEET DATA\n\n1. Navigate to \n2. Read all rows\n3. **Expected columns:**\n   - profile_url (REQUIRED)\n   - name (optional)\n   - message_text (optional - overrides generation)\n   - context (optional)\n4. Count valid rows for progress tracking\n\n---\n\n## STEP 2: PROCESS EACH ROW\n\nFor each valid row:\n\n### A. NAVIGATE TO PROFILE\n1. Go to the X profile_url from this row\n2. Wait for profile to fully load\n3. **Check profile status:**\n   - Profile exists? If not, log and continue\n   - Protected account? Note for DM access\n   - Account suspended? Log and continue\n\n### B. CHECK DM AVAILABILITY - CRITICAL\n**X DMs are often closed. Check carefully:**\n1. Look for message/DM icon or option on profile\n2. **Possible states:**\n   - DMs open: Message button/icon visible and clickable\n   - DMs closed: No message option (very common)\n   - Following required: May need to follow first\n   - Protected: Requires follow approval first\n3. **If DMs not available:**\n   - Log \"DMs closed\" with username\n   - Continue to next profile immediately\n   - This is EXPECTED for many accounts\n\n### C. ANALYZE THEIR PROFILE (if DMs open)\n**Gather context:**\n- Display name and handle\n- Bio content\n- Recent tweets (themes, topics, tone)\n- Pinned tweet\n- Follower count\n\n### D. PREPARE MESSAGE\n\n**IF message_text column has content:**\nUse it exactly.\n\n**VALIDATION:**\n- X DMs have 10,000 char limit but shorter is better\n- Optimal: 2-4 sentences, under 500 chars\n- If over reasonable length: Consider truncating or warn\n\n**ELSE generate message:**\n- Goal: networking\n- Template: \"\"\n- Row context: [if provided]\n- Profile personalization required\n\n**X DM culture:**\n- Be DIRECT - X users value brevity\n- Reference their tweets/work specifically\n- One clear purpose per message\n- Don't be formal/corporate\n- Get to the point in first sentence\n\n### E. SEND MESSAGE\n1. Access DM composer\n2. Enter message\n3. Send\n4. Verify message appears in conversation\n5. Log result\n\n### F. RATE LIMITING\n- Wait 30-60 seconds between DMs\n- X has rate limits on DM sends\n- **If rate limited:** Pause, report progress, wait or stop\n\n---\n\n## STEP 3: GENERATE COMPLETION REPORT\n\n```json\n{\n  \"totalRows\": <number>,\n  \"processed\": <number>,\n  \"sent\": <number>,\n  \"dmsClosed\": <number>,\n  \"protectedAccounts\": <number>,\n  \"failed\": <number>,\n  \"results\": [\n    {\n      \"rowIndex\": <number>,\n      \"profileUrl\": \"\",\n      \"username\": \"\",\n      \"dmsOpen\": true|false,\n      \"isProtected\": false,\n      \"messageSource\": \"sheet|generated\",\n      \"messagePreview\": \"\",\n      \"characterCount\": <number>,\n      \"status\": \"sent|dms_closed|protected|not_found|failed\",\n      \"error\": \"\"\n    }\n  ]\n}\n```\n\n---\n\n## IMPORTANT: EXPECT HIGH SKIP RATE\n\n**Many X accounts have DMs closed.**\n- This is normal, not an error\n- Skip rate of 50%+ is common\n- Track dmsClosed count for user\n- Don't treat closed DMs as failures",
  "urls": [],
  "meta": {
    "createdAt": "",
    "userAgent": ""
  },
  "execution": {
    "mode": "device",
    "deviceIds": []
  }
}

MORE STARTING POINTS

Other templates for run from a spreadsheet.

See all templates

RUN FROM A SPREADSHEETSend LinkedIn messages from a spreadsheet

Use a Google Sheet to send a tailored LinkedIn message to each profile.

RUN FROM A SPREADSHEETSend Instagram messages from a spreadsheet

Use a Google Sheet to send a tailored Instagram message to each account.

RUN FROM A SPREADSHEETSend LinkedIn requests from a spreadsheet

Use a Google Sheet to send a LinkedIn request and note to each profile.