Lleverage Docs
WebsiteLegalPlatform
  • Welcome
    • What is Lleverage?
    • Organisations
    • Projects
    • Members
  • Workflows
    • Workflows
      • Variables
      • Testing
      • Logs
      • Publishing
      • Version control
      • Workflow Co-Pilot
    • Actions
      • Controls
      • AI
        • Using the Prompt action
        • Prompt engineering
        • Model configuration
        • Agents
      • Tools
      • Integrations
    • Apps
      • Form app
      • Chat app
    • API Endpoints
    • Templates
  • KNOWLEDGE & DATA SETS
    • Knowledge Bases
  • Connections
    • Models
    • Databases
  • Help, Subscription and Other
    • Subscription Management
    • Release Notes
      • Version 0.1 - 15 July 2024
      • Version 0.2 - 6 August 2024
      • Version 0.3 - 23 September 2024
      • Version 0.4 - 7 October 2024
      • Version 0.5 - 28 October 2024
      • Version 0.6 - 6 December 2024
      • Version 0.7 - 14 January 2025
      • Version 0.8 - 11 February 2025
      • Version 0.9 - 21 March 2025
      • Version 1.0 - 8 April 2025
    • Support
Powered by GitBook
On this page
  • Available Integrations
  • Using Integrations in Workflows

Was this helpful?

  1. Workflows
  2. Actions

Integrations

Lleverage provides seamless connections to popular third-party services through dedicated integration nodes. These purpose-built nodes make it easy to interact with external platforms without writing complex code or managing authentication details manually. We're adding new integrations every week.

Available Integrations

Slack

Connect your workflows to Slack for team communication and notifications:

  • Get Slack Channel Messages: Retrieve messages from a specified Slack channel

  • Search Slack Messages: Find specific messages across channels based on criteria

  • Send Slack Message to Channel: Post messages directly to a Slack channel

  • Send Slack Message to Thread: Reply to existing message threads

  • Send Slack Message to User: Send direct messages to specific Slack users

Google Workspace

Integrate with Google's productivity tools:

  • Get Google Sheet Rows: Fetch data from Google Sheets

  • Run BigQuery Query: Execute queries against Google BigQuery datasets

Linear

Manage software development tasks through Linear:

  • Get Linear Issue: Retrieve a specific issue by its identifier (e.g., ABC-123)

  • Search Linear Issues: Find issues matching specific criteria

  • Get Linear Cycle Issues: Retrieve all issues from a particular development cycle

  • Create Linear Issue: Generate new issues directly from your workflow

HubSpot

Connect with your CRM data:

  • Get HubSpot Company: Retrieve company information

  • Get HubSpot Contact: Access contact details

  • Search HubSpot Companies: Find companies matching specified criteria

  • Search HubSpot Contacts: Locate contacts based on search parameters

  • Search HubSpot Leads: Find potential customer leads

Notion

Work with your Notion workspace:

  • Get Notion Page: Retrieve content from specific Notion pages

  • Search Notion Pages: Find pages based on search criteria

SharePoint

Connect to Microsoft's document management platform:

  • Get SharePoint File: Retrieve files from SharePoint by ID

Using Integrations in Workflows

Integrations can be added to your workflow like any other action. When you add an integration node:

  1. Select the appropriate integration action from the Integration tab or search for it

  2. Configure the connection settings (if not already set up at the organization level)

  3. Specify the parameters required for the specific integration

  4. Connect the integration node to your workflow

Connection Management

Integration nodes use connections defined at either the organization or project level:

  • Organization-level connections are available to all projects

  • Project-level connections override organization settings

To set up new connections, go to Settings → Connections and add the appropriate service.

Accessing Integration Data

Each integration node outputs data in a consistent format that can be referenced in subsequent nodes:

Copy{{integrationNodeId.specificProperty}}

For example:

  • Access Slack messages with {{getSlackChannelMessages.messages}}

  • Get Google Sheet data with {{getGoogleSheetRows.rows}}

  • Reference Linear issues with {{getLinearIssue.issue}}

Best Practices

  • Always use dedicated integration nodes instead of generic HTTP requests when available

  • Store API keys and credentials as Secrets rather than hardcoding them

  • Test your integrations thoroughly with the "Run" feature before publishing

  • Consider error handling for cases where the integration might fail

PreviousToolsNextApps

Last updated 2 months ago

Was this helpful?