Skip to main content
Use this example to log into CoverMyMeds, handle optional email-based two-factor authentication (2FA), and retrieve a patient authorization request using a request key, patient last name, and date of birth. This workflow demonstrates how to build a resilient payer / prior authorization automation that supports:
  • Existing authenticated sessions
  • Conditional username/password login
  • Email-based 2FA verification
  • Request key retrieval flows
  • Patient validation using demographics
  • Browser state extraction for downstream workflows
This page is intentionally keyword-rich so you can find it by searching for: CoverMyMeds automation, prior authorization workflow, email 2FA, request key lookup, payer portal automation, browser state extraction, authorization request retrieval, conditional login, session reuse, CMM workflow.

Overview

This automation:
  • Detects whether login is required
  • Performs username/password authentication only when needed
  • Detects whether email-based 2FA is required
  • Retrieves a verification code from email
  • Navigates to the Requests section
  • Opens a request using:
    • Request key
    • Patient last name
    • Date of birth
  • Extracts browser state information after the request is loaded

Minimal example

The core pattern combines:
  • Conditional login detection
  • Conditional email 2FA handling
  • Request lookup by key

Full automation

What this workflow demonstrates

What the final state extraction returns

The state extraction appends browser context information such as:

When to use this