Skip to Content
Palui Agent
Connectors

Connectors

Every connector that ships in Palui Agent v1, grouped by kind, and how each connector page is laid out.

Everything optional in Palui is a connector. You add, test, pause and remove them on the Saklar page. See Saklar for the lifecycle every connector shares.

v1 connectors

ConnectorKindWhat it does
TelegramchannelChat with Palui from a Telegram bot.
WhatsAppchannelChat with Palui from WhatsApp, as a linked device.
Web chatchannelChat with Palui in the dashboard, no phone needed.
CLIProxyAPImodelModels through CLIProxyAPI, so existing subscriptions pay for them.
ai-gatewaymodelA second model provider and the fallback in every chain.
recallmemoryLong-term memory: tools, auto-recall and auto-save.
MCP serverstoolsAny Streamable HTTP MCP server, with per-tool switches.
RemindersskillReminders set in plain language that survive restarts.
JobsskillScheduled agent jobs, the daily briefing and the heartbeat.
Voice-inskillTranscribes voice messages you send.
Web fetchskillReads web pages behind an SSRF guard.
Inbound webhooksskillTurns signed HTTP posts into messages.
Google CalendarskillRead-only access to your calendar.

How each page is laid out

Every connector is defined by a manifest, and its page follows the same shape:

  1. What it does: one paragraph.
  2. Connect: the setup steps in the dashboard wizard, and what Test checks.
  3. Settings: the fields you can change later.
  4. Tools: what the model can call, with each tool's class.
  5. Pause and remove: what happens to its work and its credentials.

Two rules hold for every connector. Pausing takes effect from the next turn, and tool calls already running finish. Removing asks first, deletes the stored credentials and returns the connector to not set up.

Not in v1

stdio MCP servers, a shell tool and a browser tool are planned. They need binaries in the container and a sandbox. Voice replies, self-written skills, subagents and group chats are planned too. See the changelog.

On this page