Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Person → Get

AI-generated

Overview

This node integrates with the Twenty CRM API to manage various CRM resources such as people, companies, opportunities, tasks, notes, and more. Specifically, for the Person resource with the Get operation, it retrieves a single person record by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching detailed information about a specific contact or lead in your CRM by their ID.
  • Automating workflows that require retrieving person data before performing further actions like sending emails or updating records.
  • Integrating CRM data into other systems or dashboards by pulling individual person records on demand.

Example use case: You have an automation that triggers when a new email arrives, and you want to fetch the corresponding person's details from Twenty CRM using their ID to personalize your response.

Properties

Name Meaning
ID The unique identifier of the person record to retrieve. This is required for the Get operation.

Output

The node outputs JSON data representing the person record retrieved from the Twenty CRM API. The structure corresponds to the API's person object, typically including fields such as name, emails, phones, job title, city, and other person-related attributes.

If multiple items are processed, each output item contains one person record in its json field.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Twenty CRM API.
  • The node uses the base API URL configured in the credentials.
  • Network access to the Twenty CRM REST API endpoint is necessary.

Troubleshooting

  • Invalid ID error: If the provided ID does not exist or is malformed, the API may return an error. Ensure the ID is correct and corresponds to an existing person record.
  • Authentication errors: If the API key credential is missing or invalid, requests will fail. Verify that the credential is properly set up and has sufficient permissions.
  • JSON parsing errors: Not applicable for the Get operation but relevant if using other operations with JSON input.
  • API rate limits or connectivity issues: Network problems or API limits can cause request failures. Check network connectivity and API usage quotas.

Links and References

Discussion