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 on Adobe Analytics resources. Specifically, for the Date Range resource and the Get Date Range operation, it retrieves the configuration details of a specific date range defined in Adobe Analytics. This is useful when you want to programmatically access predefined or custom date ranges to use them in reports or analytics workflows.
Common scenarios include:
- Fetching a particular date range's settings to apply consistent time frames across multiple reports.
- Automating report generation by dynamically retrieving date ranges.
- Integrating Adobe Analytics date ranges into broader data pipelines or dashboards.
Example: You might use this node to get the details of a "Last 30 Days" date range by specifying its ID, then use that information to run reports constrained to that period.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier of the Adobe Analytics company (or global company) under which the date range exists. Required for all operations except some user discovery operations. |
| Date Ranges ID | The unique identifier of the date range to retrieve. Required for the Get Date Range operation to specify which date range to fetch. |
| Query Parameters | A collection of optional parameters to filter or modify the request. For the Get Date Range operation, these can include various filters and options such as approved, limit, startDate, endDate, locale, etc. |
The Query Parameters collection supports many options, including but not limited to:
approved(boolean): Whether to include only approved calculated metrics.limit(number): Maximum number of results to return.startDate/endDate(string): Define date boundaries for filtering.locale(string): Locale setting, e.g., "en_US".useCache(boolean): Whether to use caching for faster requests.- Various filters like
dimension,event,segmentFilter,sortDirection, etc.
For the Get Date Range operation, typically only the Date Ranges ID and Global Company ID are essential; query parameters may be used for additional filtering if supported.
Output
The node outputs the JSON response from the Adobe Analytics API corresponding to the requested date range. The structure generally includes:
- Metadata about the date range such as its ID, name, start and end dates.
- Configuration details defining the scope and rules of the date range.
- Any additional properties returned by the Adobe Analytics API for the date range resource.
If the API returns no content (e.g., 204 status), the node outputs a JSON object indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for Adobe Analytics with appropriate permissions.
- The node authenticates using OAuth client credentials flow to obtain an access token.
- Network access to Adobe Analytics API endpoints (
https://analytics.adobe.io/api/) is required. - Proper configuration of the Adobe Analytics API credentials in n8n is necessary before use.
Troubleshooting
- Missing Credentials Error: If the node throws "Missing Adobe Analytics API Credentials," ensure that the Adobe Analytics API credentials are configured correctly in n8n.
- Access Token Retrieval Failure: Errors like "Failed to retrieve access token" indicate issues with client ID, secret, or scope. Verify these values and network connectivity.
- Required Parameter Missing: For the Get Date Range operation, if the Date Ranges ID is empty, the node will throw an error stating it is required. Provide a valid ID.
- API Errors: Any other errors from the Adobe Analytics API will be wrapped and reported with the message "Error calling Adobe Analytics API" along with the original error message. Check the API documentation and your input parameters.
- Empty or Unexpected Response: If the response is empty or not JSON, verify the correctness of the request URL and parameters.