#Integrations
Vatio connects to the services your agent and your team already use. Each one has its own page with everything it does, how to connect it, and what it can and cannot see.
Supabase
Your users sign in with Supabase Auth: the widget, WhatsApp and Instagram know who they are, with no code.
Claude Code
Skills that build your agent and fix what supervisors flag.
WhatsApp
Your business number, through Meta. A channel, so it lives under Channels.
Instagram
DMs on a professional account, through Meta. Also under Channels.
#At a glance
| Integration | What it gives your agent | Where you connect it | What Vatio can reach |
|---|---|---|---|
| Supabase | Signed-in visitors on every channel, and tools that read their rows under your Row Level Security | vatio auth --supabase, or Channels → Supabase in the inbox | The project's public keys; with the inbox connection, read-only access to the organization's projects, public API keys and auth settings |
| Claude Code | A coding agent that builds and improves your Vatio agent | /plugin install in Claude Code, or npx @vatio-ai/skills for any coding agent | Nothing: the skills run on your machine, through the CLI |
| Claude Code routines | A tool that hands a WhatsApp conversation with your numbers to a routine on claude.ai, which reads it and can answer | vatio routines create, then routine: in a tool file | Nothing: the routine reads the conversation with a server key you give it |
| Conversations on your business number | Channels → WhatsApp in the inbox | The number you connect | |
| Conversations in your DMs | Channels → Instagram in the inbox | The account you connect |
#Your own backend
Your API is not an integration to install: the agent calls it through tools, each one an HTTP request described in YAML, and it tells your backend what happened through webhooks. If your users sign in to that backend themselves, sign a JWT for them as Authentication describes.