Integrations Overview

Connect Runlet with your favorite tools and services

Core Integrations

Runlet currently supports two powerful integrations that enable comprehensive workflow automation:

n8n Integration

Connect your n8n instance to deploy and manage workflows

Supabase Integration

Automated database setup for workflows that need data storage

Integration Architecture

Runlet connects with your tools through two main integrations:

How Integrations Work

1. Direct Integrations

Runlet connects directly to these two services:

n8n Instance

• Purpose: Deploy and manage automation workflows
• Connection: Direct API connection to your n8n instance
• Authentication: API key + username
• Features: Workflow deployment, execution monitoring, credential management

Supabase Database

• Purpose: Automated database setup for data-driven workflows
• Connection: Direct database connection
• Authentication: Service role key
• Features: Automatic table creation, function setup, index optimization
• Smart Setup: Runlet automatically creates the database structure your workflows need

2. Services Available Through n8n

Once connected to your n8n instance, you can create workflows using any n8n-supported service:

Communication & Messaging

Slack, Discord, Microsoft Teams, Telegram, Email

• Send notifications and alerts
• Create interactive bots and responses
• Automate team communications

Data & Productivity

Google Sheets, Airtable, Notion, Microsoft Office - Process and sync data between platforms - Automate data entry and updates - Generate reports and summaries

E-commerce & Payments

Stripe, PayPal, Shopify, WooCommerce - Automate order processing - Handle payment notifications - Manage customer lifecycle

Marketing & CRM

HubSpot, Salesforce, Mailchimp, SendGrid

• Lead nurturing and scoring
• Email marketing automation
• Customer relationship management

Supported Services

Runlet supports all services available in n8n, including:

Communication

• Slack - Team messaging and notifications - Discord - Community and gaming communications - Microsoft Teams - Enterprise collaboration - Telegram - Instant messaging and bots - WhatsApp Business - Customer communications - Email (SMTP/IMAP) - Traditional email automation

Productivity

• Google Workspace - Gmail, Sheets, Drive, Calendar - Microsoft 365 - Outlook, Excel, OneDrive, Teams - Notion - Knowledge management and databases - Airtable - Flexible database and project management - Monday.com - Work management platform - Trello - Kanban-style project management

E-commerce

• Shopify - E-commerce platform - WooCommerce - WordPress e-commerce - Stripe - Payment processing - PayPal - Online payments - Square - Point of sale and payments - Magento - Enterprise e-commerce

Marketing

• Mailchimp - Email marketing - SendGrid - Email delivery - HubSpot - Inbound marketing and CRM - Salesforce - Customer relationship management - Facebook Ads - Social media advertising - Google Ads - Search and display advertising

Development

• GitHub - Code repository and collaboration - GitLab - DevOps platform - Jira - Issue tracking and project management - Jenkins - Continuous integration - Docker - Containerization - AWS - Cloud services

Analytics

• Google Analytics - Web analytics - Mixpanel - Product analytics - Segment - Customer data platform - Amplitude - Digital analytics - Hotjar - User behavior analytics

Integration Setup Process

Setting up integrations follows a consistent pattern:

1. Prerequisites

   • Active account with the service you want to integrate - Required permissions (admin access may be needed) - API keys or authentication credentials
2. Configure in Runlet

   • Navigate to Settings → Integrations - Find the service and click “Connect” - Enter required credentials and settings
3. Test Connection

   • Use the built-in connection test - Verify data access and permissions - Troubleshoot any authentication issues
4. Deploy Workflows

   • Create workflows that use the integration - Test workflow execution - Monitor for errors and performance

Authentication Methods

Different services use various authentication methods:

API Keys

Services: OpenAI, Stripe, SendGrid, many others

Setup:

• Generate API key in service dashboard
• Copy key to Runlet integration settings
• Test connection to verify access

Security: Store keys securely, rotate regularly

OAuth 2.0

Services: Google, Microsoft, Slack, GitHub Setup: - Click “Connect” in Runlet - Authorize Runlet in service’s OAuth flow - Grant necessary permissions Security: Tokens refreshed automatically, can be revoked anytime

Basic Authentication

Services: Some databases, FTP servers, legacy systems Setup: - Enter username and password - Configure any additional connection parameters - Test connectivity Security: Use strong passwords, consider IP restrictions

Custom Authentication

Services: Enterprise systems, custom APIs

Setup:

• Configure custom headers or authentication methods
• May require additional setup in n8n
• Test with sample requests

Best Practices

Security

• Use environment variables for sensitive credentials
• Rotate API keys regularly
• Apply principle of least privilege - only grant necessary permissions
• Monitor access logs for suspicious activity
• Use OAuth when available instead of API keys

Performance

• Configure rate limits appropriately
• Use webhooks instead of polling when possible
• Implement retry logic for transient failures
• Monitor quota usage to avoid service limits
• Cache frequently accessed data

Reliability

• Test integrations thoroughly before production use
• Set up monitoring and alerting for integration failures
• Have fallback procedures for when integrations are unavailable
• Document integration dependencies and requirements
• Keep credentials updated before they expire

Troubleshooting Common Issues

Authentication Failures

Symptoms: 401/403 errors, “Invalid credentials”

Solutions:

• Verify API keys are correct and not expired
• Check user permissions in the target service
• Ensure OAuth tokens haven’t been revoked
• Test credentials directly with service API

Rate Limiting

Symptoms: 429 errors, “Too Many Requests” Solutions: - Implement exponential backoff retry logic - Reduce request frequency - Upgrade service plan for higher limits - Use batch operations when available

Network Connectivity

Symptoms: Timeouts, connection refused errors Solutions: - Check firewall and network settings - Verify service endpoints are accessible - Test from different network locations - Check service status pages for outages

Data Format Issues

Symptoms: Parsing errors, validation failures

Solutions:

• Verify data format matches API expectations
• Check field mappings and transformations
• Validate data types and required fields
• Test with minimal data sets first

Getting Help

Integration Guides

Detailed setup guides for each integration

Community Support

Get help from other Runlet users

Technical Support

Direct support for integration issues

Service Documentation

Official n8n integration documentation