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 allows users to create multiple timeline activities in bulk. Timeline activities represent events or actions that are aggregated and displayed on a timeline, useful for tracking progress, updates, or historical records within an application or workflow.
Common scenarios include:
- Logging multiple user actions or system events at once.
- Bulk importing activity data into a timeline view.
- Automating the creation of event records from batch data sources.
For example, a project management tool could use this operation to add several task updates simultaneously to a project's activity timeline.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary timeline activity objects. - 1: Primary objects plus their directly related objects. - 2: Includes related objects of those related objects as well. |
| Body | JSON object representing the timeline activities to create. This should contain the aggregated or filtered event data to be displayed on the timeline. Example default: { "name": "Timeline Activity name" }. |
Output
The output contains a JSON field with the created timeline activities. The structure reflects the requested depth level, including nested related objects depending on the Depth property value.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the external Twenty API service.
- The node uses the Twenty API base URL configured via credentials.
- The request content type is JSON, and responses are expected in JSON format.
Troubleshooting
- Invalid JSON in Body: If the
Bodyproperty contains malformed JSON, the node will fail parsing it. Ensure valid JSON syntax. - Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify the API key and domain configuration.
- Depth Parameter Misuse: Providing unsupported values outside 0, 1, or 2 may result in unexpected responses or errors.
- API Rate Limits: Bulk creation might hit rate limits; consider batching requests if errors occur.
Links and References
- Twenty API Documentation (generic placeholder link)
- n8n documentation on Creating Custom Nodes