L2M MCP agents, governed
Integrations

Built-in nodes, and any MCP server.

These nodes ship with L2M and are configured in the studio, with credentials kept in the encrypted secret store. For everything else, attach an MCP server to an agent and govern its tools from the MCP control plane.

Agents and AI

Models, agents, tools and retrieval.

The pieces an agent is built from. Chat models attach to an agent's model slot; MCP tools and memory attach to its rings.

  • Chat models
    OpenAI · Anthropic · Gemini · Azure OpenAI · Ollama · OpenAI-compatible · AI gateway
  • Agents
    agent_orchestrator · supervisor_node
  • MCP Tool
    any MCP server, over stdio or Streamable HTTP
  • Knowledge bases
    built-in, with hybrid search and rerank
  • Vector stores
    Qdrant · Azure AI Search
  • Embeddings
    embeddings_azure_openai
  • Rerankers
    rerank · Cohere · Jina · Voyage
  • Citations
    extract_citations
  • Reports
    chart (Vega-Lite) · pdf_output
Apps

Messaging, work tracking, CRM, payments and storage.

App nodes run one operation each, with app triggers where the vendor sends events.

  • Slack
    slack_send_message · slack_trigger
  • Microsoft Teams
    teams_send_message
  • Email
    smtp_send_email · imap_email_trigger
  • Telegram
    telegram_send_message · telegram_trigger
  • Discord
    discord_send_message · discord_trigger
  • Twilio
    twilio_send_sms
  • GitHub
    github_action · github_webhook_trigger
  • Jira
    jira_create_issue · jira_search_issues
  • Notion
    notion_create_page · notion_query_database
  • Airtable
    create · list · update records
  • Google Sheets
    read · append · update · trigger
  • Google Calendar
    create_event · list_events
  • Google Drive
    google_drive_source · google_drive_trigger
  • Salesforce
    create_record · SOQL query
  • HubSpot
    create_contact · get_contact
  • Stripe
    create_customer · create PaymentIntent · webhook trigger
  • AWS S3
    put · get · list objects
Data and web

Databases, HTTP, Azure services and the web.

Query and write data stores, call any HTTP API, and read rendered web pages.

  • HTTP Request
    http_request · webhook_input · webhook_response
  • PostgreSQL
    postgres_query · postgres_trigger
  • MySQL
    mysql_query
  • MongoDB
    mongo_operation
  • Redis
    redis_command · redis_trigger
  • Azure Storage
    azure_storage
  • Azure Cosmos DB
    azure_cosmos_db
  • Azure Monitor
    azure_monitor_http
  • Web Browse
    web_browse (headless Chromium)
Triggers

Start a workflow from anywhere.

Besides app triggers and webhooks, workflows start on a schedule, from a form or chat, from a stream or queue, or as a tool other MCP clients call.

  • Schedules
    schedule_trigger (cron)
  • Forms and chat
    form_trigger · chat_trigger
  • Kafka
    kafka_trigger
  • RabbitMQ
    rabbitmq_trigger
  • MQTT
    mqtt_trigger
  • RSS / Atom
    rss_trigger
  • Server-sent events
    sse_trigger
  • Files
    file_trigger
  • Expose as MCP Tool
    mcp_server_trigger
Signed triggers

Inbound webhooks are checked before the workflow runs.

App triggers verify the sender's signature scheme; the generic webhook supports bearer tokens and HMAC-SHA256 with a replay window.

Stripe

Verifies the Stripe-Signature header (HMAC-SHA256 over the timestamp and body) within a replay window.

GitHub

HMAC-SHA256 over the raw body, checked against X-Hub-Signature-256.

Slack

Signing-secret verification of X-Slack-Signature with a timestamp check.

Discord

Ed25519 signature verification with the application's public key.

Telegram

Matches X-Telegram-Bot-Api-Secret-Token against the configured secret.

Generic webhook

none, bearer_token or hmac_sha256 on any webhook_input, with optional idempotency keys.

Need something that isn't listed?

Connect its MCP server and register it once: L2M probes it, tracks its tools and applies your policies. Or write a community node package with the node SDK.