Integration
Connect Crowdin to SigningHub
When Comment/Issue Added fires in Crowdin, your agent runs Add Document in SigningHub. 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 Crowdin and SigningHub 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 Crowdin can start in SigningHub
When Comment/Issue Added in Crowdin
then Add Document in SigningHub
When Comment/Issue Updated in Crowdin
then Add User in SigningHub
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 Crowdin and SigningHub
Triggers and actions 12 triggers · 40 actions
Trigger
Comment/Issue AddedTriggers when a user creates a comment or an issue.
Trigger
Comment/Issue DeletedTriggers when a user deletes a comment or an issue.
Trigger
Comment/Issue UpdatedTriggers when a user updates a comment or an issue.
Trigger
File AddedTriggers when a new file has been added to the project.
Trigger
File ApprovedTriggers when a file is fully translated and approved.
Trigger
File DeletedTriggers when a file has been deleted from the project.
Trigger
File RevertedTriggers when a file update has been reverted.
Trigger
File TranslatedTriggers when a file is fully translated.
Trigger
File UpdatedTriggers when a file has been updated.
Trigger
New DirectoryTriggers when a new directory is created in a Crowdin project.
Trigger
New LabelTriggers when a new label is added to a Crowdin project.
Trigger
New ProjectTriggers when a new project is created in Crowdin.
Action
Add ApprovalApproves a translation (or a source-string correction) in a Crowdin project.
Action
Add TranslationAdds a translation in a target language to a source string in a Crowdin project, or uploads a translated asset file.
Action
Create CommentAdds a comment or issue to a string or asset file in a Crowdin project.
Action
Create DirectoryCreates a directory in a Crowdin project, optionally inside a branch or parent directory.
Action
Create LabelCreates a new label in a Crowdin project, which can then be assigned to strings or screenshots.
Action
Create or Update a FileUploads a source file to a Crowdin project, adding it as a new file or, when an existing file ID is given, replacing that file's content.
Action
Create ProjectCreates a new translation project in Crowdin with the chosen source and target languages and project settings.
Action
Create StringCreates a source string for translation in a file of a Crowdin project.
Action
Create TaskCreates a translation or proofreading task in a Crowdin project for chosen files, directories, branches or strings.
Action
Delete CommentDeletes a string or asset comment or issue from a Crowdin project.
Action
Delete FileDeletes a source file from a Crowdin project.
Action
Download Translated FileBuilds the translated version of a project file for one target language and returns a temporary download link for it.
Action
Find DirectoryFinds directories in a Crowdin project by name.
Action
Find FileFinds source files in a Crowdin project whose name matches the text you give, optionally limited to a branch or directory.
Action
Find LabelFinds labels in a Crowdin project whose title matches the title you supply.
Action
Find LanguageFinds a Crowdin language by its name or language code (for example "Spanish" or "es") and returns its codes and details.
Action
Find ProjectFinds Crowdin projects whose name matches the text you supply, returning the first match and the full list.
Action
Find StringFinds source strings in a Crowdin project by text, identifier or context, returning the first match and the full list.
Action
Find TaskFinds a task in a Crowdin project by its title, optionally narrowed by status or batch, and returns the first match.
Action
Get CommentReturns a single string or asset comment (or issue) in a Crowdin project, including its text, author, issue status and attachments.
Action
Get ScreenshotReturns a screenshot from a Crowdin project, including its name, image link, size, tags and labels.
Action
Get TranslationReturns a single translation of a string or asset in a Crowdin project, including its text, author, rating and provider.
Action
Label StringAssigns a label to one or more strings in a Crowdin project and returns the updated strings.
Action
List ApprovalsReturns the approvals on translations in a Crowdin project, filtered by translation, correction or language.
Action
Remove Label From StringRemoves a label from one or more strings in a Crowdin project and returns the updated strings.
Action
Resolve IssueMarks an issue reported on a Crowdin string or asset as resolved and returns the updated issue.
Action
Restore File RevisionRestores a Crowdin source file to one of its previous revisions and returns the restored file.
Action
Translation ProgressReturns the translation and approval progress of a Crowdin project for each of its target languages.
Action
Upload ScreenshotUploads an image and adds it as a screenshot to a Crowdin project, optionally auto-tagging strings and attaching labels.
Action
Add Digital SignatureAdds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
Action
Add DocumentUploads a document file into an existing SigningHub document package.
Action
Add Electronic SignatureAdds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
Action
Add Recipient to WorkflowAdds a signer or other recipient to a document package's workflow.
Action
Add UserRegisters a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
Action
Create Integration URLGenerates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
Action
Create PackageCreates a new document package in SigningHub to hold documents and recipients for a signing workflow.
Action
Download PackageDownloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
Action
Get Document FieldsReturns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
Action
Get PackageReturns the details of a SigningHub document package: its name, owner, status and the documents it contains.
Action
Share Document for SigningShares a prepared document package with its signers and starts the signing workflow.
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 Crowdin
Crowdin to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Crowdin to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Crowdin to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Crowdin to Google SheetsGoogle Sheets
Crowdin to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Crowdin to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into SigningHub
HubSpot to SigningHubHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SigningHubSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SigningHubSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SigningHubGoogle Sheets
Gmail to SigningHubGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SigningHubGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Crowdin and SigningHub, answered
What can start an automation from Crowdin?
Any of Crowdin's 12 triggers in the catalog, including Comment/Issue Added, Comment/Issue Updated, File Added and File Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Crowdin?
Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SigningHub to Crowdin?
SigningHub has no triggers in the catalog today, so automations start in Crowdin. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it.
Do I have to build a connector for Crowdin or SigningHub?
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 Crowdin and SigningHub 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.