Lyft API Integration Toolset for AI Agents (MCP) - n8n Workflow

• Developers building AI agents (LLMs) requiring real-time transport service integration.


• Automation experts looking for powerful n8n templates for external API integration.


• Users needing a centralized n8n workflow for testing and production Lyft operations.


• Teams utilizing n8n to create robust, service-oriented AI applications.

This is an advanced aiautomationworkflows designed to serve the complete Lyft API suite to external AI agents or Large Language Models (LLMs). By utilizing the Multi-Channel Protocol (MCP) n8n trigger, this powerful n8n workflow centralizes 16 distinct Lyft operations—from calculating cost estimates and requesting new rides to managing sandbox environment settings. This template is essential for those building sophisticated travel planning or logistical AI agents, ensuring they have robust, enterprise-grade access to the Lyft service through a standardized n8n node structure. This simplifies the process of creating complex AI-driven applications using n8n. This flexible n8n workflow serves as a comprehensive set of n8n templates for transport API integration.

The operation begins with the dedicated Lyft MCP Server n8n trigger. This specialized n8n trigger waits for requests (commands) from an external AI agent or system. The MCP n8n node provides a unified interface for the AI. Based on the agent's natural language request (e.g., "retrieve cost estimate" or "cancel ride"), the MCP trigger dynamically routes the command to the corresponding specialized httpRequestTool n8n node.

This particular n8n workflow segments the tools into three functional areas:

1. Public Operations: For general queries like fetching cost estimates, ETA, and listing ride types.


2. User Operations: For transactional actions like requesting a new ride, retrieving user profiles, cancelling rides, and submitting ratings.


3. Sandbox Operations: Essential testing tools that allow the n8n workflow to interact with Lyft's simulated environment (e.g., setting prime time percentages, updating driver availability).

Each individual httpRequestTool is pre-configured to execute the necessary Lyft API call. The execution result is then captured and passed back through the MCP trigger to the initiating AI agent, completing the full automation cycle within this single n8n workflow.

1. Import the n8n Workflow: Download the provided JSON data and import this n8n workflow into your n8n instance using the "Import from JSON" feature.


2. MCP Trigger Setup: The primary n8n node requiring attention is the Lyft MCP Server n8n trigger. After the n8n workflow is activated, it will provide a unique Webhook URL. This URL must be provided to your AI agent or LLM system as a callable tool endpoint.


3. Credentials: All underlying httpRequestTool nodes rely on established Lyft API credentials. You must set up an OAuth2 credential specific to the Lyft API within your n8n environment, ensuring it has the necessary scopes (e.g., profile, rides.request, rides.receipts).


4. Activation: Save and activate the n8n workflow to ensure the MCP n8n trigger is live and accessible to your external AI applications, turning this n8n template into an active service.

Lyft MCP Server (mcpTrigger): This is the central n8n trigger for the entire n8n workflow. It acts as the gateway for external AI agents, converting natural language requests into structured calls routed to the appropriate Lyft API tools within n8n.
Retrieve Cost Estimate (HTTP Request Tool): Calculates the estimated fare for a trip based on start and end points. This is a crucial public query n8n node.
Request New Ride (HTTP Request Tool): Initiates a new ride request, central to the operational capabilities of this n8n workflow.
Cancel Ride Request (HTTP Request Tool): Allows the AI agent to cancel a previously requested ride, providing full lifecycle management.
List Nearby Drivers (HTTP Request Tool): Retrieves real-time location data for available drivers near a given coordinate. This n8n node assists in pre-booking decisions.
List Ride Types (HTTP Request Tool): Fetches available ride options (e.g., standard, XL, luxury) at a location.
Retrieve User Profile (HTTP Request Tool): Accesses basic user information linked to the credential used by this n8n workflow.
Update Sandbox Ride Status & Set Sandbox Ride Types (HTTP Request Tool): These n8n nodes provide functionality crucial for developers to simulate different ride conditions and thoroughly test the n8n workflow integration without affecting production accounts. These are specific test features included in this comprehensive n8n template.