Integration
Connect Onepay to SigningHub
When New Customer fires in Onepay, 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 Onepay 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 Onepay can start in SigningHub
When New Customer in Onepay
then Add Document in SigningHub
When New Customer in Onepay
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 Onepay and SigningHub
Triggers and actions 1 trigger · 30 actions
Trigger
New CustomerTriggers when a new customer is added to your Onepay app.
Action
Create Customer Card RequestCreates an Onepay customer (or reuses an existing one by Customer ID) and returns a secure link where they enter a card to save.
Action
Create ItemCreates a product or service line item you can attach to Onepay payments.
Action
Delete Customer CardPermanently deactivates a customer's saved card so it can no longer be charged.
Action
Delete ItemPermanently deletes an Onepay item that is not used by completed transactions.
Action
Delete Payment LinkDeactivates a payment link that has no successful payments.
Action
Get CustomerReturns a customer with their saved cards and transaction history.
Action
Get Customer CardReturns one of a customer's saved cards.
Action
Get Payment LinkReturns a payment link, including whether the customer has paid it.
Action
Get Payout TransactionReturns the settlement breakdown of a transaction: amount, commission, net payout and settlement date.
Action
Get Transaction StatusReturns whether an Onepay transaction was paid, with its amount and payment time.
Action
List Customer CardsReturns a customer's saved card tokens.
Action
List CustomersReturns all customers saved in your Onepay app.
Action
List Customer TransactionsReturns a customer's charge history, newest first.
Action
List ItemsReturns all items created under your Onepay App ID.
Action
List Payout TransactionsReturns settlement transactions in a date range, one page at a time.
Action
Make PaymentCharges a customer's saved card for any amount, with no action needed from the customer.
Action
Refund TransactionStarts a full or partial refund of a paid live Onepay transaction.
Action
Update ItemUpdates the fields you supply on an existing Onepay item; others keep their values.
Action
Update Payment Link DescriptionChanges the description of a payment link (the only field Onepay lets you change after creation).
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 Onepay
Onepay to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Onepay to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Onepay to StripeStripe is a payment processing platform for online businesses.
Onepay to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Onepay to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Onepay to PipedrivePipedrive is a sales CRM and pipeline management tool.
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
Onepay and SigningHub, answered
What can start an automation from Onepay?
Any of Onepay's 1 trigger in the catalog, including New Customer. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Onepay?
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 Onepay?
SigningHub has no triggers in the catalog today, so automations start in Onepay. 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 Onepay 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 Onepay 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.