Integration
Connect Keygen to SigningHub
When License Created fires in Keygen, 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 Keygen 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 Keygen can start in SigningHub
When License Created in Keygen
then Add Document 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 Keygen and SigningHub
Triggers and actions 13 triggers · 39 actions
- License Created
Fires when a license is created in Keygen.
- License Deleted
Triggers when a license is deleted.
- License Expired
Triggers when a license has expired.
- License Expiring
Triggers when a license is expiring soon.
- License Renewed
Triggers when a license is renewed.
- License Used
Triggers when a license's usage is incremented.
- Machine Activated
Triggers when a machine is activated.
- Machine Deactivated
Triggers when a machine is deactivated.
- New Event
Triggers when a new event like a license validation, an activation, or an expiration occurs.
- Password Reset
Triggers when a user requests a password reset.
- Release Created
Triggers when a new release is created.
- Release Published
Triggers when a release is published.
- User Created
Triggers when a new user is created.
- Activate Machine
Activates a new machine for a license using a known fingerprint.
- Add Release
creates a new release (version, channel, product relationship) for a product; fires the release.created webhook event.
- Checkout License
Checks out a license file.
- Checkout Machine
Checks out a machine file.
- Create License
Creates a new license according to a policy.
- Create Policy
Creates a license policy for a Keygen product.
- Create Product
Creates a product in Keygen.
- Create Release
/releases with version, channel and product relationship (status DRAFT): creates a draft release for a product, which Publish Release can then publish.
- Create Token
Creates a new API token for a license.
- Create User
Creates a new user.
- Deactivate Machine
deactivates (deletes) a machine, firing machine.deleted.
- Delete License
Permanently deletes a license.
- Find License
Finds an existing license by its license key or Keygen ID.
- Find User
Finds an existing user by their email address or Keygen ID.
- Get Token
Retrieves a single API token by its id, returning its kind, name, expiry and permissions.
- Increment License Usage
/v1/accounts/{account}/licenses/{id}/actions/increment-usage with optional body {"meta":{"increment":N}} — increments the license's uses count (fires license.usage.incremented).
- List Entitlements
Lists a license's entitlements by license key or license ID.
- List Policies
Lists the policies in the Keygen account.
- Publish Release
moves a draft release to PUBLISHED status; fires the release.published webhook event.
- Reinstate License
Reinstates a suspended license.
- Renew License
Renews a license by extending its expiration date.
- Request Password Reset
/v1/accounts/{account}/passwords with meta.email (and meta.deliver=false) — the Forgot Password call; issues a reset token for the user and fires the user.password-reset webhook event.
- Reset License Usage
Resets a license's usage counter.
- Suspend License
Suspends a license.
- Transfer License
Transfer an existing license to a different policy.
- Update License
Updates a license.
- Update Machine
Updates a machine.
- Update User
Updates a user.
- Add Digital Signature
Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
- Add Document
Uploads a document file into an existing SigningHub document package.
- Add Electronic Signature
Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
- Add Recipient to Workflow
Adds a signer or other recipient to a document package's workflow.
- Add User
Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
- Create Integration URL
Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
- Create Package
Creates a new document package in SigningHub to hold documents and recipients for a signing workflow.
- Download Package
Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
- Get Document Fields
Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
- Get Package
Returns the details of a SigningHub document package: its name, owner, status and the documents it contains.
- Share Document for Signing
Shares 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 Keygen
Keygen to Lexware OfficeLexware Office is a cloud app for german accounting.
Keygen to SendrSendr is a personalized outreach platform that helps sales teams enrich data, clean leads, and create...
Keygen to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Keygen to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Keygen to MailchimpMailchimp marketing automation and email platform.
Keygen to StripeStripe is a payment processing platform for online businesses.
More into SigningHub
HubSpot to SigningHubHubSpot is your all-in-one stop for all of your marketing software needs.
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
Keygen and SigningHub, answered
What can start an automation from Keygen?
Any of Keygen's 13 triggers in the catalog, including License Created, New Event, Release Created and User Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Keygen?
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 Keygen?
SigningHub has no triggers in the catalog today, so automations start in Keygen. 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 Keygen 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 Keygen 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.