Adobe Analytics icon

Adobe Analytics

Use the Adobe Analytics API

Overview

This node integrates with the Adobe Analytics API to perform various operations related to Adobe Analytics resources. Specifically, for the Project resource and the Validate Project Definition operation, it allows users to validate a project definition JSON against Adobe Analytics' expected schema and rules. This is useful when managing workspace projects programmatically to ensure that project configurations are correct before creation or update.

Common scenarios include:

  • Validating new or updated project definitions in automated workflows.
  • Ensuring project configuration correctness to avoid errors during deployment.
  • Integrating project validation as part of CI/CD pipelines for analytics projects.

Example: A user can input a JSON project definition and use this node to validate it via Adobe Analytics API before creating or updating the project, preventing invalid configurations from being applied.

Properties

Name Meaning
Global Company ID The unique identifier of the company in Adobe Analytics under which the project exists. Required for all operations except "usersDiscoverMeGet".
Query Parameters A collection of optional parameters to filter or modify the request. Includes many options such as approved, classifiable, componentId, endDate, limit, locale, page, pagination, sortDirection, etc. These allow fine-tuning of requests but may not be relevant for project validation specifically.
Request Body The JSON object representing the project definition to be validated. This should contain the project configuration details according to Adobe Analytics specifications.

Note: For the Validate Project Definition operation, the key property is the Request Body, which contains the project definition JSON to validate.

Output

The node outputs the response from the Adobe Analytics API after attempting to validate the project definition. The output is a JSON array where each item corresponds to the API response for each input item processed.

  • If the validation is successful, the output will typically contain confirmation or details about the validity of the project definition.
  • If there are validation errors, the output will include error messages describing what is wrong with the project definition.
  • In case of no content returned by the API, the node outputs a status code message like "204 No Content".

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for Adobe Analytics API authentication.
  • Uses OAuth client credentials flow to obtain an access token from Adobe Identity Management System (IMS).
  • Requires network access to Adobe Analytics API endpoints (https://analytics.adobe.io and https://ims-na1.adobelogin.com).
  • The node expects valid Adobe Analytics API credentials configured in n8n.

Troubleshooting

  • Missing Credentials Error: If the node throws "Missing Adobe Analytics API Credentials," ensure that the Adobe Analytics API credentials are properly set up in n8n.
  • Failed to Retrieve Access Token: Indicates issues with client ID, client secret, or scope. Verify these values and their permissions.
  • Required Parameter Missing: For the Validate Project Definition operation, if the request body is empty or malformed, the API may return errors. Ensure the JSON project definition is correctly formatted and provided.
  • API Errors: Any API call failure will throw an error with the message prefixed by "Error calling Adobe Analytics API." Check the detailed error message and stack trace for specifics.
  • Network Issues: Connectivity problems to Adobe endpoints will cause failures; verify network access and proxy settings if applicable.

Links and References


This summary focuses on the Project resource and the Validate Project Definition operation as requested, based on static analysis of the provided source code and properties.

Discussion