Actions57
- Annotation Actions
- Calculated Metric Actions
- Component Meta Data Actions
- Add Tags
- Delete Multiple Tags
- Delete One Tag
- Delete Shared Component
- Get Shared Component
- Get Tag
- List Shared Components by the User
- List Shared Components to the User
- List Tag Names
- List Tags
- Save Tags
- Search Shared Components
- Search Tags for Multiple Components
- Search Tags for One Component
- Share Component with Multiple User
- Share Component with One User
- Date Range Actions
- Dimension Actions
- Metric Actions
- Project Actions
- Report Actions
- Segment Actions
- Usage Log Actions
- User Actions
Overview
This node integrates with the Adobe Analytics API to retrieve and manage user-related data. Specifically, the "User" resource with the "Discover Me" operation fetches information about the current user's company context from Adobe Analytics. This is useful for scenarios where you want to programmatically discover details about the authenticated user's company environment, such as company ID, permissions, or other metadata related to the user's account.
Practical examples include:
- Automatically retrieving the current user's company information to configure subsequent API calls dynamically.
- Validating user access or permissions before running reports or managing analytics components.
- Integrating Adobe Analytics user context into workflows that require user-specific data insights.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The identifier of the global company in Adobe Analytics. (Required except when using the "Discover Me" operation) |
| Query Parameters | A collection of optional parameters to filter or modify the request. Includes many options such as: Approved, Classifiable, Component ID(s), Component Type, Curated RSID, Dimension, Date Range (Start/End), Event filters, Favorite, Pagination controls, Locale, Search terms, Sort options, User ID, and more. These parameters allow fine-tuning of the data retrieved from the API. |
| Request Body | JSON object used for operations that require a request payload (not applicable for "Discover Me" operation). |
Note: For the "Discover Me" operation specifically, no additional parameters are required.
Output
The output is a JSON array containing the response from the Adobe Analytics API for the "Discover Me" endpoint. This typically includes detailed information about the current user's company context, such as company identifiers, user roles, permissions, and other metadata relevant to the authenticated user.
If the API returns binary data (not typical for this operation), it would be included accordingly, but this operation primarily returns JSON data.
Dependencies
- Requires an Adobe Analytics API credential with client ID, client secret, and scope configured in n8n.
- The node obtains an OAuth2 access token by authenticating against Adobe's IMS token service.
- Network access to
https://ims-na1.adobelogin.comfor token retrieval andhttps://analytics.adobe.iofor API requests.
Troubleshooting
- Missing Credentials: If the Adobe Analytics API credentials are not set or incomplete, the node will throw an error indicating missing credentials.
- Access Token Retrieval Failure: Errors during token acquisition (e.g., invalid client ID/secret or network issues) will cause the node to fail with a message about failing to retrieve the access token.
- Invalid or Missing Parameters: For operations other than "Discover Me," missing required IDs (like annotationId, calculatedMetricId, etc.) will result in errors specifying which parameter is required.
- API Errors: Any HTTP or API-level errors are caught and reported with descriptive messages including the original error message and stack trace if available.
- Empty or Unexpected Responses: If the API returns empty or non-JSON responses, the node attempts to parse or return raw text; users should verify API availability and request correctness.