Integration
Connect Modusign and MRPLN
When Document Updated fires in Modusign, your agent runs Create Customer in MRPLN, or Customer Updated (instant) in MRPLN to Add document request in Modusign. 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 Modusign and MRPLN 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 Modusign and MRPLN can do together
From Modusign to MRPLN
When Document Updated in Modusign
then Create Customer in MRPLN
From MRPLN to Modusign
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 Modusign and MRPLN
Triggers and actions 7 triggers · 20 actions
- 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.
- Campaign Launched (instant)
Fires instantly when a campaign is launched (campaign.launched).
- Customer Opted Out (instant)
Fires instantly when a customer opts out (customer.opted_out).
- Customer Updated (instant)
Triggers instantly when a customer is updated in MRPLN.
- Message Sent (instant)
Fires instantly when a message is queued or scheduled for a customer (message.sent).
- New Customer
Triggers when a new customer is added.
- New Customer (instant)
Triggers instantly when a customer is created in MRPLN.
- Create Customer
Creates a new customer in MRPLN.
- Find Customer
Finds a customer by email address. Returns the first matching customer, or found=false when none match.
- Find Customer by Phone
Find a customer by their SMS phone number.
- Find Customer by WhatsApp
Find a customer by their WhatsApp number.
- List Templates
List the approved message templates for a channel.
- Send Message to Customer
Send an email, SMS, or WhatsApp message to a customer using an approved template
- Trigger Campaign
Launch a campaign that was built in MRPLN.
- Update Customer
Updates an existing customer in MRPLN.
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 Modusign
Modusign to timeBuzzertimeBuzzer is a simple time tracker and timesheet app to track hours worked across projects in real time.
Modusign to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Modusign to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Modusign to StripeStripe is a payment processing platform for online businesses.
Modusign to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Modusign to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into MRPLN
HubSpot to MRPLNHubSpot is your all-in-one stop for all of your marketing software needs.
Ontraport to MRPLNOntraport is an all-in-one CRM, marketing automation, and e-commerce platform.
Google Sheets to MRPLNGoogle Sheets
Gmail to MRPLNGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Modusign and MRPLN, answered
What can start an automation from Modusign?
Any of Modusign's 1 trigger in the catalog, including Document Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in MRPLN when something happens in Modusign?
Any of MRPLN's 8 actions, including Create Customer, Send Message to Customer, Update Customer and Find Customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from MRPLN to Modusign?
Yes. When something happens in MRPLN, your agent can act in Modusign too. This page covers both directions: MRPLN's triggers and Modusign's actions are listed here as well.
Do I have to build a connector for Modusign or MRPLN?
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.