Integration
Connect CallMaker to SigningHub
When Booking Created fires in CallMaker, 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 CallMaker 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 CallMaker can start in SigningHub
When Booking Created in CallMaker
then Add Document in SigningHub
When Number Change Created in CallMaker
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 CallMaker and SigningHub
Triggers and actions 15 triggers · 21 actions
Trigger
Booking CancelledFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled bookings.
Trigger
Booking ConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed bookings.
Trigger
Booking CreatedTriggers when a new booking is created.
Trigger
Booking RestoredFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored bookings.
Trigger
Booking UnConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed bookings.
Trigger
Meeting AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (true) to act only on accomplished meetings.
Trigger
Meeting Not AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (false) to act only on meetings that did not take place.
Trigger
Meeting Not SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (false) to act only on unsuccessful meetings.
Trigger
Meeting SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (true) to act only on successful meetings.
Trigger
Number Change CreatedTriggers when a new number change (a processed customer card) is recorded; returns its ID.
Trigger
Order CancelledFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled orders.
Trigger
Order ConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed orders.
Trigger
Order CreatedTriggers when a new order is created.
Trigger
Order RestoredFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored orders.
Trigger
Order UnConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed orders.
Action
Confirm Order by Order IdConfirms an order and returns the updated order.
Action
Create Customer CardCreates a customer card in a Callmaker project and list, with the field values you supply.
Action
Edit Customer CardUpdates field values on an existing Callmaker customer card.
Action
Edit Order Status by Order IdChanges the status of an order.
Action
Find Booking by Booking IdReturns one Callmaker booking (meeting) by its booking ID, including its customer card, user, times and confirmation state.
Action
Find Descendants Workflows by Workflow IdReturns the IDs of all workflows beneath a workflow.
Action
Find Number by Number IdReturns a number (customer record) by its ID.
Action
Find Order by Order IdReturns an order by its ID.
Action
Find Resource by Resource IdReturns a resource by its ID.
Action
Find User by User IdReturns a user by their ID.
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 CallMaker
CallMaker to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CallMaker to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CallMaker to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CallMaker to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CallMaker to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CallMaker 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
CallMaker and SigningHub, answered
What can start an automation from CallMaker?
Any of CallMaker's 15 triggers in the catalog, including Booking Created, Number Change Created, Order Created and Booking Confirmed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in CallMaker?
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 CallMaker?
SigningHub has no triggers in the catalog today, so automations start in CallMaker. 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 CallMaker 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 CallMaker 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.