Build solutions, not workarounds.
What do you want Frihet and Qstash to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Frihet can start in Qstash
When New Expense in Frihet
then Add queue 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 Frihet and Qstash
Triggers and actions 1 trigger · 57 actions
- New Expense
Fires when a new expense is created. Backed by vendor webhook registration.
- Add Client
Create a client.
- Add Deposit
Create a deposit.
- Add Expense
Create an expense.
- Add Invoice
Create an invoice.
- Add Product
Create a product.
- Add Quote
Create a quote.
- Add Vendor
Create a vendor.
- Apply deposit to invoice
Apply a deposit balance to an invoice.
- Delete Client
Delete a client.
- Delete Expense
Delete an expense.
- Delete Invoice
Delete an invoice.
- Delete Product
Delete a product.
- Delete Quote
Delete a quote.
- Delete Vendor
Delete a vendor.
- Get Client
Retrieve a client by id.
- Get Deposit
Retrieve a deposit by id.
- Get Expense
Retrieve an expense by id.
- Get Invoice
Retrieve an invoice by id.
- Get Product
Retrieve a product by id.
- Get Quote
Retrieve a quote by id.
- Get Vendor
Retrieve a vendor by id.
- List Clients
List clients.
- List Deposits
List deposits.
- List Expenses
List expenses.
- List Invoices
List invoices.
- List Products
List products.
- List Quotes
List quotes.
- List Vendors
List vendors.
- Mark invoice as paid
Mark an invoice as paid.
- Send Invoice
Send invoice by email to the client.
- Send Quote
Send quote by email to the client.
- Update Client
Partial update a client.
- Update Expense
Partial update an expense.
- Update Invoice
Partial update an invoice.
- Update Product
Partial update a product.
- Update Quote
Partial update a quote.
- Update Vendor
Partial update a vendor.
- 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 Frihet
Frihet to PredictHQEvents and natural disasters data
Frihet to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Frihet to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Frihet to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Frihet to Google SheetsGoogle Sheets
Frihet to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Qstash
Google Calendar to QstashGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Frihet and Qstash, answered
What can start an automation from Frihet?
Any of Frihet's 1 trigger in the catalog, including New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qstash when something happens in Frihet?
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 Frihet?
Qstash has no triggers in the catalog today, so automations start in Frihet. 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 Frihet 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.
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.