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 create a custom date range resource. Specifically, the "Create Date Range" operation allows users to define a new date range that can be used in Adobe Analytics reports and queries. This is useful for automating the management of date ranges within analytics workflows, enabling dynamic reporting periods without manual intervention.
Common scenarios include:
- Automating report generation for specific custom time frames.
- Creating reusable date ranges for consistent analysis across multiple reports.
- Managing date ranges programmatically as part of larger data processing pipelines.
Example: A marketing analyst could use this node to create a date range representing the last quarter dynamically, then use that date range in subsequent report requests.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier for the Adobe Analytics company (or global company) under which the date range will be created. |
| Query Parameters | Optional parameters to filter or modify the request. Includes many options such as approved, classifiable, componentId, endDate, startDate, limit, locale, sortDirection (ASC/DESC), and more. These allow fine-tuning of the request context but are mostly unused for creating a date range. |
| Request Body | JSON object containing the details of the date range to create. This should follow the Adobe Analytics API specification for a date range definition. |
Note: The full list of query parameters is extensive and covers many filtering and pagination options relevant to other resources; for the "Create Date Range" operation, typically only the requestBody is essential.
Output
The output is a JSON array where each item corresponds to the response from the Adobe Analytics API after creating the date range. The structure depends on the API's response but generally includes:
- The newly created date range's configuration and metadata.
- Status information about the creation request.
If the API returns no content, the node outputs a status code message indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an Adobe Analytics API credential configured in n8n, including:
- Client ID
- Client Secret
- Scope
- The node authenticates via OAuth client credentials flow to obtain an access token before making API calls.
- Network access to Adobe Analytics API endpoints (
https://analytics.adobe.ioandhttps://ims-na1.adobelogin.com).
Troubleshooting
- Missing Credentials: If the Adobe Analytics API credentials are not set or incomplete, the node throws an error "Missing Adobe Analytics API Credentials".
- Access Token Retrieval Failure: If the OAuth token cannot be obtained, the node throws "Failed to retrieve access token".
- Required Parameter Missing: For this operation, if the required parameters like
globalCompanyIdorrequestBodyare missing or empty, the node may fail or return an error from the API. - API Errors: Any errors returned by the Adobe Analytics API are wrapped and reported with the prefix "Error calling Adobe Analytics API", including the original message and stack trace if available.
- Invalid JSON in Request Body: The
requestBodymust be valid JSON; otherwise, parsing errors will occur.
To resolve issues:
- Ensure all required credentials and parameters are correctly configured.
- Validate the JSON structure of the request body.
- Check network connectivity and API permissions.
- Review error messages for specific API response details.
Links and References
- Adobe Analytics API Documentation
- Adobe IMS Authentication
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)