Connected Services
Part of the MountDev Ops Workspace documentation. Updated November 20, 2026
MountDev Ops Workspace documentation | Updated November 20, 2026
The API connections your company uses, in one place. Any service with an API can be added: its address, how it signs in, and its key or token. This page is confidential: only owners and admins see it. No key is ever shown to anyone, an AI agent included. Today AI agents never see this page. When Connection Actions ship (Planned), an AI agent will be able to read a custom connection's name, address, and actions, read only, and draft changes that wait for an owner or admin's Yes. It still never sees or types a key.
What Each Connection Shows
- Its name and what it is for.
- Its address (always https).
- Whether it is working: Working, Failing, or Not checked yet, and when it was last checked. Under Failing the connection always says why, with the time: "Last check failed: PlanetScale did not answer within 20 seconds. | Oct 22, 2026, 10:15 AM".
A saved key or token is never shown again, to anyone. It is stored encrypted with a key that only your company's workspace can use, and it can only be replaced.
Adding or Changing a Connection
On Settings, in the Connections card, on the Connected Services tab (owners and admins; the old API Connections address opens it):
Connected Services is a list with one row for each connection (its name, what it is, its status, and when it was last checked). Select a row to open that connection's page, with its sections in this order: Overview and Status (with Check Now), Actions, Fixed Address, Routes, Webhook Address, Change, and Danger Zone (with Delete). A section that does not apply is not shown. The one Add button at the top opens the choices below, Connect a Service and Add a Connection. Integrations, My Connections uses the same list and pages (My Connections).
- Connect a Service (an Add choice) lists the services below that are not connected yet; choose one to connect it with your own account.
- Add a Connection (an Add choice; action
core.connections.save): for any other API, a name, what it is for, the address, and how it signs in: a bearer token, a key in a header (name the header), a user name and password, a key in the address (name the parameter), or no sign-in. Add a check address, like /v1/status, for the check to ask. Up to 10 Extra Headers (a name, a value, Keep this secret, Send as a query parameter) are sent on every call, for a value such as a client identifier; a secret value is encrypted and never shown again, and a new address removes it (see My Connections). - A connection can also sign in with a service account key or a one-time sign-in (see Sign-In for Outside Services); the Add a Connection pop up offers them once their screen is approved (Planned).
- Change (on the connection's page) a connection the same way. Leave the key empty to keep the saved one. Changing the address, the sign-in, or the key marks it as not checked yet.
- Delete a connection (in its Danger Zone; action
core.connections.delete). - Check Now (action
core.connections.check) asks the service once with the saved key and records whether it answered, and when it fails, the plain reason: the service's own answer, a timeout, or that it could not be reached. - Seeing the list (action
core.connections.list) never includes a key.
Actions
A connection you added yourself can carry Actions: single calls to the service, described once, that workflows use as steps. See Connection Actions.
Fixed Address
A service that accepts calls only from registered addresses is reached through the fixed address servers, never directly. Any connection can use them: turn on Send From a Fixed Address (the detail fixed_address when saving it). See Fixed Outbound Address.
Stripe
Connect a Service, then Stripe, adds your company's own Stripe account, which Invoices uses to charge your customers and take their payments (Payments With Stripe). It asks for three keys, with the same action (core.connections.save, service Stripe):
- Secret key: starts with sk_live_ (or rk_live_ for a restricted key). Stored encrypted, never shown again.
- Publishable key: starts with pk_live_. Your customers' invoice pages use it.
- Webhook signing secret: starts with whsec_. Stored encrypted, never shown again. It proves that each payment update came from Stripe.
The address (https://api.stripe.com) and the check are fixed, and a company has one Stripe connection. Test keys (sk_test_, pk_test_) work the same way and show Test mode. Change replaces any of the keys; leave one empty to keep it.
Other Services
Connect a Service also connects these, each with your own account, one of each per company, with the same action (core.connections.save, with the service). Each one's address, sign-in, and check are fixed. Its key is checked before it is saved, stored encrypted, and never shown again; Change keeps the saved key when you leave it empty. Check Now asks the service whether the key works.
- Telnyx (phone calls, text messages, and video meetings): the API key (it starts with KEY), the public key (it proves that a text, call, or update really came from Telnyx), the business number, and, if you use them, the WebRTC connection ID, the TeXML application ID, and the messaging profile ID. The business number (10 digits) is needed for calls and texts only: leave it empty if you use Telnyx only for video meetings. Its row then says so, and Phone says calls and texts need it. Check Now reads your Telnyx balance. It is one connection for every app that works through Telnyx, so no app asks for its own key: Meetings holds video meetings in Telnyx Video Rooms with it, and you pay Telnyx directly for what you use there. Once Telnyx is connected, its row shows your webhook address with a Copy button: Telnyx sends its video meeting updates there, and video meetings add it to each room on their own. Every update is checked against your public key, and one that is not from your Telnyx account, or more than 5 minutes old, is refused.
- Twilio (phone calls, text messages, and video meetings): the Account SID (it starts with AC), the Auth Token, an API Key SID (it starts with SK) and the API key's secret, and, once Phone uses them, the TwiML application SID and the Messaging Service SID. The Auth Token and the API key secret are saved sealed and never shown again. Check Now asks Twilio for your account with the Account SID and Auth Token. It is one connection for every app that works through Twilio, so no app asks for its own key, and you pay Twilio directly for what you use. See Phone Providers for what it powers and how to choose which provider serves what.
- Cloudflare (DNS records for your domains): an API token with "Edit zone DNS" for your zones. Check Now asks Cloudflare to verify the token.
- Google Search Console (search performance for your websites): a service account key file (JSON). Its address shows on the connection; add that address to your Search Console as a user. Check Now signs in to Google with the key and lists the sites it can see.
- Google PageSpeed (page speed measurements for your websites): a Google API key (it starts with AIza). Check Now measures a sample page, which can take up to 25 seconds.
- Ahrefs (search and AI visibility data): an Ahrefs API key. Check Now reads your Ahrefs plan's limits.
- GitHub (reading your own repositories from a workflow, read only): a fine-grained token made in GitHub under Settings, Developer settings, Fine-grained tokens, with Contents and Metadata set to Read only for the repositories to read, and those repositories listed as owner/name. It starts with github_pat_. Check Now reads one repository's name, never its content. Workflows only ever read through it (Reading GitHub From a Workflow).
- Your Own Storage (a bucket you own, for backups and large files): the address of any S3 compatible storage, the region, the bucket, and an access key ID and secret access key made for that bucket. The secret is sealed and never shown again. Check Now writes a tiny test object and removes it. Workflows put, link, list, and delete objects through it, and its calls follow the Send From a Fixed Address switch (Your Own Storage in Workflows).
- OpenAI API (speech to text): an OpenAI API key, which starts with sk-. Meetings uses it to transcribe recordings (Automatic Transcription); it is sent only from your workspace, and OpenAI bills its usage to your OpenAI account. MountDev Ops supplies no AI model of its own. Check Now lists the models the key may use.
- Web Search (Brave Search): a Brave Search API key, for apps that search the public web, such as Partners' weekly check for leaked pricing. Check Now runs one test search.
- Rocket.net (website hosting: sites, staging copies, storage, and bandwidth): Rocket.net has no API keys, so the connection signs in as a Rocket.net user: the login email and the password. A user made just for this is best. Check Now signs in to Rocket.net.
- BlogVault (website backups, security scans, and updates): the API key from BlogVault, My Account, API Credentials. Check Now lists your sites.
- Slack Notices (the Slack channel your website notices are posted to): the Incoming Webhook address for one channel (Slack: Apps, Incoming Webhooks, Add to Slack). It starts with https://hooks.slack.com/services/ and nothing else is accepted. It is sealed with your account's own key and never shown again. Check Now posts one made-up line to the channel and says whether Slack took it. Slack Notices says how notices reach it.
- Amazon Web Services (your AWS account, for sending email through Amazon SES): an access key from AWS, IAM, Users, the user for this connection, Security credentials, Create access key. Enter its access key ID (it starts with AKIA), its secret access key, and the region your SES account sends from (like us-east-1). Give that user only the permissions it needs. The secret access key is stored encrypted and never shown again. Check Now asks Amazon SES for your account's sending status.
- Amazon Lightsail (your AWS account, to build a fixed address server in it): an access key from AWS, IAM, Users, a user that has only the Lightsail policy shown on the Fixed Addresses screen (it cannot delete anything), Security credentials, Create access key, the key ID and the secret access key. It is used once, to build, and your workspace erases the secret when the address is ready. Check Now asks Lightsail for its places. See Fixed Addresses.
- AWS Hosting (your AWS account, for the websites you host on AWS): for a company that hosts websites on its own AWS account. Its own access key, apart from Amazon Web Services (email), from AWS, IAM, Users, the user for your hosting, Security credentials, Create access key. Enter your AWS account ID (12 numbers), the access key ID (it starts with AKIA), the secret access key, and the region your websites run in (like us-west-2). Give that user only the hosting's permissions. The secret access key is stored encrypted and never shown again. Check Now asks AWS which account the key belongs to, checks that it is the one you entered, and checks that the key may read your hosting's ECS clusters; it changes nothing.
- Cloudflare Hosting Storage (storage for the websites you host on Cloudflare, and their visit counts): for a company that hosts websites on Cloudflare. Enter your Cloudflare Account ID, the R2 Bucket your hosted websites are stored in, and two things made in Cloudflare:
- An API token from API Tokens, Create Token, Custom Token, with two permissions: Account, Workers R2 Storage, Edit (so each website gets its own storage key that works only for its own files and only for a day), and Account, Account Analytics, Read (so visits and cache use can be counted for each website).
- An R2 API token from R2, Manage API Tokens, Create API Token, with Object Read and Write on that bucket only. Cloudflare shows its access key ID and secret access key once, when it is made: enter both.
- PlanetScale (the MySQL database of the websites you host on Cloudflare): for a company whose hosted websites keep their data in PlanetScale (made in Cloudflare under Storage and Databases, or directly with PlanetScale). Enter your PlanetScale Organization (its name, as in app.planetscale.com/your-organization), and a service token from your organization's Settings, Service tokens: its ID and the token, which PlanetScale shows once. Give the token these permissions: read_databases, read_branch, and read_metrics_endpoints (so the hosting can watch the database and warn before it needs a larger size), connect_production_branch (so each website gets its own database password), and read_backups and write_backups (so an hourly backup schedule is kept). The token is stored encrypted and never shown again. Check Now lists your databases; it changes nothing. It waits up to 20 seconds for PlanetScale and asks once more when PlanetScale could not be reached or had a problem on its side, so one slow moment does not mark it Failing. When it fails, it says why in PlanetScale's own words where PlanetScale gave them: a token or ID it did not accept, a missing read_databases permission, an organization the token cannot see, too many requests, or a timeout. A token without read_metrics_endpoints still connects.
- Published Service Endpoint (for an account that publishes its own actions to its customers, see Publishing Your Own Actions to Your Customers, which you manage in Verticals, then Your Services for Clients): the full https address that receives each call to one of your published actions, and the endpoint key your endpoint expects in its Authorization header. The key is stored encrypted, opened only when a call is sent, and never shown again. Check Now sends your endpoint a call that does nothing and says what it answered; the address is checked like every address the workspace calls, so it cannot be on a private network.
- Google Sign-In Client (Google services that need a person to sign in, such as Google Postmaster Tools): some Google services answer only a person who signed in with Google, never a service account. In Google Cloud Console, open Google Auth Platform, Clients, Create Client, choose Web application, and add the redirect address that the service using it gives you. Enter the Client ID (it ends in .apps.googleusercontent.com) and the Client secret (it starts with GOCSPX-). The secret is stored encrypted and never shown again. The sign-in itself is made where the service is used. Check Now asks Google whether it knows the client and its secret, with a sign-in that cannot exist, so nothing is signed in and nothing is kept.
The API token and the secret access key are stored encrypted and never shown again. Check Now asks Cloudflare to make read-only storage credentials for the bucket that last 15 minutes, which proves the token, the access key ID, and the bucket together; nothing it gets back is kept.
The Claude API key and the outside MCP servers your AI agents use are on AI Agents, under Your AI Agents' Keys. Cloudflare Turnstile keys, for spam protection on your forms, are kept in Forms Settings, and Resend is one of the ways your email can go out, kept in Settings, Email. Each is in one place only, and Connected Services shows it too: once set up, with Change to open its place; until then, under Connect a Service, which opens its place.
Zoho WorkDrive
Importing from other services is coming later (Import From Zoho WorkDrive). A Zoho WorkDrive connection keeps its saved key and can still be checked with Check Now, but it brings no files into Files for now. Use Import From File in Settings to bring your data in.
Zoho Desk
Importing from other services is coming later (Zoho Desk in Helpdesk). Zoho Desk is no longer offered under Connect a Service (actions core.zdesk.save, core.zdesk.start, core.zdesk.finish, and core.zdesk.choose answer that importing is coming later), and a Desk's tickets are not brought into Helpdesk for now. A Zoho Desk connection saved earlier stays listed with its saved key, says so on its card, and can be deleted; Delete never removes a ticket or message already in Helpdesk.
Bringing Existing Keys In
When a business already kept these keys in another system run for it, they can be brought into its workspace once (its Turnstile keys go to Forms Settings, and its MCP servers to AI Agents), each one sealed at once with your company's own key, exactly as if an owner had typed it in. A connection someone already made here is never replaced, a key that does not pass the same checks as the form is left out, and the Activity Log says what was connected, ending with "brought over from the hub". No key is shown or logged along the way.
