Integration
Connect Rotessa and Yandex
When New Customer fires in Rotessa, your agent runs Add folder in Yandex, or New file in Yandex to Create Customer in Rotessa. 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 Rotessa and Yandex 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Rotessa and Yandex can do together
From Rotessa to Yandex
When New Customer in Rotessa
then Add folder in Yandex
When Customer Change in Rotessa
then Update resource in Yandex
From Yandex to Rotessa
When New file in Yandex
then Create Customer in Rotessa
When New file in Yandex
then Update Customer in Rotessa
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 Rotessa and Yandex
Triggers and actions 5 triggers · 23 actions
Trigger
Customer ChangeTriggers when a Rotessa customer is added or updated.
Trigger
Declined TransactionTriggers when a Rotessa payment is declined.
Trigger
New CustomerTriggers when a new customer is added in Rotessa.
Trigger
Transaction ApprovedTriggers when a Rotessa payment is approved.
Action
Create CustomerCreates a new customer in Rotessa with their bank details.
Action
Create TransactionCreates a one-time or recurring payment (transaction schedule) for a Rotessa customer.
Action
Create Transaction Schedule by Custom IdentifierCreates a one-time or recurring payment for the customer identified by your custom identifier.
Action
Delete Transaction ScheduleDeletes a transaction schedule so no further payments are processed.
Action
Get CustomerReturns one Rotessa customer by ID, including bank details, address and schedules.
Action
Get Transaction ScheduleReturns one transaction schedule and its payments.
Action
List CustomersReturns all customers in your Rotessa account.
Action
List TransactionsReturns payments processed in a date range, optionally filtered by status (Pending, Approved, Declined, Chargeback).
Action
Match a CustomerFinds the Rotessa customer that carries your custom identifier.
Action
Update CustomerUpdates an existing Rotessa customer's contact or bank details.
Action
Update Transaction ScheduleChanges the amount or comment of an existing transaction schedule.
Trigger
New fileTriggers when a new file is uploaded to Yandex Disk.
Action
Add folderCreates a new empty folder at the given path on Yandex Disk. The parent folder must already exist.
Action
Copy resourceCopies a file or folder on Yandex Disk to a new location and returns a link to the copy, or to the copy operation when Yandex performs it in the background.
Action
Delete resourceDeletes a file or folder on Yandex Disk, moving it to the Trash by default or removing it permanently.
Action
Get disk infoReturns general information about the connected user's Yandex Disk: total, used and trash space, file size limits, system folder paths and the disk owner.
Action
Get download linkReturns a temporary direct link for downloading a file stored on Yandex Disk.
Action
Get resourceReturns the details of a file or folder on Yandex Disk, such as its name, type, size, dates and custom properties. For a folder, the response also lists the items inside it.
Action
List filesReturns a flat list of every file on the user's Yandex Disk, optionally filtered by media type and sorted.
Action
List public resourcesReturns the files and folders on your Yandex Disk that have been published with a public link.
Action
List recently uploaded filesReturns the files most recently uploaded to Yandex Disk, newest first, optionally filtered by media type.
Action
Move resourceMoves or renames a file or folder on Yandex Disk. Returns a link to the moved item, or to the background move operation when it runs asynchronously.
Action
Publish resourcePublishes a file or folder on Yandex Disk so it gets a public link, optionally with access settings such as a password or expiry. Returns a link to the published resource's metadata.
Action
Update resourceAdds or changes custom properties on a file or folder in Yandex Disk. Properties with the same name are overwritten, new ones are added, and a property set to null is removed.
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 Rotessa
Rotessa to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Rotessa to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Rotessa to StripeStripe is a payment processing platform for online businesses.
Rotessa to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Rotessa to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Rotessa to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Yandex
HubSpot to YandexHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to YandexSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to YandexSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to YandexGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to YandexGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to YandexGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Rotessa and Yandex, answered
What can start an automation from Rotessa?
Any of Rotessa's 4 triggers in the catalog, including New Customer, Customer Change, Declined Transaction and Transaction Approved. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Yandex when something happens in Rotessa?
Any of Yandex's 12 actions, including Update resource, Add folder, Copy resource and Get disk info. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Yandex to Rotessa?
Yes. When something happens in Yandex, your agent can act in Rotessa too. This page covers both directions: Yandex's triggers and Rotessa's actions are listed here as well.
Do I have to build a connector for Rotessa or Yandex?
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 Rotessa and Yandex 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.