Website State Setup

Common use cases

  • Set a location, language or currency.
  • Sign in to a website where you have permission to automate access.
  • Open a required page and complete a preliminary interaction.

Trigger condition

Enable Website State Setup and configure Perform when not found selector. The action sequence runs only when this selector does not match the current page.

  • Selected element count 0: the action sequence runs.
  • Selected element count 1 or more: the expected state already exists and the sequence does not run.

Use Element Preview to test the trigger condition. Select an element that proves the required state exists, such as the active location or a signed-in account label.

Fig. 1: Website State Setup

Fig. 2: Selected Element

Available actions

  • Open URL - Open a specific page before continuing. Do not add this action when the remaining actions can run on the current page.
  • Click - Click a matching element/button/tab.
  • Text Input - Enter non-sensitive text into a matching field.
  • Password Input - Enter a password. Password values synced or imported into Cloud are encrypted, cannot be exported, and are blank in an exported sitemap definition.

Match a specific state

The point-and-click selector may identify the correct element without distinguishing its text. Add a supported text condition when the action should depend on a specific value.

div.store-location:contains('New York')

The setup runs when the selector above is not found. A negated condition can be used when the sequence should run only while a particular state is present.

Authorized access only

Use sign-in automation only where data extraction behind the login complies with the website terms or where you have explicit written permission.

Cloud failure behavior

When a Cloud job uses Website State Setup and a required element cannot be found, the affected page is recorded as a Failed page. The failure reason identifies the missing element or selector, for example:

Couldn't find input - input#customer-email:visible

The exact message depends on the configured Website State Setup. Use the job's Inspect view to compare the returned page with the expected state.

Related