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 interacts with the Twenty API to retrieve detailed information about a single connected account by its unique identifier. It is useful when you need to fetch specific data about a connected account, such as user profile details or linked service information, within an automation workflow. For example, you might use this node to get the full details of a user's connected social media account or third-party integration in order to process or display that data further downstream.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the connected account object to retrieve. This is required to specify which account to find. |
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary connected account data. - 1: Primary data plus directly related objects. - 2: Primary data, directly related objects, and their related objects (two levels deep). |
Output
The node outputs JSON data representing the connected account object retrieved from the API. The structure includes the main connected account fields and, depending on the Depth property, may also include nested related objects up to two levels deep. This allows workflows to access comprehensive account details and associated entities in one call.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Twenty API.
- The base URL for the API is configured dynamically from the provided credentials.
- The node uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Missing or invalid Id: If the
Idproperty is empty or incorrect, the API will likely return an error indicating the object was not found. Ensure the correct connected account ID is provided. - Authentication errors: If the API key credential is missing or invalid, authentication failures will occur. Verify that the API key is correctly set up in n8n credentials.
- Depth parameter misuse: Providing an unsupported depth value could cause unexpected results or errors. Use only 0, 1, or 2 as specified.
- Network or API downtime: Connectivity issues or API outages will result in request failures. Check network connectivity and API status if errors persist.
Links and References
- Twenty API Documentation (Assumed official API docs for reference)
- n8n documentation on Using API Credentials