Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Company → Get
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources such as companies, people, opportunities, tasks, notes, and more. Specifically for the Company - Get operation, it retrieves a single company record by its unique ID.
Common scenarios where this node is useful include:
- Fetching detailed information about a specific company stored in Twenty CRM.
- Integrating company data retrieval into automated workflows, e.g., enriching customer profiles or triggering follow-up actions based on company details.
- Using the company data in other systems by pulling it dynamically during workflow execution.
Example: You have a workflow that triggers when a new deal is created, and you want to fetch the associated company's details to personalize communications or update another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the company record to retrieve. This is required for the "Get" operation. |
Output
The node outputs the retrieved company data as JSON. The structure corresponds to the company object returned by the Twenty CRM API, typically including fields like company name, domain, employee count, address, and other metadata.
If multiple items are processed, each output item contains the JSON data for one company record.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Twenty CRM API.
- The node expects the base API URL and authentication details to be configured in the credentials.
- Network access to the Twenty CRM REST API endpoint is necessary.
Troubleshooting
- Invalid ID error: If the provided company ID does not exist or is malformed, the API will return an error. Verify the ID value before running the node.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to read company records.
- JSON parsing errors: Not applicable for the "Get" operation but relevant if using custom JSON fields in other operations.
- Rate limits or network issues: The node may fail if the API rate limit is exceeded or if there are connectivity problems. Implement retry logic or check network status.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and data structures)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP request behavior)