WebsiteLegalPlatform

Integrations

External Apps in Lleverage provide seamless connections to over 2,000 third-party services and platforms. These integrations allow you to incorporate external functionality directly into your workflows, extending the capabilities of your automations beyond the Lleverage platform.

Overview

Integrations in Lleverage are designed to work exactly like the native products you already use. When you add an integration, you're not just connecting to a service — you're gaining access to all the specific actions that service provides, allowing you to use information from any source and output it in any format you can imagine.

Key Features

  • Access to 2,000+ integration providers

  • Each provider offers multiple specific actions

  • Native-like functionality that mirrors how you use the actual product

  • Can retrieve information from external sources

  • Can send data to external platforms

  • Authentication handled securely through Lleverage

  • Optional properties for advanced configuration

  • Can be used as workflow triggers or actions

💡 Understanding Integration Actions: Each integration provider (like Slack, Gmail, or Salesforce) offers multiple specific actions. For example, Slack doesn't just "connect", it provides actions like "Send Message," "Create Channel," "Update Status," and more. This means you can perform virtually any task you would normally do in that application.

How to Add an External App

  1. Click on the "Add Action" button in your workflow

  2. Navigate to the External Apps section by either: , Scrolling to the bottom of the "All" tab, or , Selecting the "External Apps" tab directly

  3. Browse through providers (sorted by popularity)

  4. Click on a provider to see all available actions for that service

  5. Select the specific action you want to add to your workflow

💡 External Apps are organized differently than other nodes — they're grouped by provider first due to the large number of integrations available.

How to Configure an External App

  1. Select the External App node in your workflow

  2. Click on "Add New Connection" in the configuration panel

  3. Click "Continue" in the authentication modal

  4. Complete the authentication process (this varies by provider)

  5. Configure the specific action settings

  6. Check "Optional Properties" at the bottom for additional advanced settings

⚠️ Be mindful of your plan limits when using External Apps. Frequent calls to integrations might consume your workflow runs quickly, especially with scheduled triggers.

How to Use External Apps as Triggers

External Apps can initiate workflows based on events in third-party services:

  1. Add an Integration trigger to your workflow

  2. Select your provider and configure authentication

  3. Choose the specific trigger event (e.g., "When email received," "When form submitted")

  4. Set up any additional trigger conditions

  5. Configure how the workflow should respond to the trigger

⚠️ When using External Apps as triggers, be especially careful with automation frequency as triggers may run automatically and consume your plan's workflow runs.

Trigger Action

How to Request Missing Integrations

If you can't find a specific integration or action you need, you have two options:

Option 1: Connect Directly via API

  1. Navigate to the Advanced category section in the action picker

  2. Select "Send HTTP Request"

  3. Follow the provider's development documentation to configure:

    1. URL endpoint

    2. Authentication headers

    3. Request method (GET, POST, PUT, DELETE)

    4. Request body and parameters

  4. Test the connection using the Run panel

💡 This method gives you immediate access to any API without waiting for official integration support.

Option 2: Request the Integration

  1. In the Add Action Menu: Search for the action and click "Request Action" when no results appear

  2. Via User Settings: Go to User Settings → Request Feature

  3. Through Support: Contact the support team via the chat feature

💡 Enterprise customers may receive timeline estimates for requested integrations.

Request in Sidebar Navigation
Request in the Add Action Menu

Understanding Integration Functionality

How Integrations Work

  • Native Experience: Each integration works exactly like the product itself. If you're using the Gmail integration, it behaves like Gmail. If you're using Salesforce, it operates like Salesforce.

  • Specific Actions: Every provider offers distinct actions that mirror what you can do in their platform

  • Bidirectional Flow: Use integrations to both retrieve and send information

Common Use Cases

  • Data Input: Pull customer data from Salesforce, retrieve emails from Gmail, fetch tasks from Asana

  • Data Output: Send Slack messages, create Trello cards, update Google Sheets

  • Process Automation: Trigger workflows based on external events, update multiple systems simultaneously

  • Information Synthesis: Combine data from multiple sources into unified reports or actions

Integration Structure

External App nodes follow the same structure as other Lleverage nodes:

  • Variable chip in the top left shows the output

  • Expand/collapse controls in the top right

  • Authentication and configuration in the main body

  • Optional properties section for advanced settings

Best Practices

  • Test Authentication: Always test your connection after initial setup

  • Use Variables: Pass data between integrations using Lleverage variables

  • Handle Errors: Add error handling for external API calls that might fail

  • Monitor Usage: Keep track of API calls to avoid hitting rate limits

  • Secure Credentials: Use Lleverage's secure authentication rather than hardcoding credentials

💡 Pro Tip: Many integrations offer webhook capabilities, allowing you to create real-time, event-driven workflows that respond instantly to changes in your external systems.

Last updated