Integration
Connect Cursion to SigningHub
When New Flow fires in Cursion, 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 Cursion 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 Cursion can start in SigningHub
When New Flow in Cursion
then Add Document in SigningHub
When New Page in Cursion
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 Cursion and SigningHub
Triggers and actions 5 triggers · 28 actions
Trigger
New FlowTriggers when a new Flow is created in your Cursion account.
Trigger
New PageTriggers when a new page is added to a Cursion site.
Trigger
New ScanTriggers when a new Scan is created for the selected Cursion page.
Trigger
New SiteTriggers when a new site is added to your Cursion account.
Trigger
New TestTriggers when a new Test (a comparison of two scans) is created for a page.
Action
Add caseGenerates a new test case for a site from a plain-language prompt and returns the process tracking its creation.
Action
Add flowCreates a Flow in Cursion — a named sequence of steps (scans, cases, alerts) that FlowRuns execute.
Action
Create CaseRunRuns a saved Case against a Site, creating a CaseRun that executes in the background and returns immediately.
Action
Create FlowRunRuns a Flow against a Site and returns the new FlowRun, which completes asynchronously.
Action
Create PageCreates a Page under a Cursion Site and, unless skipped, starts its initial baseline Scan.
Action
Create ScanStarts a new Scan of a Site's pages in Cursion. The scan runs in the background and may take several minutes to complete.
Action
Create SiteCreates a Site in Cursion for a domain, then crawls it for pages and runs initial baseline scans in the background.
Action
Delete siteDeletes a site and, with it, all of the site's scans, tests, schedules and alerts.
Action
Get FlowRunReturns a single FlowRun — the result of running a Flow against a Site — including its nodes, status and logs.
Action
Get scanReturns a single Cursion scan with its HTML, logs, Lighthouse and security scores, and screenshots.
Action
Get siteReturns a single Cursion site with its URL, tags, crawl times and latest scan and test summary.
Action
Get testReturns a single Test, the comparison of two scans of a page, with its scores, status and deltas.
Action
List flowsReturns the flows in your Cursion account, including each flow's steps (nodes) and connections (edges).
Action
List pagesReturns the pages that belong to a Cursion site, with each page's URL, tags and latest scan and test results.
Action
List scansReturns the scans captured for a Cursion page, ordered by creation time.
Action
List sitesReturns the sites in your Cursion account, newest first, with each site's URL, tags and latest scan and test details.
Action
List testsReturns the Tests run against a Cursion Page, ordered by creation time.
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 Cursion
Cursion to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cursion to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cursion to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cursion to Google SheetsGoogle Sheets
Cursion to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cursion 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
Cursion and SigningHub, answered
What can start an automation from Cursion?
Any of Cursion's 5 triggers in the catalog, including New Flow, New Page, New Scan and New Site. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Cursion?
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 Cursion?
SigningHub has no triggers in the catalog today, so automations start in Cursion. 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 Cursion 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 Cursion 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.