> ## Documentation Index
> Fetch the complete documentation index at: https://runlet.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Overview

> Connect Runlet with your favorite tools and services

## Core Integrations

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

<CardGroup cols={2}>
  <Card title="n8n Integration" icon="link" href="/integrations/n8n-setup">
    Connect your n8n instance to deploy and manage workflows
  </Card>

  <Card title="Supabase Integration" icon="database" href="/integrations/supabase-setup">
    Automated database setup for workflows that need data storage
  </Card>
</CardGroup>

## Integration Architecture

Runlet connects with your tools through two main integrations:

```mermaid theme={null}
graph TB
    A[Runlet Platform] --> B[n8n Instance]
    A --> C[Supabase Database]

    B --> D[External Services]
    D --> E[Slack, Google Sheets, Stripe, etc.]

    C --> F[Automated Database Setup]
    F --> G[Tables, Functions, Indexes]

    subgraph "Direct Integrations"
        B
        C
    end

    subgraph "Via n8n"
        D
        E
    end

    subgraph "Database Automation"
        F
        G
    end
```

## How Integrations Work

### 1. Direct Integrations

Runlet connects directly to these two services:

<AccordionGroup>
  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>
</AccordionGroup>

### 2. Services Available Through n8n

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

<AccordionGroup>
  <Accordion title="Communication & Messaging">
    **Slack, Discord, Microsoft Teams, Telegram, Email**

    * Send notifications and alerts
    * Create interactive bots and responses
    * Automate team communications
  </Accordion>

  <Accordion title="Data & Productivity">
    **Google Sheets, Airtable, Notion, Microsoft Office** - Process and sync data
    between platforms - Automate data entry and updates - Generate reports and
    summaries
  </Accordion>

  <Accordion title="E-commerce & Payments">
    **Stripe, PayPal, Shopify, WooCommerce** - Automate order processing - Handle
    payment notifications - Manage customer lifecycle
  </Accordion>

  <Accordion title="Marketing & CRM">
    **HubSpot, Salesforce, Mailchimp, SendGrid**

    * Lead nurturing and scoring
    * Email marketing automation
    * Customer relationship management
  </Accordion>
</AccordionGroup>

## Supported Services

Runlet supports all services available in n8n, including:

<Tabs>
  <Tab title="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
  </Tab>

  <Tab title="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
  </Tab>

  <Tab title="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
  </Tab>

  <Tab title="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
  </Tab>

  <Tab title="Development">
    * **GitHub** - Code repository and collaboration - **GitLab** - DevOps
      platform - **Jira** - Issue tracking and project management - **Jenkins** -
      Continuous integration - **Docker** - Containerization - **AWS** - Cloud
      services
  </Tab>

  <Tab title="Analytics">
    * **Google Analytics** - Web analytics - **Mixpanel** - Product analytics -
      **Segment** - Customer data platform - **Amplitude** - Digital analytics -
      **Hotjar** - User behavior analytics
  </Tab>
</Tabs>

## Integration Setup Process

Setting up integrations follows a consistent pattern:

<Steps>
  <Step title="Prerequisites">
    * Active account with the service you want to integrate - Required
      permissions (admin access may be needed) - API keys or authentication
      credentials
  </Step>

  <Step title="Configure in Runlet">
    * Navigate to Settings → Integrations - Find the service and click "Connect" -
      Enter required credentials and settings
  </Step>

  <Step title="Test Connection">
    * Use the built-in connection test - Verify data access and permissions -
      Troubleshoot any authentication issues
  </Step>

  <Step title="Deploy Workflows">
    * Create workflows that use the integration - Test workflow execution -
      Monitor for errors and performance
  </Step>
</Steps>

## Authentication Methods

Different services use various authentication methods:

<AccordionGroup>
  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="Custom Authentication">
    **Services**: Enterprise systems, custom APIs

    **Setup**:

    * Configure custom headers or authentication methods
    * May require additional setup in n8n
    * Test with sample requests
  </Accordion>
</AccordionGroup>

## 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

<AccordionGroup>
  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>
</AccordionGroup>

## Getting Help

<CardGroup cols={2}>
  <Card title="Integration Guides" icon="book" href="/integrations/n8n-setup">
    Detailed setup guides for each integration
  </Card>

  <Card title="Community Support" icon="discord" href="https://discord.gg/YcdHU6CtNW">
    Get help from other Runlet users
  </Card>

  <Card title="Technical Support" icon="envelope" href="mailto:support@runlet.ai">
    Direct support for integration issues
  </Card>

  <Card title="Service Documentation" icon="external-link" href="https://docs.n8n.io/integrations/">
    Official n8n integration documentation
  </Card>
</CardGroup>