Skip to main content

GoLogin Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a GoLogin location.
go_login_api.png

GoLogin

  1. Click the + icon on the Nexset that will be sent to the GoLogin destination, and select the Send to Destination option from the menu.

  2. Select the GoLogin connector from the list of available destination connectors. Then, select the credential that will be used to connect to the GoLogin account, and click Next; or, create a new GoLogin credential for use in this flow.

  3. In Nexla, GoLogin destinations can be created using pre-built endpoint templates, which expedite destination setup for common GoLogin endpoints. Each template is designed specifically for the corresponding GoLogin endpoint, making destination setup easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    GoLogin destinations can also be configured manually, allowing you to send data to GoLogin endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common GoLogin endpoints. Each template is designed specifically for the corresponding GoLogin endpoint, making destination setup easy and efficient.

Endpoint Settings​

  • Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your destination for this endpoint.

    Add Member to Workspace

    Invites one or more members to a workspace with specified roles and permissions. Use this endpoint to automate team onboarding or synchronize workspace membership from an external directory.

    • Sends a POST request to the GoLogin workspace members endpoint with the invitation payload in the request body.
    • Configure the following parameter: Workspace Id — the unique identifier of the GoLogin workspace to which members will be added.

    The workspace ID can be found in the GoLogin web application under workspace settings, or retrieved via the GoLogin API.

    Remove Member from Workspace

    Removes a member from a workspace, revoking all their access and permissions. Use this endpoint to automate offboarding or synchronize workspace membership removals from an external HR or identity system.

    • Sends a DELETE request to the GoLogin workspace member endpoint for the specified member.
    • Configure the following parameters: Workspace Id — the unique identifier of the workspace. Member Id — the unique identifier of the member to remove.

    This operation is irreversible — the member will lose all access to the workspace immediately. Re-invitation is required to restore access.

    Create Workspace

    Creates a new workspace with the specified configuration. Use this endpoint to programmatically provision GoLogin workspaces as part of a customer onboarding or environment setup workflow.

    • Sends a POST request to the GoLogin workspaces endpoint with the new workspace configuration in the request body.
    • Returns the created workspace object, including the newly assigned workspace ID.

    Enable the Response Webhook option to capture the new workspace ID returned after creation for use in downstream flows.

    Create Dev Token

    Creates a new developer API token for programmatic access to the GoLogin API. Use this endpoint to automate token provisioning as part of a developer or integration setup workflow.

    • Sends a POST request to the GoLogin developer token endpoint and returns the newly created token.
    • The created token is returned in the API response and should be captured via the Response Webhook option if it needs to be used downstream.

    Store generated API tokens securely. Tokens grant full API access to the associated GoLogin account and should not be exposed in logs or downstream systems without appropriate access controls.

    Create a Standard Browser Profile with Full Parameter Set

    Creates a standard browser profile with the full set of configurable parameters. Use this endpoint to bulk-provision browser profiles with custom fingerprint, proxy, and navigator settings sourced from a Nexset.

    • Sends a POST request to https://api.gologin.com/browser with a full profile configuration payload in the request body.
    • Returns the created profile object including the newly assigned profile ID.

    Use the Retrieve or Generate a Browser Fingerprint source endpoint to generate fingerprint values that can be included in the profile creation payload.

    Full Update of a Browser Profile

    Performs a full replacement update of a browser profile, including fingerprint, proxy, navigator settings, notes, and other attributes. Use this endpoint to synchronize complete profile configurations from an external source of truth into GoLogin.

    • Sends a PUT request to https://api.gologin.com/browser/{'{id}'} with the complete updated profile payload.
    • Configure the following parameter: Update Browser By Id Id — the unique identifier of the browser profile to update.

    This is a full replacement (PUT) operation — all profile fields must be included in the payload. Use the Get Profile by ID source endpoint to retrieve the current profile state before performing updates.

    Upload / Replace Cookies for a Browser Profile

    Uploads or replaces the cookies stored in a specific browser profile. Use this endpoint to restore saved session cookies or programmatically inject cookies into GoLogin profiles.

    • Sends a POST request to the GoLogin browser cookies endpoint with the cookie payload for the specified profile.
    • Configure the following parameter: Create Browser By Id Cookies Id — the unique identifier of the browser profile whose cookies will be replaced.

    This operation replaces all existing cookies for the profile. Use the Get Browser Cookies source endpoint to retrieve the current cookie set before performing updates if a backup is needed.

    Create a New Profile Folder

    Creates a new profile folder for organizing browser profiles. Use this endpoint to programmatically provision folder structures as part of a workspace setup or profile management workflow.

    • Sends a POST request to https://api.gologin.com/folders with the folder name and configuration in the request body.
    • Returns the created folder object including the newly assigned folder ID.

    Enable the Response Webhook option to capture the new folder ID for use in subsequent profile assignment flows.

    Create a New Tag

    Creates a new tag for organizing and classifying browser profiles. Use this endpoint to programmatically set up a tag taxonomy before bulk-assigning tags to profiles.

    • Sends a POST request to the GoLogin tags endpoint with the tag name and configuration in the request body.
    • Returns the created tag object including the newly assigned tag ID.

    Enable the Response Webhook option to capture the new tag ID for use in subsequent profile tagging flows.

    Bulk Delete Multiple Browser Profiles

    Deletes multiple browser profiles in a single API call. Use this endpoint to programmatically clean up stale or decommissioned profiles in bulk.

    • Sends a DELETE request to the GoLogin browser endpoint with an array of profile IDs in the request body.
    • Use the Record Batching option to group profile IDs into appropriately sized deletion payloads.

    Profile deletion is permanent and cannot be undone. Verify the list of profile IDs before executing bulk deletion flows.

    Delete a Browser Profile by ID

    Deletes a single browser profile by its unique ID. Use this endpoint to remove individual profiles as part of an automated lifecycle management workflow.

    • Sends a DELETE request to https://api.gologin.com/browser/{'{id}'} to remove the specified profile.
    • Configure the following parameter: Delete Browser By Id Id — the unique identifier of the browser profile to delete.

    Profile deletion is permanent and cannot be undone. Use lookup-based macros to iterate over a list of IDs and delete profiles one at a time.

    Move a Browser Profile into a Folder

    Moves a browser profile into a specified folder. Use this endpoint to reorganize profiles programmatically or automate folder assignment as part of a profile management workflow.

    • Sends a POST request to the GoLogin browser folder assignment endpoint for the specified profile.
    • Configure the following parameter: Create Browser By Id Folder Id — the unique identifier of the browser profile to move.

    Folder IDs can be retrieved using the List Folders source endpoint. Use lookup-based macros to dynamically assign profiles to folders based on data from an upstream Nexset.

    Stop a Running Cloud Browser Session

    Stops a running cloud browser session for a profile. Use this endpoint to programmatically terminate active sessions as part of a session management or resource cleanup workflow.

    • Sends a DELETE request to the GoLogin cloud browser web session endpoint for the specified profile.
    • Configure the following parameter: Delete Browser By Id Web Id — the unique identifier of the profile whose cloud session should be stopped.

    Stopping a cloud browser session terminates the active browsing session immediately. Ensure that any required session data has been saved before invoking this endpoint.

Configure Manually​

GoLogin destinations can be manually configured to send data to any valid GoLogin API endpoint. This is useful for creating or updating browser profiles, managing proxy assignments, importing profile configurations, or synchronizing profile metadata from external systems into GoLogin.

First, select the API method that will be used for calls to the GoLogin API from the Method pulldown menu. Common methods for GoLogin write operations include:

  • POST: For creating new browser profiles or triggering profile actions (e.g., https://api.gologin.com/browser).
  • PUT: For fully replacing an existing browser profile's configuration (e.g., https://api.gologin.com/browser/{profileId}).
  • PATCH: For partially updating a profile's settings, such as changing the user agent or proxy (e.g., https://api.gologin.com/browser/{profileId}).
  • DELETE: For removing a browser profile from GoLogin.

Data Format​

  1. Select the format in which the Nexset data will be sent to the GoLogin API from the Content Format pulldown menu. GoLogin's REST API accepts and returns JSON. Select JSON as the content format to ensure Nexla serializes the Nexset records into the expected request body structure.

API Endpoint URL​

  1. Enter the URL of the GoLogin API endpoint to which you want to send the Nexset data in the URL field. The GoLogin REST API base URL is https://api.gologin.com. Common destination endpoints include:

    • https://api.gologin.com/browser — Create a new browser profile (use with POST).
    • https://api.gologin.com/browser/{profileId} — Update an existing browser profile by ID (use with PUT or PATCH).
    • https://api.gologin.com/proxy — Create or update a saved proxy configuration.

    For update and upsert operations, include the GoLogin profile ID at the end of the URL (e.g., https://api.gologin.com/browser/abc123profileId). The profile ID can be found in the GoLogin web application under each profile's settings, or retrieved programmatically via the GoLogin GET /browser/v2 endpoint.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers and corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the Authorization header here. Nexla automatically populates it with the Bearer token from your GoLogin credential for every API call.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this GoLogin destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

GoLogin enforces API rate limits of 300 requests per minute for free and trial plans, and 1,200 requests per minute for paid plans. If you are processing large volumes of records, consider configuring batching to reduce the total number of API calls and avoid rate limit errors.

Response Webhook​

Optional

Nexla can automatically send the response received from the GoLogin API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as newly created profile IDs or error messages.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the GoLogin API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing​

After all endpoint settings have been configured, Nexla can send a test payload to the GoLogin API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the GoLogin API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured GoLogin endpoint, open the destination resource menu and select Activate.

    The Nexset data will not be sent to GoLogin until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.