Integration
Connect Gridfox and Modusign
When Record Created fires in Gridfox, your agent runs Add document request in Modusign, or Document Updated in Modusign to Add record in Gridfox. 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 Gridfox 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 Gridfox and Modusign can do together
From Gridfox to Modusign
When Record Created in Gridfox
then Add document request in Modusign
When Record Created or Updated in Gridfox
then Request Document With Template in Modusign
From Modusign to Gridfox
When Document Updated in Modusign
then Add record in Gridfox
When Document Updated in Modusign
then Update record in Gridfox
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 Gridfox and Modusign
Triggers and actions 3 triggers · 21 actions
Trigger
Record CreatedTriggers when a new record is created.
Trigger
Record Created or UpdatedFires when a record in the chosen Gridfox table is created or updated.
Action
Add recordCreate a record in a table.
Action
Add userAdd a user to the project.
Action
Delete recordDelete a record.
Action
Find recordsSearch records in a table by search parameters.
Action
Get recordGet a record by reference field value.
Action
Get record auditGet audit history for a record.
Action
List tablesList tables in the project.
Action
List User Groupslists the project's user groups with their member users (id, email).
Action
Update recordUpdate a record by reference field value.
Trigger
Document UpdatedTriggers when a document is created, signed, completed, or aborted.
Action
Add document requestRequest signatures on a document (signature request).
Action
Add labelCreates a new label in Modusign.
Action
Cancel document requestCancel a pending signature request.
Action
Delete labelDelete a label.
Action
Delete templateDelete a template.
Action
Get DocumentRetrieves the details of a single Modusign document by its ID.
Action
Get templateGet a template by id.
Action
Get userGets the Modusign user whose credentials the connection uses.
Action
Remind SigningResend signing request notifications to signers who did not sign.
Action
Request Document With TemplateCreate a document using a template and request signers to sign it.
Action
Search DocumentsSearch for documents with specific conditions.
Action
Update labelUpdate 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 Gridfox
Gridfox to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Gridfox to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Gridfox to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gridfox to MailchimpMailchimp marketing automation and email platform.
Gridfox to StripeStripe is a payment processing platform for online businesses.
Gridfox to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Modusign
HubSpot to ModusignHubSpot is your all-in-one stop for all of your marketing software needs.
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
Gridfox and Modusign, answered
What can start an automation from Gridfox?
Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Modusign when something happens in Gridfox?
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 Gridfox?
Yes. When something happens in Modusign, your agent can act in Gridfox too. This page covers both directions: Modusign's triggers and Gridfox's actions are listed here as well.
Do I have to build a connector for Gridfox 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.