Actions22
Contact → Get
AI-generatedOverview
This node interacts with the InNotes CRM API to retrieve detailed information about a specific contact by its ID. It is useful in scenarios where you need to fetch contact details for further processing, display, or integration with other systems. For example, you might use this node to get contact information before sending a personalized email or updating a contact record in another database.
Use Case Examples
- Retrieve contact details by providing the Contact ID to fetch the contact's name, LinkedIn key, location, current company, picture URL, tags, and status.
- Use the node to get contact information as part of a workflow that enriches customer data or triggers follow-up actions based on contact attributes.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The ID of the contact to retrieve. This is a required string input used to specify which contact's details to fetch. |
| Options | Additional options to control batch processing such as batch size and timeout between batches to avoid rate limiting. |
Output
JSON
id- The unique identifier of the contact.name- The name of the contact.linkedin_key- The LinkedIn key associated with the contact.linkedin_user- The LinkedIn user identifier of the contact.location- The location of the contact.current_company- The current company where the contact works.picture_url- URL to the contact's picture.tags- Tags associated with the contact.status_id- The status identifier of the contact.
Dependencies
- InNotes API credentials (API key and base URL)
Troubleshooting
- Ensure the Contact ID provided is valid and exists in the InNotes CRM system to avoid 'not found' errors.
- Check that the InNotes API credentials are correctly configured and have the necessary permissions to access contact data.
- If rate limiting errors occur, adjust the batch size and timeout between batches options to reduce request frequency.
Links
- InNotes API Documentation - Official API documentation for InNotes CRM, useful for understanding available endpoints and data structures.
