Vectorshift
for LuumenAI
Read your VectorShift pipelines and chatbots, run them as approved steps
Connect VectorShift with an API key and Luumen can see what you have built: pipelines, chatbots, knowledge bases, and transformations. Ask what a pipeline expects as input, or which chatbots point at a given knowledge base. When you want a pipeline run, one input or a batch, Luumen shows the inputs first and waits for your approval.
The Vectorshift toolbox
11 tools: 6 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ChatbotFetch an existing chatbot by its ID or name.
- ReadGet Knowledge BaseFetch an existing knowledge base by its ID or name.
- ReadGet PipelineFetch an existing pipeline by its ID or name.
- ReadList ChatbotsList all available chatbots in the account.
- ReadList PipelinesList all available pipelines in the VectorShift account.
- ReadList TransformationsList all available transformations in the account.
- WriteCreate ChatbotCreate a new chatbot. Approval by default
- WriteDelete ChatbotDelete a chatbot by its ID. Approval by default
- WriteRun PipelineRun a VectorShift pipeline with the given inputs. Approval by default
- WriteRun Pipeline in BulkRun a VectorShift pipeline in bulk with multiple sets of inputs. Approval by default
- WriteTerminate Pipeline ExecutionTerminate a running pipeline execution. Approval by default
One prompt, start to finish
What a governed Vectorshift run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create chatbot, delete chatbot, run pipeline, run pipeline in bulk, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Vectorshift — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Vectorshift to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.