Integrations
Credentials are encrypted at rest, connections are tested on save, and every write goes through approvals. Each entry below also states what the connection reads, the same list our privacy policy relies on.
Reporting, campaign and creative changes through the approvals queue, lead-gen forms, and organic Facebook Page and Instagram widgets.
Data accessed: Ad account metadata and performance metrics (spend, impressions, clicks, conversions), campaign structure, creatives, Page and Instagram insights, lead-gen forms, and customer-list audiences you choose to upload (hashed before upload).
Campaign, ad group, keyword, asset, and budget reports; proposed edits applied after approval; Audience Manager access.
Data accessed: Google Ads account metadata, campaign structure, and performance metrics for the customer accounts you connect.
Inbound conversations triaged by AI into tasks, client attribution, drafted replies your team approves, and completion sweeps.
Data accessed: Conversation threads, customer email addresses, mailbox metadata, and attachments from the mailboxes you connect.
Pay-now buttons on public invoice and proposal pages, deposits, and webhook-driven payment status.
Data accessed: Checkout session and payment status. Card details never touch Voo; they are entered on Stripe.
Agents open issues and pull requests; import agent skills from public repositories.
Data accessed: Repository metadata and the issues and pull requests Voo creates in repositories you authorize.
Uptime incidents become tasks for the responsible team and close when the incident resolves.
Data accessed: Incident payloads sent to Voo by Better Stack webhooks.
Visual bug reports from client sites sync into tasks with comments kept in step.
Data accessed: Bug reports, comments, and screenshots from the BugSmash projects you connect.
Site and domain management for WordPress hosting from inside tasks and agent tools.
Data accessed: Server, site, and domain records for the GridPane account you connect.
Application and domain management for servers you run on ServerAvatar.
Data accessed: Server, application, and domain records for the ServerAvatar account you connect.
Per-brand site connections so agents and staff can publish and check sites without hunting for logins.
Data accessed: Site metadata and the content Voo publishes to sites you connect.
Notification rules that route task, approval, and client events to channels.
Data accessed: Channel identifiers and the messages Voo posts. Voo does not read your Slack history.
Transactional email for proposals, invoices, client replies, and notifications, sent from your agency's identity.
Data accessed: Recipient addresses and message content for the emails Voo sends on your behalf.
Two-way task mapping for teams migrating from Wrike or collaborating with clients who live there.
Data accessed: Tasks, folders, and comments in the Wrike spaces you map.
One key for every model Voo uses: chat, sub-agents, images, video, transcription, captions, speech, and music. Swap models from settings.
Data accessed: The prompts, files, and context Voo sends to the models you select, routed through OpenRouter to the model provider.
Plug external MCP servers into Voo's agents as tools, and use Voo itself as an MCP server from Claude, Cursor, or your own agents.
Data accessed: Whatever the connected server's tools read or write; each server is namespaced and can be disabled per workspace.
Fallback fetcher for the agent's web tool when a site blocks plain requests.
Data accessed: The public URLs an agent asks to read.
Voo exposes scoped API keys, signed webhooks, and an MCP server, and agents can use any MCP server you add. Tell us what you need.
Set up a workspace in minutes, or ask us for a walkthrough with your services and clients loaded in.