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 manage and update projects within an Adobe Analytics workspace. Specifically, the "Update Project" operation allows users to modify the configuration of an existing project by specifying its ID and providing updated data in the request body.
Common scenarios where this node is beneficial include:
- Automating updates to project settings or metadata without manual intervention.
- Integrating Adobe Analytics project management into broader workflows, such as CI/CD pipelines or reporting automation.
- Synchronizing project configurations across multiple environments or teams.
For example, a user might update a project's name, description, or other attributes programmatically after receiving new input from another system or user interface.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier for the company in Adobe Analytics under which the project exists. Required for all operations except some user discovery operations. |
| Project ID | The unique identifier of the project to update. This is required for the Update Project operation to specify which project to modify. |
| Query Parameters | Optional parameters to filter or modify the request. Includes many options such as pagination, filtering by date range, sorting, limits, locale, and various flags controlling the inclusion of specific data aspects. |
| Request Body | A JSON object containing the updated project configuration details. This is the main payload sent to Adobe Analytics to apply changes to the specified project. |
The Query Parameters collection includes many optional fields that can be used to refine the request or control returned data, such as:
limit: Maximum number of results to return.page: Page number for paginated results.sortDirection: Sort order (ASC or DESC).startDate/endDate: Date range filters.- Various boolean flags like
approved,favorite,reportable, etc. - Filters by IDs, names, tags, event types, and more.
These parameters provide fine-grained control over the request but are generally optional for the update operation.
Output
The node outputs the response from the Adobe Analytics API after attempting to update the project. The output is a JSON array where each item corresponds to the API response for one input item.
- If the API returns JSON data, it is parsed and returned as JSON.
- If the API returns a string, the node attempts to parse it as JSON; if parsing fails, it returns the raw text.
- If no content is returned (HTTP 204), the node outputs a status message indicating "204 No Content".
The output structure depends on the Adobe Analytics API response for the update operation, typically including the updated project details or confirmation of success.
Dependencies
- Requires an API key credential for Adobe Analytics with client ID, client secret, and scope configured.
- The node authenticates using OAuth2 client credentials flow to obtain an access token before making API calls.
- Network access to
https://ims-na1.adobelogin.com/ims/token/v3for token retrieval andhttps://analytics.adobe.io/api/{globalCompanyId}for API requests. - Proper permissions on the Adobe Analytics account to update projects.
Troubleshooting
- Missing Credentials Error: If the API key credential is not set or incomplete, the node will throw an error about missing credentials. Ensure the Adobe Analytics API credentials are properly configured.
- Access Token Retrieval Failure: If the node cannot get an access token, it throws an error. Check client ID, client secret, and scope values.
- Required Parameter Missing: For updating a project, the Project ID must be provided. Omitting it causes an error.
- API Errors: Any errors returned by the Adobe Analytics API (e.g., invalid JSON in request body, insufficient permissions) will be wrapped and reported by the node. Review the error message and stack trace for details.
- Invalid JSON in Request Body: The request body must be valid JSON. Invalid JSON will cause parsing errors.
- Network Issues: Connectivity problems to Adobe endpoints will cause request failures.
Links and References
- Adobe Analytics API Documentation
- Adobe IMS Authentication
- n8n Documentation - Creating Custom Nodes
This summary covers the static analysis of the node's execute method focused on the "Project" resource and "Update Project" operation, describing its inputs, outputs, dependencies, and common troubleshooting points.