Overview
Thelua integrations command enables you to connect your agent to third-party services like Linear, Discord, Google Calendar, HubSpot, and 250+ other integrations via Unified.to. When you connect an integration:
- An MCP server is automatically created to expose tools to your agent
- Triggers can be set up to wake up your agent when events occur in the connected service
Limit: Only 1 connection per integration type is allowed per agent. To change scopes, use
lua integrations update.How It Works
- Connect: Authenticate with a third-party service via OAuth or API token
- Auto-MCP: An MCP server is automatically created and activated for the connection
- Agent Access: Your agent can now use tools from that integration (e.g., create Linear issues, send Discord messages)
- Triggers (optional): Set up event-driven triggers to wake up your agent when things happen (e.g., a task is created, a message is received). Triggers are opt-in — you can skip them at connect and add them later.
Commands
lua integrations connect
Connect a new third-party integration with optional triggers.- CLI fetches available integrations
- You select or specify an integration and auth method
- Browser opens for OAuth authorization (or you enter API credentials)
- Connection is established and stored
- MCP server is automatically created and activated
- In interactive mode, you’re asked whether to configure triggers now (opt-in, default: skip). If triggers are specified via
--triggers, they are created immediately.
Triggers are opt-in: The interactive flow asks “Do you want to configure triggers now?” and defaults to skip — add only what you actually need. You can always add triggers later with
lua triggers create. When using --triggers non-interactively, triggers are created immediately.lua integrations list
View all connected integrations and their status.- 🟢 Active - Connection healthy, tools available
- 🟡 Connected (tools pending) - Connection healthy, MCP server inactive
- 🔴 Unhealthy - Re-authorization required
- ⏸️ Paused - Connection paused
lua integrations info
View detailed information about an integration type, including available OAuth scopes and triggers. This is useful for discovering what’s available before connecting.Friendly Labels: Scopes and triggers display user-friendly descriptions (e.g., “A new issue was created in Linear” instead of “task_task.created”) to help non-technical users understand what each option does.
lua integrations available
List all available integrations you can connect.- 🔐 OAuth only
- 🔑 API Token only
- 🔐🔑 Both available
lua integrations update
Update an existing connection’s OAuth scopes. This re-authorizes the connection with new permissions.Update deletes the old connection and creates a new one with updated scopes. You’ll need to re-authorize in the browser.
lua integrations disconnect
Remove a connected account. This also deletes the associated MCP server and any webhook subscriptions.lua integrations webhooks
Manage triggers (webhook subscriptions) for connected integrations. Triggers let your agent receive events when things happen in connected services (e.g., task created, message received).- list
- events
- create
- delete
- pause
- resume
List all triggers:Output:Status Icons:
- ✅ Active — trigger is running
- ⏸️ Paused by you — you paused this trigger; resume with
lua triggers resume - 💳 Credit-suspended — paused due to credit depletion; add credits to re-enable
- 🔴 Unhealthy — requires re-authorization
- ⚪ Paused externally — paused from outside Lua (e.g., Unified.to dashboard)
Webhook IDs are displayed for each trigger, making it easy to reference them for pause/resume/delete operations.
lua integrations mcp
Manage MCP servers for connections. MCP servers are automatically created when you connect an integration, but you can activate/deactivate them manually.- list
- activate
- deactivate
List connections with MCP server status:Output:
Non-Interactive Mode
All integrations commands support non-interactive mode for CI/CD, automation, and AI coding assistants.Discovery Commands
Use these to discover available options before connecting:Connect Options
Info Options
Disconnect Options
Trigger/Webhook Options
MCP Options
Examples
Workflow Example
1
Discover Available Integrations
2
Connect the Integration
lua triggers create.3
Verify Connection
4
Test with Agent
5
Manage Triggers
Event-Driven Triggers
Triggers are a powerful way to make your agent reactive to external events. Instead of polling or manually checking for updates, your agent automatically wakes up when something happens.How Triggers Work
- You connect an integration with triggers enabled
- Unified.to monitors the connected service for events
- When an event occurs (e.g., a task is created), Unified.to sends a webhook
- Your agent wakes up with the event data in
runtimeContext - The agent can respond based on what happened
Example: React to New Linear Issues
- Send a notification to Slack
- Update a dashboard
- Assign the issue to a team member
- Any other action your agent is configured to perform
Trigger Types
Most integrations use virtual webhooks. The polling interval can be configured:
Authentication Types
OAuth 2.0 (Recommended)
- Secure authorization flow via browser
- Scope selection for fine-grained permissions
- Automatic token refresh
- Requires OAuth to be configured for the integration in your Unified.to workspace
API Token / Personal Access Token
- Direct credential entry
- Simpler setup
- Token fields vary by integration (e.g., API Key, Personal Access Token, Bot Token)
- Instructions shown during connection for where to obtain credentials
Tips
Use Triggers for Event-Driven Workflows
Use Triggers for Event-Driven Workflows
Triggers make your agent reactive to external events. They are opt-in — add only what you actually need:Your agent automatically wakes up when events occur — no polling required!
Discover Before Connecting
Discover Before Connecting
Use discovery commands to understand what’s available:This is especially useful for AI coding assistants building agents programmatically.
Hide Sensitive Data
Hide Sensitive Data
By default,
--hide-sensitive true is enabled, which hides sensitive fields from MCP tool responses. Disable only if your agent needs access to sensitive data:Scope Selection
Scope Selection
When using OAuth, select only the scopes your agent needs. Use
all during development, then restrict to specific scopes in production:One Connection Per Integration
One Connection Per Integration
Each agent can have only one connection per integration type. To change accounts or scopes, use
lua integrations update or disconnect and reconnect.JSON Output for Scripting
JSON Output for Scripting
Use Perfect for CI/CD pipelines and AI coding assistants.
--json for machine-readable output:Related Commands
MCP Command
Manage all MCP servers (including non-integration servers)
Chat Command
Test your agent with integration tools
See Also
- MCP Servers Overview - Understanding MCP servers
- Webhooks Overview - Creating webhook handlers
- LuaWebhook API - Webhook API reference

