Integration
Connect Dastra to Qstash
When New Task fires in Dastra, your agent runs Batch publish messages in Qstash. 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 Qstash 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 Qstash
When New Task in Dastra
then Batch publish messages in Qstash
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 Qstash
Triggers and actions 1 trigger · 37 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 queue
Create or update a queue (upsert), setting parallelism.
- Add schedule
Create a cron-based schedule that periodically publishes a message to a destination.
- Add URL group endpoint
Create a URL group or add/update an endpoint within it (fan-out publishing target).
- Batch publish messages
Publish multiple messages to multiple destinations in one call.
- Delete DLQ message
Remove a message from the dead-letter queue.
- Delete message
Cancel a message that has not yet been delivered.
- Delete queue
Delete a queue by name.
- Delete schedule
Delete a schedule by id.
- Delete URL group
Deletes a QStash URL group and all its endpoints. In-flight messages are not removed.
- Enqueue message
Add a message to a named queue for sequential delivery.
- Get DLQ message
Retrieve a single dead-letter queue message by id.
- Get message
Retrieve a queued/published message by id.
- Get queue
Retrieve a queue's configuration and stats by name.
- Get schedule
Retrieve a schedule by id.
- Get URL group
Retrieve a URL group and its endpoints by name.
- List DLQ messages
List messages that failed delivery and landed in the dead-letter queue.
- List queues
List all queues for the account.
- Publish message
Publish a single message to a URL or URL group for QStash to deliver.
- Retry DLQ message
Re-attempt delivery of a dead-lettered message now.
- Update schedule
Updates an existing QStash schedule by replacing its settings (destination, cron, message and delivery options).
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 Qstash
Questions
Dastra and Qstash, 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 Qstash when something happens in Dastra?
Any of Qstash's 20 actions, including Update schedule, Add queue, Add schedule and Add URL group endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qstash to Dastra?
Qstash has no triggers in the catalog today, so automations start in Dastra. If you need the other direction, ask: your agent reads Qstash's API documentation and adds it.
Do I have to build a connector for Dastra or Qstash?
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 Qstash 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.