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 perform various operations related to analytics data management and retrieval. Specifically, for the Project resource with the Get Project operation, it retrieves the configuration details of a specific project within an Adobe Analytics workspace.
Use cases include:
- Fetching detailed configuration information about a particular project by its ID.
- Integrating Adobe Analytics project data into workflows for reporting or automation.
- Validating project existence or inspecting project metadata before further processing.
Example scenario: You want to automate the retrieval of project configurations to sync them with another system or to audit project settings regularly.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier of the company in Adobe Analytics under which the project exists. This is required to scope the API request correctly. |
| Project ID | The unique identifier of the project you want to retrieve. This is mandatory for the Get Project operation. |
| Query Parameters | Optional parameters to refine or filter the request. These include a wide range of filters such as date ranges, pagination controls, sorting options, and flags to include/exclude certain types of data. See below for some examples: |
| - Approved | Whether to include calculated metrics that are approved (boolean). |
| - Classifiable | Whether to include classifiable dimensions (boolean). |
| - Limit | Maximum number of results to return (number). |
| - Locale | Locale setting for the response (string, e.g., "en_US"). |
| - Page | Page number for paginated results (number, base 0). |
| - Sort Direction | Sort direction, either ascending ("ASC") or descending ("DESC"). |
| - Sort Property | Property name to sort by (string). |
| ... | Many other optional query parameters exist to filter or customize the request, including filtering by owner ID, segmentable flag, report suite ID, and more. |
Output
The output is a JSON object representing the retrieved project configuration from Adobe Analytics. It contains all relevant project details as returned by the Adobe Analytics API, such as project metadata, settings, and possibly nested objects describing components of the project.
If the API returns no content (HTTP 204), the node outputs a status message indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for Adobe Analytics with client ID, client secret, and scope configured.
- The node obtains an OAuth access token via Adobe's IMS token endpoint using client credentials flow.
- Network access to
https://analytics.adobe.ioandhttps://ims-na1.adobelogin.comis necessary. - Proper permissions on the Adobe Analytics account to read project configurations.
Troubleshooting
- Missing Credentials Error: If the node throws "Missing Adobe Analytics API Credentials," ensure that the API key credential is properly set up and linked in n8n.
- Failed to Retrieve Access Token: Indicates issues with client ID/secret or network problems. Verify credentials and connectivity.
- "Project ID is required" Error: For the Get Project operation, the Project ID must be provided; otherwise, the node will throw this error.
- API Errors: Any errors returned by Adobe Analytics API are wrapped and reported with messages like "Error calling Adobe Analytics API: ...". Check the error message and stack trace for details.
- Empty or Unexpected Response: If the response is empty or not JSON, verify the correctness of input parameters and API availability.