Integration
Connect Dastra to Qdrant
When New Task fires in Dastra, your agent runs Add collection in Qdrant. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Dastra and Qdrant to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Dastra can start in Qdrant
When New Task in Dastra
then Add collection in Qdrant
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Dastra and Qdrant
Triggers and actions 1 trigger · 32 actions
- New Task
Triggers when a new task is created in the chosen Dastra workspace.
- Add asset
Creates an asset (software, building, network, data store and so on) in a Dastra workspace and returns the new asset record.
- Add data processing
Creates a new data processing activity in your Dastra record of processing activities, in the organizational unit you choose.
- Attach an Actor to a Data Processing
Links one or more actors (vendors, internal services, third parties, data controllers) to a data processing activity in your Dastra register, as recipients, data controllers, stakeholders or referents.
- Create an Actor
Creates an actor (a vendor, partner, processor or other third party) in a Dastra workspace and returns the new actor record.
- Create a Task
Creates a task in a Dastra workspace, with its priority, dates, assignee, project and links to other Dastra records.
- Delete actor
Deletes an actor (a controller, processor or other third party) from a Dastra workspace.
- Delete task
Deletes a task from a Dastra workspace.
- Get actor
Returns one actor (vendor, processor, controller or other third party) from a Dastra workspace by its id, including its contact details, tags, contracts and custom field values.
- Get data processing
Returns a data processing activity from your Dastra register of processing activities, including its purposes, recipients, data subject rights and custom fields.
- Get task
Returns a single Dastra task by its id, including its state, priority, deadline, assignee and custom field values.
- List assets
Returns the assets (software, buildings, networks, data stores and other resources) in a Dastra workspace, optionally filtered by type, state, owner, tag, organizational unit or a search text.
- List tasks
Returns the tasks in a Dastra workspace, optionally filtered by state, priority, assignee, project, linked object, dates or search text.
- Search Actor
Returns the actors (vendors, data controllers, third parties and other organizations or people) in a Dastra workspace that match the search text and filters.
- Search Data Processing
Searches the data processing activities in a Dastra workspace by text and optional filters, returning every matching activity with its full record.
- Update actor
Updates an existing actor (vendor, partner or person) in a Dastra workspace. Fields you leave blank keep their current values.
- Update data processing
Updates an existing data processing activity in a Dastra workspace, changing only the fields you fill in, and returns the updated record.
- Update task
Updates an existing Dastra task. Fields you leave blank keep their current values.
- Add collection
Creates a new Qdrant collection with the given name and vector configuration.
- Add payload index
Creates a payload index on a field of a Qdrant collection so that filters on that field run fast.
- Add points
Adds points (vectors with optional payloads) to a Qdrant collection, overwriting any existing point with the same id.
- Add snapshot
Creates a new snapshot of a Qdrant collection and returns the snapshot's name, size and checksum.
- Count points
Returns the number of points in a Qdrant collection, optionally only those matching a payload filter.
- Delete collection
Deletes a Qdrant collection and all of the points and data stored in it.
- Delete points
Deletes points from a Qdrant collection, either by a list of point ids or by every point matching a filter.
- Find points by vector
Returns the points in a collection whose vectors are closest to the vector you supply, ranked by similarity score, with their payloads.
- Get collection
Returns the details of a Qdrant collection: its status, point and vector counts, segment count, configuration and payload index schema.
- Get point
Returns a single point from a Qdrant collection, including its payload and vector.
- List collections
Returns the names of all collections in your Qdrant cluster.
- List points
Returns the points stored in a Qdrant collection, optionally narrowed by a payload filter and ordered by a payload field.
- List snapshots
Returns every snapshot stored for a Qdrant collection, with each snapshot's file name, creation time, size and checksum.
- Update collection
Updates the settings of an existing Qdrant collection, such as its vector, index, optimizer, quantization, strict-mode or metadata parameters.
- Update point payload
Sets payload values on points in a Qdrant collection, chosen by point ids or a filter. Keys you supply are added or overwritten; other existing payload keys are kept.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Dastra
Dastra to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dastra to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dastra to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dastra to Google SheetsGoogle Sheets
Dastra to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Dastra to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Qdrant
Questions
Dastra and Qdrant, answered
What can start an automation from Dastra?
Any of Dastra's 1 trigger in the catalog, including New Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qdrant when something happens in Dastra?
Any of Qdrant's 15 actions, including Update collection, Update point payload, Add collection and Add payload index. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qdrant to Dastra?
Qdrant has no triggers in the catalog today, so automations start in Dastra. If you need the other direction, ask: your agent reads Qdrant's API documentation and adds it.
Do I have to build a connector for Dastra or Qdrant?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Dastra and Qdrant without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.