How does Lyro handle a pipeline run that takes a while to finish?

Run Pipeline returns either the result or a run_id for asynchronous execution, so a long job does not block the conversation. Terminate Pipeline Execution stops that run by the same run_id if the inputs turn out to be wrong.

Can Lyro add documents to a VectorShift knowledge base?

No. The knowledge base actions here are reads: List Knowledge Bases and Get Knowledge Base return configuration and metadata. Uploading or indexing content still happens inside VectorShift, and Lyro can confirm which knowledge base a pipeline is pointed at but not change what is in it.

What has to exist before Lyro can create a chatbot?

A pipeline. Chatbots in VectorShift are conversational interfaces built on pipelines, so Lyro resolves the pipeline first with List Pipelines or Get Pipeline and then passes it to Create Chatbot rather than creating a bot with nothing behind it.

Can a deleted chatbot be recovered?

No. Delete Chatbot permanently removes the chatbot from the account by ID and nothing in the toolkit restores it. Calling Get Chatbot first captures the configuration and metadata, which is worth doing before a deletion anyone might want to reverse.

Vectorshift MCP integration

Runs pipelines singly or in bulk, stops an execution by run ID, and creates, inspects, or removes the chatbots built on top of them.

Connect Vectorshift See all integrations

12actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create chatbot
Lyro spins up a new chatbot in VectorShift with custom logic and knowledge. Your team deploys AI-powered conversations without writing backend code.
Run pipeline
Lyro executes a VectorShift pipeline with your inputs to transform or enrich customer data. Your team automates complex workflows inside every support conversation.
List chatbots
Lyro retrieves all available chatbots in your account so you can pick the right one for the job. Your team discovers and reuses existing agents without searching your dashboard.

See all 12 actions

How businesses use Vectorshift + Lyro

Each card is one request a support team gets, and the Vectorshift actions Lyro runs to close it.

Run a pipeline and stay in control of it
Lyro executes a pipeline with the inputs supplied, batches multiple input sets into one bulk run, and terminates an execution by its run ID when it should not finish.
Run PipelineRun Pipeline in BulkTerminate Pipeline Execution
Manage the chatbots deployed on an account
Lyro creates a chatbot on top of an existing pipeline, retrieves one by ID or name to read its configuration, lists what is deployed, and removes a bot that is no longer used.
Create ChatbotGet ChatbotList ChatbotsDelete Chatbot
See what an account has to work with
Lyro lists the pipelines and transformations available and opens a specific pipeline by ID or name, so the right building block is identified before anything is run or built on it.
List PipelinesGet PipelineList Transformations
Check which knowledge base a build should point at
Lyro lists the knowledge bases on the account and fetches one by ID or name with its configuration and metadata, confirming the source a pipeline or chatbot draws on.
List Knowledge BasesGet Knowledge Base

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Vectorshift actions it has and picks the ones a request needs.

01
Connect Vectorshift
Authorize the Vectorshift account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Vectorshift actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Vectorshift · Lyro

Everything else about Vectorshift

Setup, permissions, and the limits of what Lyro can do inside Vectorshift.

Run Pipeline returns either the result or a run_id for asynchronous execution, so a long job does not block the conversation. Terminate Pipeline Execution stops that run by the same run_id if the inputs turn out to be wrong.

Every action available in Vectorshift

All 12 actions your agent can call on Vectorshift, straight from the live MCP connection.

Create chatbot
Create a new chatbot.
Delete chatbot
Delete a chatbot by its ID.
Get chatbot
Fetch an existing chatbot by its ID or name.
Get knowledge base
Fetch an existing knowledge base by its ID or name.
Get pipeline
Fetch an existing pipeline by its ID or name.
List chatbots
List all available chatbots in the account.
List knowledge bases
List all available knowledge bases in your VectorShift account.
List pipelines
List all available pipelines in the VectorShift account.
List transformations
List all available transformations in the account.
Run pipeline
Run a VectorShift pipeline with the given inputs.
Run pipeline in bulk
Run a VectorShift pipeline in bulk with multiple sets of inputs.
Terminate pipeline execution
Terminate a running pipeline execution.