Integration
Connect Saasu to Signatureapi
When New Contact fires in Saasu, 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 Saasu 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 Saasu can start in Signatureapi
When New Contact in Saasu
then Add ceremony in Signatureapi
When New Contact in Saasu
then Add deliverable 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 Saasu and Signatureapi
Triggers and actions 1 trigger · 36 actions
Trigger
New ContactTriggers when a new contact is added to your Saasu file.
Action
Add activityCreates an activity (task, call, meeting, note) in your Saasu file, optionally attached to a contact or transaction.
Action
Add companyCreates a company record in Saasu.
Action
Add itemCreates an inventory or combo item in Saasu.
Action
Add journalCreates a manual journal entry with debit and credit lines in a Saasu file.
Action
Create ContactCreates a new contact (person) in your Saasu file and returns its id.
Action
Create Item InvoiceCreates an item-layout invoice, quote or order in Saasu with inventory item line items.
Action
Create Service InvoiceCreates a service-layout sale or purchase invoice in Saasu, with line items described by account and amount.
Action
Delete contactDeletes a contact from your Saasu file.
Action
Delete invoiceDeletes a sale or purchase invoice from the Saasu file.
Action
Delete itemDeletes an inventory item from the Saasu file.
Action
Email invoiceEmails a Saasu invoice to the email address you specify.
Action
Find accountsReturns the accounts in your Saasu chart of accounts, filtered by type, status, bank-account flag or header account.
Action
Find companiesReturns the companies in your Saasu file whose name matches, optionally limited to a last-modified date range.
Action
Find ContactFinds Saasu contacts matching an email, name, company or other criteria and returns the matching contacts.
Action
Find itemsReturns the inventory and combo items whose code or description matches the search text.
Action
Get contactReturns a single Saasu contact by its ID.
Action
Get invoiceReturns a single Saasu invoice (sale or purchase) by its ID, including line items and totals.
Action
Get journalReturns a single journal transaction, including its date, reference, summary and journal line items.
Action
Update contactUpdates an existing contact in Saasu, such as their name, email, phone numbers, addresses and customer/supplier flags.
Action
Update invoiceUpdates an existing Saasu sale or purchase invoice, replacing its details and line items.
Action
Update itemUpdates an existing inventory or combo item in Saasu, such as its code, description, prices, accounts and tax codes.
Action
Add ceremonyCreates 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.
Action
Add deliverableCreates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
Action
Add envelopeCreates an envelope with documents and recipients and starts the signing process.
Action
Add uploadUploads 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.
Action
Cancel envelopeCancel an in-progress envelope so remaining recipients can no longer sign.
Action
Delete envelopeDelete an envelope.
Action
Get deliverableRetrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
Action
Get envelopeRetrieve a single envelope by id.
Action
Get recipientRetrieves a recipient's details, including status, ceremony information and completion timestamp.
Action
Get uploadFetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
Action
List deliverablesReturns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
Action
List envelopesLists envelopes in the account, most recent first, optionally filtered by status or topic.
Action
Resend requestResends 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.
Action
Update envelopeUpdate mutable fields (e.g. title, metadata) of an existing envelope.
Action
Update recipientReplaces 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 Saasu
Saasu to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Saasu to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Saasu to StripeStripe is a payment processing platform for online businesses.
Saasu to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Saasu to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Saasu to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Signatureapi
HubSpot to SignatureapiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SignatureapiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SignatureapiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SignatureapiGoogle Sheets
Gmail to SignatureapiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignatureapiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Saasu and Signatureapi, answered
What can start an automation from Saasu?
Any of Saasu's 1 trigger in the catalog, including New Contact. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Signatureapi when something happens in Saasu?
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 Saasu?
Signatureapi has no triggers in the catalog today, so automations start in Saasu. 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 Saasu 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 Saasu 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.