Skip to main content
Rilo provides access to 1000+ integrations through multiple integration methods, allowing you to connect workflows to virtually any service or tool.

​
Integration Methods

Rilo supports three main integration methods:

Pre-built Integrations

1000+ integrations via Composio platform

MCP Libraries

Model Context Protocol servers for custom tools

Custom Integrations

Connect to any REST API or MCP server

​
Pre-built Integrations

Rilo provides 1000+ pre-built integrations for popular services via the Composio platform.

​
Integration Categories

  • Email Tools: Gmail, Outlook, Zoho Mail
  • Document & File Management: Google Docs, Sheets, Drive, Dropbox, OneDrive, Box
  • Communication & Collaboration: Slack, Discord, Microsoft Teams, Zoom, Telegram, WhatsApp
  • Developer Tools & Infrastructure: GitHub, GitLab, Jira, AWS, Docker
  • Finance & Accounting: QuickBooks, Stripe, PayPal, Xero, Shopify, Square
  • Marketing & Social Media: HubSpot, Mailchimp, Facebook, Instagram, LinkedIn, Twitter
  • Project Management & Productivity: Asana, Trello, Notion, Monday.com
  • Sales & CRM: Salesforce, Pipedrive, HubSpot CRM, Zendesk
  • HR & People Operations: BambooHR, Workday, Gusto
  • Specialized Tools: Canvas, Fireflies, Gong, Polygon, and more

​
Connecting Integrations

  1. Go to Integrations page: Browse available integrations
  2. Click “Connect”: Authenticate with the service
  3. Use in workflows: Integration becomes available as a library
Most Composio integrations use OAuth for authentication. You’ll be redirected to authenticate with the service.

​
MCP Libraries

Model Context Protocol (MCP) servers extend Rilo with custom tools and capabilities.

​
What is MCP?

MCP is a protocol for connecting AI applications to external tools and data sources. Rilo supports MCP servers to extend its capabilities beyond standard integrations.

​
Adding MCP Servers

  1. Go to Integrations page: Navigate to MCP section
  2. Add MCP Server: Provide server URL and authentication
  3. Tools Available: MCP tools become available as libraries
MCP servers can provide custom tools, data sources, and capabilities not available in standard integrations.

​
Custom Integrations

Create custom integrations for any REST API or MCP server.

​
Custom API Integrations

Connect to any REST API by defining endpoints:
  1. Go to Integrations page: Navigate to Custom Integrations section
  2. Create Custom Integration: Select “API” type
  3. Define Endpoints: Specify API endpoints and methods
  4. Configure Authentication: Set up API keys, OAuth, etc.
  5. Add Tools: Add multiple tools to your integration
  6. Generate Library: Rilo generates a library from your API definition

​
Custom MCP Tools

Connect to MCP servers for dynamic tool discovery:
  1. Go to Integrations page: Navigate to Custom Integrations section
  2. Create Custom Integration: Select “MCP” type
  3. Configure Server: Provide MCP server URL and authentication
  4. Discover Tools: Rilo automatically fetches available tools
  5. Generate Library: Tools become available as library methods
Custom integrations enable you to connect to internal tools, specialized services, or any REST API or MCP server.

​
Integration Capabilities

​
What Integrations Can Do

✅ Read data: Fetch data from services ✅ Write data: Create, update, delete records ✅ Trigger workflows: Start workflows on events ✅ Send notifications: Send messages, emails, etc. ✅ Process files: Upload, download, process files ✅ Automate workflows: Connect multiple services together

​
Integration Limitations

❌ Single account per workflow: Cannot use multiple accounts of the same tool in one workflow ❌ OAuth scopes: Limited to granted OAuth scopes ❌ API rate limits: Subject to service rate limits ❌ Service availability: Depends on external service availability
Each tool integration connects to a single authenticated account. To use multiple accounts, create separate workflows.

​
Using Integrations in Workflows

​
Via Natural Language

Describe what you want: 
"Read emails from Gmail and create tasks in Asana"
The AI agent automatically:
  • Identifies required integrations
  • Prompts for connection if needed
  • Uses appropriate tools in generated code

​
In Generated Code

Integrations are used as libraries: 
from library.communication_tools_library import CommunicationToolsLibrary
from library.project_management_tools_library import ProjectManagementToolsLibrary

gmail = CommunicationToolsLibrary()
asana = ProjectManagementToolsLibrary()

# Read emails
emails = gmail.read_emails(query="is:unread")

# Create tasks
for email in emails:
    asana.create_task(
        name=email["subject"],
        notes=email["body"]
    )

​
Integration Management

​
Viewing Connected Integrations

  • Integrations page: See all connected integrations
  • Status indicators: See which integrations are active
  • Connection details: View authentication status
  • Tool counts: See how many tools each integration provides

​
Disconnecting Integrations

  1. Go to Integrations page
  2. Find integration: Locate the integration to disconnect
  3. Click “Disconnect”: Remove the connection
Disconnecting an integration will break workflows that use it. Update workflows before disconnecting.

​
Tool Documentation

Rilo provides comprehensive documentation for all available tools: Each tool documentation page includes:
  • Available functions/actions
  • Available triggers
  • Authentication requirements
  • Usage examples
  • Best practices

​
Best Practices

Connect integrations only when needed. Too many connections can be hard to manage.
Review OAuth scopes when connecting. Only grant necessary permissions.
Test integrations in workflows before deploying to production.
Monitor integration usage and API rate limits to avoid issues.
Create custom integrations for internal APIs or specialized services not available in Composio.

​
Troubleshooting

  • Verify credentials are correct
  • Check OAuth permissions
  • Ensure service is accessible
  • Try disconnecting and reconnecting
  • Verify integration is connected
  • Check integration is active
  • Ensure correct library name is used
  • Refresh workflow editor
  • Implement rate limiting in workflows
  • Use caching to reduce API calls
  • Contact service provider for higher limits
  • Consider upgrading integration plan
  • Verify API base URL is correct
  • Check authentication credentials
  • Test API endpoint directly
  • Review API documentation
Rilo’s integration ecosystem is continuously growing. New integrations are added regularly. Check the Integrations page for the latest additions.