The Scenario
You run a scraping agency with eight active client projects. Each project needs datacenter proxy endpoints configured for a specific city, with credentials unique to that client. The config table lives in a Google Sheet — one row per project, with the client name in column A, username in column B, password in column C, and target city in column D. The column E endpoint string is what everyone's waiting on.
A new batch of projects came in this week. You've updated the sheet with the new rows. Now you need the endpoint strings generated for all eight, formatted exactly as Smartproxy expects, before your engineers can start deployment.
The bad version:
- You open the Smartproxy dashboard and navigate to the datacenter endpoint section, where you find the hostname and port for the target city listed in row 2
- You manually construct the connection string for row 2 — interpolating the username from column B, the password from column C, and the hostname and port for the city from column D — then paste it into column E
- You repeat this for all eight rows, double-checking each string because a single character transposition in the password or hostname will cause a silent connection failure that doesn't surface until a client's scraping job crashes mid-run
This is configuration assembly work. The engineering value is in what happens after the strings are deployed, not in the fifteen minutes spent constructing them character by character from a dashboard lookup and a spreadsheet.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the table, understands the credential and city columns, and through its built-in Smartproxy integration can generate fully formatted connection strings for every project row and write them directly into column E.
For each row in rows 2–9, generate a Smartproxy custom datacenter endpoint using the username from column B, password from column C, and city from column D — write the full endpoint string in the format 'http://[username]:[password]@[host]:[port]' into column E
What You Get
- Column E fills with a properly formatted Smartproxy datacenter connection string for each project row — username and password embedded, hostname resolved from the city in column D, port matching Smartproxy's datacenter endpoint format
- Rows where the city in column D doesn't map to a recognized Smartproxy datacenter location are flagged in column F so you can review them before handing off to engineering
- Each string is unique to the row's credentials, so client A's endpoint doesn't share authentication with client B's
What If the Data Is Not Quite Ready
The session type varies by row — some clients need rotating, some need sticky, specified in column E
For each row in rows 2–9, generate a Smartproxy datacenter endpoint using the username from column B, password from column C, city from column D, and session type from column E — write the full connection string into column F
Some rows have blank passwords because those clients haven't sent credentials yet
For each row in rows 2–9, check whether column B and column C are both filled in — if yes, generate the Smartproxy datacenter endpoint string for the city in column D and write it into column E — if either credential column is blank, write "credentials pending" into column E instead
The city names in column D are inconsistent — some are full city names, some are Smartproxy location codes, some are abbreviations
Normalize the city values in column D to Smartproxy-recognized datacenter location identifiers, then for each row in rows 2–9 generate the endpoint string using the username from column B, password from column C, and the normalized city, and write the full connection string into column E — flag any city values that couldn't be matched
The team wants a single pass that validates credentials, resolves cities, generates endpoints, and marks rows as deployment-ready
For each row in rows 2–9: normalize the city in column D to a Smartproxy datacenter location, validate that columns B and C are non-empty, generate the endpoint string in the format 'http://[username]:[password]@[host]:[port]', write it into column E, and write "ready" or "blocked: [reason]" into column F based on whether all inputs were valid
Run the full validation and generation in one prompt rather than making three separate passes through the table.
Try It
Get the 7-day free trial of SheetXAI and open any Google Sheet you're using as a client proxy config table, then ask it to generate Smartproxy datacenter endpoint strings for every project row. Link back to the hub: How to Connect Smartproxy to Google Sheets. Or see the related spoke: Bulk Generate Smartproxy Backconnect Endpoints From a Google Sheet.