Integrations
Eligoo Integrations
Eligoo connects to the tools you already use — AI model providers, telephony, social channels, advertising, data sources, Google Workspace and your own mailbox — using your own accounts and keys. Nothing runs through a shared Eligoo account: each connection is made once per workspace, verified when you add it, and used only by the AI employees whose role needs it.
By signing up you agree to the Terms and Privacy Policy.
AI models (bring your own keys)
Connect one or more providers, set a workspace default model and assign a different model to any employee. Model usage is billed to you by the provider.
OpenAI
GPT models for any employee, plus OpenAI voices for the AI voice agent.
OpenAnthropic
Claude models for employees that write, plan and reason over long context.
OpenGoogle Gemini
Gemini models through a Google AI key.
OpenGroq
Fast inference on open-weight models — useful where latency matters, such as live calls.
OpenOpenRouter
One key that routes to many models, so you can mix providers without managing several accounts.
Open
Voice and telephony
The AI voice agent runs on Eligoo’s self-hosted LiveKit stack. You bring the phone numbers and the speech providers.
- Built in
LiveKit
The media server, SIP gateway and recording pipeline behind every call. Nothing for you to sign up for.
Open Deepgram
Default speech-to-text (nova-3) and an option for text-to-speech voices.
OpenElevenLabs
Natural voices for outbound and inbound AI calls.
OpenTwilio
Elastic SIP trunk created automatically from your Account SID and Auth Token.
OpenTelnyx
SIP trunking with credentials you enter manually.
OpenPlivo
Zentrunk SIP trunking for AI calling.
OpenVobiz
SIP trunking that is popular for Indian numbers.
Open
How integrations work in Eligoo
Every integration is added per workspace, either by signing in with OAuth (Google Workspace, Meta, LinkedIn, YouTube and the other social channels) or by pasting an API key or credentials (model providers, speech providers, Apollo, Serper, fal.ai, telephony trunks and your mailbox). Eligoo verifies the connection when you add it — a test request, a login to the mailbox, a check of the trunk credentials — so a broken key is caught on the settings page rather than in the middle of a task.
Keys and tokens are stored server-side and masked in the interface after they are saved. They are never returned to the browser, and they are never shared between workspaces. Model prompts, generated media and call audio go straight to the provider you connected under your own account, so each provider’s data terms apply to that traffic.
Each AI employee only has access to the integrations its role needs. Sage can publish to your social channels; Pixel cannot. Hook can send from your mailbox and dial your trunk; Radar cannot. Boost can read Meta Ads; nobody else can. That separation is part of how each employee’s approval boundary is enforced.
Disconnecting an integration stops the employees that rely on it. A removed model key takes an employee to the Blocked status until another model is assigned; a removed mailbox pauses running sequences; a removed trunk stops calling campaigns. Nothing silently falls back to a shared credential.
Frequently asked questions
Do I need to connect every integration to use Eligoo?
No. At minimum you connect one AI model provider so the employees can think. Everything else is added when an employee needs it — a mailbox before Hook sends email, a SIP trunk before it calls, a social channel before Sage publishes.
Can I use my own API keys instead of paying Eligoo for model usage?
Yes — that is the only way Eligoo works. You connect your own OpenAI, Anthropic, Google Gemini, Groq or OpenRouter account and the provider bills you directly for tokens. Eligoo credits cover the platform side of the work.
Where are my keys stored?
Server-side in your workspace, encrypted at rest on the hosting provider’s disks, and shown only as a masked value in the interface once saved. Details are on the security page.
Which CRMs does Eligoo integrate with?
Eligoo has a built-in CRM that Radar, Hook and Ledger work in. There is no third-party CRM connector today; records can be exported from the workspace.
What happens to a running task if an integration fails?
The execution fails, the task returns to a pending state and the employee’s status shows Blocked or Error with the reason in the activity log. Once the connection is fixed the work can be resumed or re-approved.
Connect your tools and put the workforce to work
Add a model key, connect a channel, and hire the employees you need. Eligoo connects to the AI provider accounts you already have (OpenAI, Anthropic, Google Gemini, Groq or OpenRouter). Keys are stored server-side in your workspace and never sent to the browser.
By signing up you agree to the Terms and Privacy Policy.
Last updated 23 September 2026