> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up your Grok Bot link builder

> Connect Grok Bot to AgentLinkOps, save a Link Builder or Link Monitor role, and verify your first workspace read.

Give your **Link Builder** bot the job of finding relevant link opportunities, preparing outreach and tracking earned links. Use one bot for a website or a selected portfolio.

You need [Grok Bot](https://x.ai/bot) and an authorized AgentLinkOps workspace. Hosted AgentLinkOps access currently requires a pilot invitation.

For other agents, [choose a setup guide](https://docs.agentlinkops.com/guides/ai-agents.md). The same [two starter roles](https://docs.agentlinkops.com/guides/agent-roles.md) work across the guides.

## 1. Give your bot a job

Create a **Link Builder** or **Link Monitor** bot, then copy its [starter prompt](https://docs.agentlinkops.com/guides/agent-roles.md). Both roles support one website or a selected portfolio. Save separate briefs for each site.

Bot names do not isolate client data: personal bots share a computer and connected accounts. Review [Grok's shared computer model](https://docs.x.ai/grok-bot/computer-and-apps) before adding client access.

## 2. Connect AgentLinkOps

Open **Connect apps → Add a custom connector**. Choose **Remote HTTPS**, name it **AgentLinkOps**, and enter:

```text theme={null}
https://app.agentlinkops.com/mcp
```

Leave custom headers and client ID empty. Choose **Add plugin**, then **Connect**. Complete browser sign-in and review access for the intended workspace and sites. Keep passwords and codes in the sign-in window. Follow any returned AgentLinkOps approval link.

Have Grok confirm the connection with `get_workspace` and `list_projects`. The result should name your workspace and selected sites. If you have no project yet, [add your website](https://docs.agentlinkops.com/guides/get-started-app.md).

## 3. Get your first report

For **Link Builder**, show existing campaigns and saved links, then recommend one campaign draft. Use the [campaign quickstart](https://docs.agentlinkops.com/quickstart.md#2-give-it-a-campaign-mission) for a site with no campaign yet.

For **Link Monitor**, start with a saved-link report. Include source and destination URLs, recorded state, observation date and active or paused status. Include every result page and flag inaccessible sites. An unknown observation does not prove a lost link. A missing link never observed live is not a confirmed loss.

Reading saved observations does not refresh them. New checks and monitoring can consume allowance; `monitor_link` starts metered, recurring work. Use workspace and project reads to test the connection.

## 4. Put the bot to work

For **Link Builder**, connect your preferred sequencer or mailbox for outreach. AgentLinkOps stores records and observations; your bot manages sending through that separate connection. Confirm its tools can draft, send, read replies and enforce suppression before handing over approved campaigns. See [outreach and sender handoff](https://docs.agentlinkops.com/guides/crm-sender-handoff.md).

Begin with an ad hoc campaign draft. Once the workflow works, save it as a [Grok skill](https://docs.x.ai/grok-bot/skills-routines-and-automations). Agree a schedule before creating a routine. If replacing existing automation, switch ownership without overlapping senders.

For **Link Monitor**, agree a reporting cadence after reviewing the first report.

Local scripts need the intended computer online and reachable. A cloud routine does not make local files or mail credentials available automatically.

> [accordion] Fix approval or missing-permission errors
>
> For `AGENT_APPROVAL_REQUIRED`, approve the current client, then refresh its existing connector. Reconnecting can create a new OAuth client; an approval for the old client may no longer apply.
>
> For `INSUFFICIENT_SCOPE`, review the named permission: website reads need `projects:read`, link reads need `watches:read`, and change history needs `events:read`. Choose the access needed for the intended job. See [MCP connection recovery](https://docs.agentlinkops.com/guides/connect-mcp.md#reconnect-after-a-failure).

> [accordion] What has been tested
>
> Our November 14, 2026 walkthrough connected an actual Grok Bot through OAuth and produced a portfolio report and CSV from saved link observations. A November 15 read-only Link Builder exercise used the existing AgentLinkOps MCP connection and public web research to produce a site brief, two plausible page fits and one outreach draft. Contact routes, sender access, prior-contact checks and suppression remained unresolved. This exercised draft preparation, not sending, AgentLinkOps writes, placement checks or recurring operation.
>
> Check your own sender, permissions and workflow before use. Reading a skill reference in chat does not install a native Grok skill.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.