Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation, Find Timeline Activity Duplicates, is designed to identify duplicate timeline activities within a dataset. It is useful in scenarios where you want to clean up or analyze timeline data by detecting repeated or redundant entries. For example, if you have multiple timeline activities logged for the same event or action, this operation helps find those duplicates based on specified criteria.
Typical use cases include:
- Data deduplication before reporting or analytics.
- Identifying repeated user actions or events in a timeline.
- Cleaning up imported timeline data by removing duplicates.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information to include in the response: - 0: Only the primary timeline activity object.- 1: Primary object plus its directly related objects.- 2: Primary object, its related objects, and their related objects. |
| Data | JSON array specifying the fields or criteria used to find duplicates. Typically includes properties like the timeline activity name or other identifying attributes. |
| Ids | JSON array of IDs to limit the search scope to specific timeline activities. Can be used to target particular records when searching for duplicates. |
Output
The output is a JSON structure containing the found duplicate timeline activities according to the input criteria. The exact structure depends on the API response but generally includes:
- Details of each duplicate timeline activity found.
- Nested related objects depending on the selected depth level.
- Metadata about the duplicates such as counts or matching fields.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential to authenticate with the Twenty API service.
- The node uses the Twenty API base URL configured via credentials.
- The operation sends HTTP requests with JSON bodies and expects JSON responses.
Troubleshooting
- Invalid JSON in Data or Ids: Since these inputs expect JSON arrays, malformed JSON will cause errors. Ensure valid JSON formatting.
- Authentication Errors: Missing or invalid API credentials will result in authorization failures. Verify that the API key credential is correctly set up.
- Depth Parameter Misuse: Using unsupported depth values may lead to unexpected results or errors. Use only 0, 1, or 2.
- Empty Results: If no duplicates are found, the output will be empty. Confirm that the input criteria (Data and Ids) correctly specify the timeline activities to check.
Links and References
- Twenty API Documentation (general reference for the API endpoints)
- n8n Documentation on Creating Custom Nodes