Docs

My Connections

Part of the MountDev Ops Integrations documentation. Updated November 7, 2026

MountDev Ops Integrations documentation | Updated November 7, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 3,437 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.

What You See

My Connections lists everything you have connected: the services from the Library and any other connection you made, such as one added with Add a Connection. Connections are listed under their group, such as Google or Zoho. A group with more than three connections starts collapsed to its heading, which says how many it holds and how many need attention; press the heading to open or close it. Each row shows its health, when it was last checked, and which apps use it. Connections that are not in the Library are under Other Connections. The list comes from action integrations.library, and the same facts are available to an assistant as integrations.health (tool integrations_health), which never returns a key.

Working: the last check worked.
Needs Attention: the last check failed. The row says why, in plain words, such as "Telnyx did not accept the saved key", and when. Replace the key.
Not Checked: nothing has checked it yet. Select Check Now.

Check Now

Check Now makes one read-only call to the service with your own key and shows whether it worked (action integrations.check). Only the result and the reason are kept, with the time. Whatever the service sends back is never kept, shown, or logged. Anyone who can see the library can run a check. A check never changes anything at the service.

Replace Key

Replace Key opens the same pop up as Connect, with the new key. The old key is replaced and never shown. For Stripe and Zoho Desk it opens their own steps (action integrations.save).

Disconnect

Disconnect names what will stop before you confirm, such as "new payments on invoices; automatic charging of subscriptions; payment links on proposals" (action integrations.stops). Confirming removes the saved key from your account and the apps that used it stop (action integrations.disconnect, tool integrations_disconnect). You can connect it again any time with a key. Only owners, admins, and anyone whose role allows managing connections can disconnect.

Add a Connection

Add a Connection saves any other outside service that has an address and a key, to use with the Call a Web Service step in your workflows. It works as it always has, in Connected Services.

API Keys, Webhooks, Automations, and Inbound Webhooks

These pages are in the menu of Integrations, where they were on Settings, Connections. They work exactly as before. See API Keys, Webhooks, and Automations.