Integration
Connect Kit and Modusign
When New Form Subscriber fires in Kit, your agent runs Add document request in Modusign, or Document Updated in Modusign to Add Subscriber to Form in Kit. 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 Kit and Modusign to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Kit and Modusign can do together
From Kit to Modusign
When New Form Subscriber in Kit
then Add document request in Modusign
From Modusign to Kit
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 Kit and Modusign
Triggers and actions 8 triggers · 16 actions
- New Form Subscriber
Triggers when a subscription occurs on a specific form.
- New Purchase
Triggers when a new purchase is added to your account.
- New Sequence Subscriber
Triggers when a subscriber is added to a sequence.
- New Subscriber
Triggers when a new subscriber is confirmed within your account (has completed any applicable double opt-ins).
- New Unsubscribe
Triggers when a subscriber unsubscribes from your emails.
- Subscriber Added to Tag
Triggers when a specific tag is added to a subscriber.
- Tag Removed From Subscriber
Triggers when a specific tag is removed from a subscriber.
- Add Subscriber to Form
Subscribe someone to a specific form.
- Add Tag to Subscriber
Add a subscriber to a specific tag.
- Find Subscriber
Finds an existing confirmed subscriber by email.
- Remove Tag From Subscriber
Remove a specific tag from a subscriber if they have it.
- Document Updated
Triggers when a document is created, signed, completed, or aborted.
- Add document request
Request signatures on a document (signature request).
- Add label
Creates a new label in Modusign.
- Cancel document request
Cancel a pending signature request.
- Delete label
Delete a label.
- Delete template
Delete a template.
- Get Document
Retrieves the details of a single Modusign document by its ID.
- Get template
Get a template by id.
- Get user
Gets the Modusign user whose credentials the connection uses.
- Remind Signing
Resend signing request notifications to signers who did not sign.
- Request Document With Template
Create a document using a template and request signers to sign it.
- Search Documents
Search for documents with specific conditions.
- Update label
Update a label.
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 Kit
Kit to API SnapFree utility API platform. QR codes, screenshots, PDFs, image resize, hashing, and more
Kit to ClerkClerk is a user authentication and management platform that lets developers add sign-in, profiles, and...
Kit to PostLakeOne API to publish, schedule, and read analytics across every major social network
Kit to SynchroteamSynchroteam is a Cloud-based Field Service Management application
Kit to WikimediaThis API provides cacheable and straightforward access to Wikimedia content and data, in machine-readable...
Kit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into Modusign
Google Sheets to ModusignGoogle Sheets
Gmail to ModusignGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ModusignGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ModusignGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ModusignMailchimp marketing automation and email platform.
Questions
Kit and Modusign, answered
What can start an automation from Kit?
Any of Kit's 7 triggers in the catalog, including New Form Subscriber, New Purchase, New Sequence Subscriber and New Subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Modusign when something happens in Kit?
Any of Modusign's 12 actions, including Update label, Add document request, Add label and Get Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Modusign to Kit?
Yes. When something happens in Modusign, your agent can act in Kit too. This page covers both directions: Modusign's triggers and Kit's actions are listed here as well.
Do I have to build a connector for Kit or Modusign?
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.
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.