Actions22
- App Actions
- Account Actions
- Channel Actions
- Message Actions
- Template Actions
- Contact Actions
- Tag Actions
- User Actions
- Team Actions
- Webhook Actions
Overview
The node implements integration with the Poli API, specifically supporting multiple resources and operations. For the Contact resource with the Create Contact operation, it allows users to create a new contact record in the Poli system.
This node is beneficial when automating customer relationship management workflows, such as adding new contacts from form submissions, syncing contacts from other systems, or bulk importing contacts into Poli.
Practical examples:
- Automatically creating a new contact in Poli when a lead fills out a web form.
- Adding contacts imported from a CSV file into Poli with detailed address and channel information.
- Associating tags and companies to contacts during creation for better segmentation.
Properties
| Name | Meaning |
|---|---|
| Account ID | The identifier of the account under which the contact will be created (required). |
| Name | Full name of the contact (required). |
| Phone (com DDD) | Contact's phone number including area code (required). |
| Contact's email address (optional). | |
| CPF/CNPJ | Brazilian individual or company tax identification number (optional). |
| Picture File ID | Optional. The file ID of an already uploaded picture to use as the contact's photo. |
| Tag ID | Optional. A tag UUID to associate with the contact for categorization. |
| Contact Account ID | Optional. Company UUID to relate the contact to a company. Sent inside companies[]. |
| Addresses | Optional. Multiple addresses can be added. Each address includes: Type (Headquarter, Billing, Shipping, Other), Country Code, Country, Postal Code, State, City, Street, Number, Neighborhood, Complement. |
| Channels | Optional. Multiple communication channels can be added. Currently supports phone numbers. |
Output
The node outputs JSON data representing the newly created contact object as returned by the Poli API. This typically includes the contact's unique identifier, provided fields, and any additional metadata assigned by the API.
If the API supports returning binary data (e.g., contact picture), it would be included accordingly, but this is not explicitly indicated in the provided source.
Dependencies
- Requires an API key credential for authenticating requests to the Poli API.
- The node depends on the Poli API being accessible and properly configured.
- No additional external services are required beyond the Poli API.
Troubleshooting
Common issues:
- Missing required fields like Account ID, Name, or Phone will cause errors.
- Invalid phone number format may result in API rejection.
- Providing incorrect or expired API credentials will cause authentication failures.
- If optional fields like Tag ID or Company UUID do not exist in the Poli system, the API might reject the request.
Error messages:
"Resource 'contact' not found"or"Operation 'create' not found"indicates misconfiguration of resource or operation parameters.- Authentication errors suggest checking the API key credential setup.
- Validation errors from the API usually specify which field is invalid or missing; ensure all required fields are correctly filled.
Links and References
- Poli API Documentation (general reference): https://docs.poli.com.br (example placeholder, replace with actual URL if known)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/