AlterLabInstall

Summary

Manage AlterLab’s stored browser sessions for authenticated scraping: create, list, retrieve, update, delete, validate, or refresh a session. Choose the session operation and provide its required ID or creation details; list filters and other fields are optional.

Inputs

• Operation (required) — Choose Create, Delete, Get, List, Refresh, Update, or Validate.
• Session ID (required) — UUID required for Get, Update, Delete, Validate, and Refresh.
• Name (required) — Label for a new session; used by Create.
• Domain (required) — Target domain for a new session; used by Create.
• Cookies (JSON) (required) — Cookie name-value object required by Create. For Update, optionally provide replacement cookies; for Refresh, optionally provide cookies to rotate in.
• Additional Fields — For Create, optionally set custom headers, notes, and expiration.
• Update Fields — For Update, optionally change the name, cookies, headers, notes, or expiration. Only supplied fields are sent.
• Headers (JSON) — For Refresh, optionally provide updated custom headers; can be supplied with or without refreshed cookies.
• Filters — For List, optionally filter by domain and status (active, expired, or invalid).

Output shape

One or more n8n items containing session data or operation results.

Create, Get, Update, and Refresh return a session object with camelCase fields such as id, name, domain, cookieNames, status, and timestamps. List emits one item per returned session; if none are returned, it emits {"sessions": [], "total": 0}. Validate returns sessionId, isValid, confidence, httpStatus, detectedUser, cookiesExpiringSoon, consecutiveFailures, and details. Delete returns {"sessionId": "…", "deleted": true}. API failures are raised as node errors.

Links

• n8n community nodes installation guide