Integration
Connect Yandex to Signatureapi
When New file fires in Yandex, your agent runs Add ceremony in Signatureapi. 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 Yandex and Signatureapi 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 Yandex can start in Signatureapi
When New file in Yandex
then Add ceremony in Signatureapi
When New file in Yandex
then Add deliverable in Signatureapi
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 Yandex and Signatureapi
Triggers and actions 1 trigger · 26 actions
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 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.
Action
Add ceremonyCreates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
Action
Add deliverableCreates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
Action
Add envelopeCreates an envelope with documents and recipients and starts the signing process.
Action
Add uploadUploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
Action
Cancel envelopeCancel an in-progress envelope so remaining recipients can no longer sign.
Action
Delete envelopeDelete an envelope.
Action
Get deliverableRetrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
Action
Get envelopeRetrieve a single envelope by id.
Action
Get recipientRetrieves a recipient's details, including status, ceremony information and completion timestamp.
Action
Get uploadFetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
Action
List deliverablesReturns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
Action
List envelopesLists envelopes in the account, most recent first, optionally filtered by status or topic.
Action
Resend requestResends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
Action
Update envelopeUpdate mutable fields (e.g. title, metadata) of an existing envelope.
Action
Update recipientReplaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
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 Yandex
Yandex to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Yandex to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Yandex to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Yandex to AnthropicAnthropic builds Claude, a family of large language models.
Yandex to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
Yandex to ElevenLabsElevenLabs is an AI audio research and deployment company.
More into Signatureapi
HubSpot to SignatureapiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SignatureapiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SignatureapiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SignatureapiGoogle Sheets
Gmail to SignatureapiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignatureapiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Yandex and Signatureapi, answered
What can start an automation from Yandex?
Any of Yandex's 1 trigger in the catalog, including New file. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Signatureapi when something happens in Yandex?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to Yandex?
Signatureapi has no triggers in the catalog today, so automations start in Yandex. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for Yandex or Signatureapi?
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 Yandex and Signatureapi 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.