Overview
This node integrates with the Clint API to manage contacts. It supports operations such as listing all contacts, retrieving a specific contact by ID, creating new contacts, updating existing contacts, deleting contacts, and managing tags associated with contacts. This node is useful for automating contact management workflows, such as syncing contacts from Clint to other systems, bulk updating contact information, or organizing contacts with tags.
Use Case Examples
- List all contacts to display in a dashboard.
- Create a new contact when a form is submitted.
- Update contact details based on external data changes.
- Delete contacts that are no longer needed automatically after a certain period.
Properties
| Name | Meaning |
|---|---|
| Operation | Specifies the action to perform on contacts, such as list, get, create, update, delete, add tags, or remove tags. |
| Contact ID | The unique identifier of the contact, required for operations that target a specific contact (get, update, delete, add tags, remove tags). |
| Name | The name of the contact, used when creating or updating a contact. |
| DDI | The international dialing code for the contact's phone number, used when creating or updating a contact. |
| Phone | The phone number of the contact, used when creating or updating a contact. |
| The email address of the contact, used when creating or updating a contact. | |
| Tag IDs | Comma-separated list of tag IDs to add or remove from a contact. |
Output
JSON
json- The response data from the Clint API for the performed operation, which may include contact details, lists of contacts, or success/error messages.
Dependencies
- Requires an API token credential for the Clint API, used for authorization in API requests.
Troubleshooting
- Common issues include invalid or expired API tokens causing authorization errors, which can be resolved by updating the credentials.
- Incorrect or missing Contact ID for operations that require it will result in errors; ensure the Contact ID is provided when needed.
- Malformed tag IDs (e.g., incorrect formatting or non-existent tags) can cause tag management operations to fail; verify tag IDs are correct and properly formatted as comma-separated values.
- Network or API endpoint issues may cause request failures; check network connectivity and Clint API status.
Links
- Clint API Documentation - Official documentation for the Clint API, useful for understanding available endpoints and data structures.