Actions24
- Account Actions
- Analytics Actions
- Campaign Actions
- Lead Actions
Overview
This node integrates with the Instantly API to retrieve multiple account records. Specifically, the "Get Many Accounts" operation fetches a list of accounts from the Instantly platform, allowing users to either return all available accounts or limit the number of results returned.
Common scenarios for this node include:
- Synchronizing account data from Instantly into other systems.
- Bulk processing or analysis of account information.
- Automating workflows that require access to multiple user accounts managed in Instantly.
For example, a marketing automation workflow might use this node to pull all accounts and then segment them based on email domains or names before sending targeted campaigns.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all account results or only up to a specified limit. |
| Limit | The maximum number of account results to return when "Return All" is set to false. |
Output
The node outputs an array of JSON objects representing Instantly accounts. Each object typically contains fields such as email, first name, last name, and possibly other account-related metadata as provided by the Instantly API.
No binary data output is indicated in the source code.
Example output structure (simplified):
[
{
"email": "user@example.com",
"first_name": "John",
"last_name": "Doe",
"id": "12345"
},
...
]
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- The node uses HTTP requests to Instantly's REST endpoints (e.g.,
/api/v2/accounts). - No additional external dependencies beyond the Instantly API and n8n's standard HTTP request capabilities.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network errors or timeouts when connecting to the Instantly API.
- Receiving empty results if no accounts exist or if filters exclude all entries.
Error messages:
- Errors during dropdown loading (e.g., fetching accounts) log messages like "Error fetching email accounts for dropdown".
- If the API request fails, the node throws an error with the message from the API response.
Resolutions:
- Verify that the API key credential is correctly configured and has sufficient permissions.
- Check network connectivity and API endpoint availability.
- Confirm that the Instantly account actually contains accounts to retrieve.
Links and References
- Instantly API Documentation (hypothetical link; replace with actual)
- n8n documentation on creating custom nodes
- n8n community forums for troubleshooting API integrations