TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node interacts with the Twenty API to retrieve detailed information about a specific Task Target by its unique identifier. It is useful when you need to fetch a single Task Target object, optionally including related nested objects up to a specified depth. Typical use cases include integrating task management data into workflows, displaying task details in dashboards, or synchronizing task targets with other systems.

Properties

Name Meaning
Id The unique identifier of the Task Target object to retrieve. This is required.
Depth Determines how much related nested data to include in the response:
- 0: Only the primary Task Target object information.
- 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 deep).

Output

The node outputs JSON data representing the requested Task Target object. The structure includes the main Task Target fields and, depending on the Depth parameter, may also include nested related objects up to two levels deep. This allows flexible retrieval of associated data without additional requests.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Twenty API.
  • The node expects the base URL domain to be configured in the credentials.
  • Uses the Twenty API version 1.0.3 OpenAPI specification for request construction.

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 correct Task Target ID is provided.
  • Authentication errors: If the API key or domain credentials are missing or invalid, authentication will fail. Verify that the credentials are correctly set up in n8n.
  • Depth parameter misuse: Providing an unsupported depth value might cause unexpected results or errors. Use only 0, 1, or 2 as allowed.
  • Network issues: Connectivity problems with the Twenty API endpoint can cause timeouts or failures. Check network access and API availability.

Links and References

Discussion