Skip to main content
Use OpenClaw on a host you control to prepare campaigns or report on existing links. You need an installed OpenClaw agent and an authorized AgentLinkOps workspace.

1. Save the MCP server

Run these commands on the host that runs OpenClaw:
Complete browser sign-in and review the intended workspace access. A probe lists capabilities; it does not prove account reads succeed. See saved MCP servers and OpenClaw OAuth. Ask the agent to call get_workspace and list_projects. Check that it names the intended workspace and websites. If no website exists, add one first. Follow the returned connection recovery instructions if authorization fails.

2. Save the agent’s job

Copy your Link Builder or Link Monitor prompt into the intended agent’s persistent workspace instructions. Keep existing instructions and save a separate brief for each selected website. Have the agent read the maintained AgentLinkOps reference before using its tools. Continue with the role’s first campaign or saved-link report. Connect a sender only for Link Builder; use sender handoff for existing campaigns.

3. Schedule through the gateway

Once the ad hoc result works, agree cadence, timezone, report destination and approved actions. Ask the agent to inspect existing automations and propose a job using the saved instructions. Review it before enabling it, and check the first due execution. OpenClaw’s gateway runs scheduled work. Keep its host and gateway available, with the required connector and files reachable. A gateway configuration is not proof that a job ran. See how OpenClaw automations work. This path follows OpenClaw documentation reviewed November 15, 2026. We have not yet tested its AgentLinkOps OAuth connection or scheduled campaign execution. Compare agent setup paths.