Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
Overview
This node interacts with the "Connect Secure" API to retrieve data related to browser extensions associated with a user. Specifically, the "Retrieve Browser Extensions" operation under the "Asset Data" resource fetches browser extension information based on user ID and optional query parameters such as filtering conditions, pagination, and sorting.
Typical use cases include:
- Fetching a list of browser extensions installed or managed for a specific user.
- Querying browser extension data with filters (e.g., by extension type or status).
- Paginating through large sets of browser extension records.
- Sorting the results based on specified fields.
For example, a security analyst might use this node to pull all browser extensions installed by a particular user to audit for unauthorized or risky extensions.
Properties
| Name | Meaning |
|---|---|
| X USER ID | The unique identifier of the user whose browser extensions are being retrieved. |
| Condition | A query string to filter the browser extensions based on specific criteria. |
| Skip | Number of records to skip in the result set, useful for pagination. |
| Limit | Maximum number of records to return, controlling the size of the response. |
| Order By | Field(s) by which to sort the returned browser extension records. |
Output
The node outputs JSON data representing the retrieved browser extensions. Each item in the output corresponds to a browser extension record matching the query parameters.
The structure typically includes details about each browser extension such as its name, version, installation date, and other metadata as provided by the Connect Secure API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Connect Secure API.
- An API authentication token or key credential must be configured in n8n to authorize requests.
- The node depends on the external Connect Secure service endpoint defined in the bundled OpenAPI specification.
Troubleshooting
- Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is correctly set.
- Invalid query condition syntax: If the condition string is malformed, the API may reject the request. Validate the query format.
- Pagination issues: Setting
skiporlimitincorrectly may result in empty or incomplete data sets. - Authentication errors: Verify that the API credentials are correct and have sufficient permissions.
- Network or API downtime: Check connectivity and the status of the Connect Secure API service if requests fail.
Common error messages will likely relate to HTTP status codes such as 400 (bad request), 401 (unauthorized), or 500 (server error). Reviewing the API response message can help pinpoint the issue.
Links and References
- Connect Secure API documentation (refer to your organization's internal API docs or the OpenAPI spec bundled with the node)
- n8n documentation on setting up API credentials and using HTTP request nodes for custom integrations