Skip to main content

Create Session

Establishes a connection to CapMonster Cloud by creating a session with your API key. This session is required for all captcha solving operations.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Options​

  • API Key - The CapMonster Cloud API key credential from your account. This should be stored as a credential in Robomotion for security.

Output​

  • Session - A unique session ID that must be passed to all other CapMonster nodes to authenticate API requests.

How It Works​

The Create Session node is the entry point for all CapMonster operations. When executed, it:

  1. Retrieves your API key from the provided credential
  2. Creates a CapMonster Cloud client instance
  3. Generates a unique session ID
  4. Stores the client instance for use by other nodes
  5. Returns the session ID for use in subsequent operations

Requirements​

  • A valid CapMonster Cloud account
  • An API key from your CapMonster dashboard
  • The API key must be stored as a credential in Robomotion

Getting Your API Key​

  1. Sign up or log in to CapMonster Cloud
  2. Navigate to your dashboard
  3. Find the API key section
  4. Copy your API key
  5. Store it as a credential in Robomotion

Error Handling​

The node will fail in the following cases:

  • Missing or invalid API key credential
  • Empty API key value
  • Unable to create CapMonster client

Usage Notes​

  • The Create Session node must be executed before any captcha solving operations
  • The session ID should be stored in a message variable for easy access
  • Each Create Session creates a new client instance
  • Sessions are stored in memory and persist throughout the flow execution
  • Multiple sessions can be created if you need to use different API keys

Best Practices​

  • Store your API key as a credential, never hardcode it in your flow
  • Use a single Create Session node at the beginning of your captcha solving workflow
  • Pass the session ID to all subsequent CapMonster nodes
  • Consider checking your balance after creating a session to ensure sufficient funds
  • Handle connection errors gracefully to avoid flow interruptions

Example Flow​

Create Session (API Key credential)
  → Session ID stored in message
    → Get Balance (verify funds)
      → Solve Captcha nodes (use session ID)

Security Considerations​

  • API keys provide full access to your CapMonster account
  • Always use Robomotion's credential storage for API keys
  • Never log or expose API keys in error messages
  • Rotate your API keys periodically for enhanced security
  • Monitor your account usage to detect unauthorized access