Integration
Connect Globaledit to SigningHub
When New Collection fires in Globaledit, 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 Globaledit 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)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 Globaledit can start in SigningHub
When New Collection in Globaledit
then Add Document in SigningHub
When New Collection in Globaledit
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 Globaledit and SigningHub
Triggers and actions 1 trigger · 42 actions
Trigger
New CollectionTriggers when a new collection or project is created in an account.
Action
Add Asset CommentsAdds a comment, or a reply to a comment, on one or more assets.
Action
Add Assets to CollectionAdds assets to a collection.
Action
Add Folder CommentAdds a comment, or a reply to a comment, on a folder.
Action
Apply Tags to AssetsApplies tags to one or more assets.
Action
Create CollectionCreates a collection in an account.
Action
Create FolderCreates a folder in a workspace, optionally inside a parent folder.
Action
Create TagsCreates one or more asset tags in the organization.
Action
Create WorkspaceCreates a workspace in an account.
Action
Delete AssetsDeletes assets from a workspace.
Action
Delete CollectionDeletes a collection.
Action
Delete TagsDeletes organization asset tags.
Action
Get Asset MetadataReturns the metadata field values of one metadata schema for the given assets.
Action
Get Asset PreviewReturns a temporary download link to an asset's preview image at the chosen size.
Action
Get Asset SummaryReturns an asset's summary: name, type, size, folder path, versions and properties.
Action
Get Collection AssetsReturns the assets in a collection.
Action
Get Collection SummaryReturns a collection's details by ID.
Action
Get Folder AssetsReturns the assets in a folder.
Action
Get FoldersReturns every folder and subfolder in a workspace.
Action
Get User InfoReturns the profile of the user the API key acts as, including the organizations it belongs to.
Action
Get WorkspacesReturns the accounts and workspaces the user can see in an organization.
Action
List CollectionsReturns the collections and projects the user can access in an account.
Action
List Organization UsersReturns the users in an organization.
Action
List TagsReturns every asset tag defined in the organization.
Action
Remove Assets from CollectionRemoves assets from a collection.
Action
Remove Tags from AssetsRemoves tags from one or more assets.
Action
Rename FolderRenames a folder in a workspace.
Action
Update Asset NameRenames an asset.
Action
Update CollectionUpdates a collection's name and description.
Action
Update MetadataSets metadata field values on one or more assets.
Action
Update RatingSets a rating (stars, color, status or a yes/no rating) on one or more assets.
Action
Update TagRenames an organization asset tag.
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 Globaledit
Globaledit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Globaledit to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Globaledit to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Globaledit to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Globaledit to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Globaledit 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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
Globaledit and SigningHub, answered
What can start an automation from Globaledit?
Any of Globaledit's 1 trigger in the catalog, including New Collection. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Globaledit?
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 Globaledit?
SigningHub has no triggers in the catalog today, so automations start in Globaledit. 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 Globaledit 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 Globaledit 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.