Integration
Connect SignNow and Sorry
When Document Updated fires in SignNow, your agent runs Update status page in Sorry, or New notice in Sorry to Update Document in SignNow. 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 SignNow and Sorry 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 SignNow and Sorry can do together
From SignNow to Sorry
When Document Updated in SignNow
then Update status page in Sorry
From Sorry to SignNow
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 SignNow and Sorry
Triggers and actions 4 triggers · 29 actions
- Document Deleted
Triggers when a document has been deleted.
- Document Updated
Triggers when a document has been updated.
- New Document
Triggers when a document has been uploaded to SignNow.
- Add signing link
Creates a single signing link (and QR code) for a SignNow document or template so anyone with the link can sign it.
- Add template
Creates a template in SignNow from an existing document. The source document is flattened into a reusable template.
- Delete document
Deletes a document from the SignNow account.
- Download document
Downloads a SignNow document as a PDF, or as a zip that also includes its attachments.
- Get document
Get a document by id.
- Invite to Sign
Sends a free form invite to sign an existing SignNow document that has no fields; the signer can place their signature anywhere on the document.
- List documents
Lists the documents in a SignNow folder (for example your Documents folder), with optional filtering by signing status or date and sorting.
- List signing links
Lists the signing links created for a document or template.
- Merge documents
Merges existing SignNow documents into one new document.
- Resend invite
Resends the email invite to sign a document to a signer who has not yet signed.
- Update Document
edits an existing document (e.g. adds or updates fields/texts), which fires the user.document.update event without sending an invite (avoids the daily invite limit).
- Upload Document
Uploads a file to the SignNow account and returns the new document's ID.
- Upload Document & Extract Fields
Uploads a .doc, .docx or .pdf file to SignNow and converts its text tags (and optionally its fillable PDF fields) into SignNow fields.
- New notice
Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.
- Add component
Creates a new component on a Sorry status page, optionally nested under a parent component.
- Add notice
Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.
- Add notice update
Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.
- Add subscriber
Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.
- Delete notice
Deletes a notice (incident, maintenance or general) from a Sorry status page.
- Delete subscriber
Permanently removes a subscriber from a status page.
- Get notice
Returns a single notice from a status page, including its type, state, subject, synopsis and link.
- Get status page
Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.
- List components
Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.
- List notices
Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.
- List notice updates
Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.
- List status pages
Returns all status pages in your Sorry account, optionally filtered by name or creation date.
- List subscribers
Returns the subscribers on a status page, optionally only those who receive notices for a specific component.
- Update component
Updates a component on a Sorry status page, such as its name, description, position or parent component.
- Update notice
Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.
- Update status page
Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.
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 SignNow
SignNow to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
SignNow to StripeStripe is a payment processing platform for online businesses.
SignNow to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
SignNow to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
SignNow to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
SignNow to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
More into Sorry
HubSpot to SorryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SorrySalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SorryGoogle Sheets
Gmail to SorryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SorryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
SignNow and Sorry, answered
What can start an automation from SignNow?
Any of SignNow's 3 triggers in the catalog, including Document Updated, New Document and Document Deleted. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sorry when something happens in SignNow?
Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Sorry to SignNow?
Yes. When something happens in Sorry, your agent can act in SignNow too. This page covers both directions: Sorry's triggers and SignNow's actions are listed here as well.
Do I have to build a connector for SignNow or Sorry?
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 SignNow and Sorry 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.