Connect Apollo.io to Windsurf
Give Windsurf governed access to Apollo.io’s 99 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Apollo.io to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Add Apollo.io to Runlayer
Apollo.io isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Apollo.io’s 99 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Apollo.io
Sign in the way Apollo.io requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Apollo.io from Windsurf
Apollo.io’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
99 Apollo.io tools in Windsurf
Runlayer policy decides which of these Windsurf users can call.
Create accounts bulk
Create many accounts (companies) in one call.
Create accounts
Use the Create an Account endpoint to add a new account to your team's Apollo account.
Update accounts
Use the Update an Account endpoint to update existing accounts in your team's Apollo account.
Agent analyze performance
"How is my team performing on outbound?" (synthesized narrative report)
Agent build lead scores
"Build an account score for India-based EV / clean-energy companies."
Agent connect mailbox
"Connect my Gmail / Outlook." | "Apply best-practice send settings."
Agent draft sequence copy
"Draft a 6-step multichannel sequence (3 emails, 2 calls, 1 LinkedIn) for healthcare
Agent explain howto
"How do I connect Apollo to Salesforce / reset my password?"
Control
What Runlayer can see and stop in Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Apollo.io call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more