TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node allows you to retrieve a single Timeline Activity object from the Twenty API by specifying its unique identifier. It is useful when you need detailed information about a specific timeline event or activity, such as fetching details of a user action, system event, or any logged activity within the timeline.

Common scenarios include:

  • Displaying detailed information about a particular timeline event in a dashboard.
  • Fetching related nested data for an activity to analyze its context.
  • Integrating timeline activity data into other workflows or reports.

For example, you might use this node to get the details of a timeline activity with ID 12345 and include related objects up to two levels deep to understand the full context of that activity.

Properties

Name Meaning
Id The unique identifier of the timeline activity object you want to retrieve. This is required.
Depth Determines how much related nested data to include in the response:
- 0: Only the primary timeline activity object.
- 1: The primary object plus its directly related objects (no further nesting).
- 2: The primary object, its directly related objects, and their related objects (two levels of nesting).

Output

The node outputs a JSON object representing the requested timeline activity. Depending on the selected depth, this JSON may include nested related objects providing additional context about the activity.

If binary data were involved (not indicated here), it would typically represent attachments or media related to the timeline activity, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the Twenty API.
  • The node uses the base URL configured in the credentials to send requests.
  • No additional external dependencies are indicated beyond the Twenty API access.

Troubleshooting

  • Missing or invalid Id: If the Id property is empty or incorrect, the API will likely return an error indicating the object was not found. Ensure the Id is correct and corresponds to an existing timeline activity.
  • Invalid depth value: Using a depth outside the allowed range (0, 1, 2) may cause unexpected results or errors. Use one of the provided options.
  • Authentication errors: If the API key or domain is misconfigured, authentication will fail. Verify credentials and endpoint settings.
  • Network issues: Connectivity problems can prevent the node from reaching the API. Check network access and proxy settings if applicable.

Links and References

Discussion