Integration
Connect Finmo to Signatureapi
When Application Submitted by Borrower fires in Finmo, your agent runs Add ceremony in Signatureapi. 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 Finmo and Signatureapi 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 Finmo can start in Signatureapi
When Application Submitted by Borrower in Finmo
then Add ceremony in Signatureapi
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 Finmo and Signatureapi
Triggers and actions 6 triggers · 28 actions
- Application Started
Triggers when a new mortgage application is started in Finmo.
- Application Submitted by Borrower
Triggers when a borrower submits (or resubmits) a mortgage application in Finmo.
- Deal Submitted
Triggers when a deal (application) in Finmo reaches the Submitted status.
- Updated Borrower Email
Triggers when a borrower's email address changes (or a new borrower appears) on any application in the selected team.
- Updated Deal Status
Triggers when an application (deal) changes to a new status.
- Updated Document Request Status
Triggers when a document request on a Finmo application changes status (requested, needs attention, for review, approved, archived).
- Add application
Creates a new mortgage application (deal) in Finmo for a new or existing applicant, optionally inviting the borrower.
- Add client
Adds a client (borrower) to a Finmo application, optionally inviting them to the borrower portal.
- Add client income
Adds an income (employment, pension, support or other) to a borrower on a Finmo application.
- Add client liability
Creates a liability (credit card, loan, lease, support payment, etc.) on a Finmo application for one or more of its borrowers.
- Add document
Creates a document upload on a Finmo application and returns a signed link for uploading the file.
- Add document request
Creates a document request on a Finmo application, asking one or more borrowers to provide a document of the chosen type.
- Delete client
Removes a client (borrower) from a Finmo application.
- Find applications by criteria
Searches applications by borrower name or application ID, optionally narrowed to a brokerage, team or broker.
- Get client
Returns a client (borrower) on a Finmo application, including their contact details and profile.
- List application documents
Returns every document (document request) on a Finmo application, with its status, file details, borrower and document template.
- List applications
Returns application overviews for a brokerage, team or broker, optionally searched by borrower name.
- Update application
Updates an application's goal settings, such as the goal, purchase price, down payment, property use and closing date.
- Update client
Updates a client (borrower) on a Finmo application with new contact, personal and portal details.
- Add ceremony
Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
- Add deliverable
Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
- Add envelope
Creates an envelope with documents and recipients and starts the signing process.
- Add upload
Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
- Cancel envelope
Cancel an in-progress envelope so remaining recipients can no longer sign.
- Delete envelope
Delete an envelope.
- Get deliverable
Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
- Get envelope
Retrieve a single envelope by id.
- Get recipient
Retrieves a recipient's details, including status, ceremony information and completion timestamp.
- Get upload
Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
- List deliverables
Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
- List envelopes
Lists envelopes in the account, most recent first, optionally filtered by status or topic.
- Resend request
Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
- Update envelope
Update mutable fields (e.g. title, metadata) of an existing envelope.
- Update recipient
Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
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 Finmo
Finmo to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Finmo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Finmo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Finmo to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Finmo to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Finmo to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Signatureapi
Questions
Finmo and Signatureapi, answered
What can start an automation from Finmo?
Any of Finmo's 6 triggers in the catalog, including Application Submitted by Borrower, Deal Submitted, Updated Borrower Email and Updated Deal Status. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Signatureapi when something happens in Finmo?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to Finmo?
Signatureapi has no triggers in the catalog today, so automations start in Finmo. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for Finmo or Signatureapi?
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 Finmo and Signatureapi 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.