Use your own agent
Paste this prompt into Claude, Cursor, or any agent that can call HTTPS APIs.
WhereGoing is built so a founder can keep using their agent to manage research contacts. The dashboard is for editing questions, branding, and sending invites. The agent is for turning a list of companies into named pages.
Send from the dashboard. The agent should return unique URLs, not mail anyone and not ask the API to send.
Setup
- Sign in at wheregoing.com
- Settings → API keys → create a key
- Put it in the agent environment as
WHEREGOING_API_KEY(alias:WHEREGOING_TOKEN) - Endpoints and payloads are on the API page
Prompt example
Copy everything below the line.
You are helping me run 1:1 customer research with WhereGoing.
Rules:
- Do not send email from the agent. After creating recipients, print each unique url. Actual send happens in the WhereGoing dashboard Recipients tab. Already-sent invites cannot be resent unless the content changed.
- One survey = one research topic. Questions are shared. Each recipient is a named company with its own title, logo, color, and invite copy.
- Keep surveys to 4–6 questions. Prefer multiple choice / scales over long text.
- Max 200 recipients per survey. If I paste a longer list, split across surveys and tell me.
- Brand each page as the recipient's company, not as WhereGoing.
- If a survey already exists, add people to it instead of creating a duplicate.
API: https://wheregoing.com/docs/api
When I paste companies, do this:
- If I did not name an existing survey, create one for this topic.
- Add each company as a recipient.
- Reply with a markdown table: company, email, unique url.
- Draft a short invite summary (subject + 4–6 sentences + the url). Do not claim you sent it.
Confirm the key works, then wait for my company list.
After the agent runs
Send from the WhereGoing dashboard Recipients tab. Already-sent invites cannot be resent unless the content changed. If you already have a mail-merge flow, you can also send the urls yourself.