Skip to main content

Login

Authenticates with pCloud and establishes a connection for performing cloud storage 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​

  • Credentials - pCloud account credentials containing username (email) and password.
  • Region - The pCloud server region. Choose between "Europe" (default) or "United States" based on where your pCloud account is registered.

Output​

  • Client Id - A unique identifier for the pCloud client connection that must be used in all subsequent pCloud operations.

How It Works​

The Login node is the essential first step in any pCloud automation workflow. It establishes an authenticated connection to pCloud's servers and provides a client ID for use in subsequent operations.

When executed, the node:

  1. Retrieves the username and password from the provided credentials
  2. Determines the appropriate pCloud server based on the selected region
  3. Authenticates with pCloud using the credentials
  4. Creates a pCloud client instance
  5. Stores the client in a thread-safe manager
  6. Returns a unique client ID for use in other pCloud nodes

Requirements​

  • A valid pCloud account
  • Account credentials (email/username and password) stored in Robomotion credentials
  • Knowledge of your account's region (Europe or United States)

Error Handling​

The node will return specific errors in the following cases:

  • Missing or invalid credentials
  • Empty username in credentials
  • Empty password in credentials
  • Authentication failure with pCloud servers
  • Network connectivity issues

Usage Notes​

  • The Login node must be executed before any other pCloud operations
  • The returned Client Id must be passed to all subsequent pCloud nodes
  • The region selection is important - use "Europe" for European accounts and "United States" for US accounts
  • The client connection remains active throughout the flow execution
  • Each Login creates a new client session in memory

Best Practices​

  • Store your pCloud credentials securely using Robomotion's credential system
  • Use a single Login node at the beginning of your flow
  • Verify the correct region for your pCloud account to avoid connection errors
  • Keep the Client Id in the message scope for easy access by other nodes
  • Handle authentication errors appropriately to prevent workflow failures

Example Flow​

A typical pCloud automation flow starts with Login:

  1. Login - Authenticate and get Client Id
  2. Create Folder - Create a folder structure
  3. Upload File - Upload files to pCloud
  4. Get Public Link - Generate sharing links

The Client Id from step 1 is used in all subsequent steps to maintain the authenticated connection.

Regional Considerations​

pCloud operates separate infrastructure for different regions:

  • Europe - For accounts registered in European countries
  • United States - For accounts registered in the US and other regions

Using the wrong region will result in authentication failures even with correct credentials. If you're unsure of your account region, check your pCloud account settings or the URL you use to access pCloud (eapi.pcloud.com for Europe, api.pcloud.com for US).