Actions5
- Mail Actions
- Contact Actions
Overview
This node is designed to interact with a contact management system, specifically to retrieve lists of contacts associated with an account. It is useful in scenarios where you need to fetch and process groups or segments of contacts for marketing campaigns, customer relationship management, or data synchronization tasks. For example, you might use this node to get all contact lists from an email marketing platform before sending targeted emails.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "API Token" or "Bearer Token". |
| Account ID | The identifier of the account whose contact lists you want to retrieve. This can be provided directly or via an expression. |
Output
The node outputs JSON data representing the contact lists retrieved from the specified account. Each item in the output typically contains details about a contact list such as its name, ID, and possibly other metadata depending on the external service's response structure.
No binary data output is indicated by the source code or properties.
Dependencies
- Requires an external API service that manages contacts and contact lists.
- Needs proper authentication credentials (either an API token or a bearer token) configured in n8n.
- The user must provide a valid Account ID to specify which account's contact lists to fetch.
Troubleshooting
- Invalid Authentication: If the API token or bearer token is incorrect or expired, the node will fail to authenticate. Ensure the credentials are valid and have necessary permissions.
- Missing or Incorrect Account ID: Providing an invalid or empty Account ID will result in no data or an error. Verify the Account ID is correct and corresponds to an existing account.
- API Rate Limits or Service Downtime: External API limits or outages may cause failures. Check the service status and consider implementing retries or error handling.
- Unexpected Response Structure: If the external API changes its response format, the node might not parse the data correctly. Keep the integration updated accordingly.
Links and References
- Refer to the documentation of the external contact management API for details on authentication methods and contact list retrieval endpoints.
- n8n documentation on how to configure API credentials and use expressions for dynamic input values.