Skip to content

Sign in

Monitive supports GitHub, Google, Microsoft, or email sign-in. None of the methods use a password. You can also link a second method to an account you already use, from account settings.

Each method resolves to its own identity on your account: a GitHub login resolves by your GitHub user ID, a Google login resolves by your Google account’s subject identifier, and email sign-in resolves by the address itself. Signing in with a different method than the one you used originally only finds your existing account automatically in specific cases — see When matching email addresses link automatically below. Outside those cases, see Linking a second method to an existing account before you try a different provider on an account you already use.

  1. Go to my.monitive.com.
  2. Pick GitHub, Google, Microsoft, or email:
    • Click Continue with GitHub to authorize with GitHub.
    • Click Continue with Google to authorize with Google.
    • Enter your address under Email and click Send sign-in link.
  3. For email sign-in, check your inbox: either follow the link, or enter the 6-digit code on the page you’re sent back to. The link and code both expire in 10 minutes.

Monitive’s sign-in page, showing Continue with GitHub, Continue with Google, and an email field

Linking a second method to an existing account

Section titled “Linking a second method to an existing account”

If you already have an account — say, from GitHub sign-in — and you want to add Google or email as a second way in:

  1. Sign in with the method you already use first.
  2. Go to Settings and find Connected identities.
  3. Click Add Google, or enter an address under Email and click Add email, then confirm it the same way you would for a fresh email sign-in.

Do this instead of signing in directly with the new method on its own — outside the specific cases described below where matching email addresses link automatically, a direct sign-in with an unlinked method creates a second, empty account with no monitors.

If the identity is already linked to a different account: linking fails. You’ll see this if you try to add a Google account or an email address that’s already tied to a different Monitive user — including a Google account whose own verified email happens to match your current account’s address. There is no merge path for this case today: the two accounts’ monitors and recipients stay separate. If you hit this, decide which account you want to keep using and sign in to that one directly with the method already linked to it.

Section titled “When matching email addresses link automatically”

Whether a first sign-in with a new method lands on your existing account or creates a fresh, empty one depends on the method and, for Google, the address:

  • GitHub: a first sign-in for a GitHub account links to an existing user who already holds that account’s verified primary email as a verified email identity and has no GitHub identity of their own yet. GitHub sign-in requires a verified primary email — GitHub reports none, or only an unverified one, and the sign-in is refused outright.
  • Google: a first sign-in links to an existing user who holds the same verified address and has no Google identity yet, but only when the address is gmail.com or googlemail.com, or a Google Workspace account whose domain matches the address. Any other verified address creates a separate user instead, with no link.
  • Email code: resolves by the address alone.

Outside those cases, there’s no automatic link. If the identity isn’t already linked to a different account, use the linking steps above instead. If the address is already attached to a different account’s GitHub or Google identity, linking will fail — sign in to that other account directly with the method already linked to it instead; there’s no merge path between the two accounts.

There isn’t an API or MCP equivalent for this guide — signing in and linking identities require completing an OAuth consent screen or clicking an emailed link in a browser, and the identity-linking endpoints (POST /api/v1/me/identities/github, /google, /email/start, /email/verify) only accept a browser dashboard session. Calling any of them with an API key or an MCP/OAuth access token returns 403 {"error":"session_required"}.

Once you’re signed in, the full set — creating monitors, managing recipients, querying incidents — is available over the REST API using an API key. MCP covers a narrower surface: monitor operations (create, read, update, delete, list) and incident operations (list), plus attaching an already-created recipient to a new monitor via create_monitor’s recipient_ids/recipients arguments. Creating or confirming recipients, and changing an existing monitor’s recipients, has no MCP tool today — use the REST API or dashboard for those. See API keys for API key creation and format, Use Monitive through MCP for connecting an agent, and Choose who gets alerts for recipient attachment semantics.

Sign-in itself carries no plan limit. Once signed in, see API keys for the API key limit (10 keys per account) and the monitors guide for monitor caps.

“This identity is already linked to another user.” You tried to link a Google account or an email address already tied to a different Monitive account. Sign in to that other account directly instead, or decide which of the two accounts to keep — there’s no built-in merge.

I signed in with Google/email and my monitors are gone. You likely landed in a second, new account rather than your original one. Sign out, sign back in with the method you used originally (GitHub, most likely), and link the new method from Settings → Connected identities instead of signing in with it directly.

The sign-in link or code expired. Links and codes are valid for 10 minutes. Click Use a different address (or just retry) to request a new one.

I got rate-limited. Email sign-in and linking share a per-address and per-process sender limit. Wait and retry — the page shows how long.