Actions15
Overview
This node interacts with the Instantly API to manage accounts, campaigns, and leads. Specifically for the Account - Get Many operation, it retrieves multiple account records from the Instantly platform. This is useful when you want to fetch a list of accounts for reporting, synchronization, or bulk processing purposes.
Common scenarios include:
- Retrieving all accounts to analyze user data or export it.
- Fetching a limited number of accounts for display in dashboards or further automation steps.
- Integrating Instantly account data into other systems by pulling many accounts at once.
Example: You might use this node to get up to 50 accounts (or all accounts) and then filter or process them downstream in your workflow.
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 if "Return All" is set to false. Minimum value is 1. |
Output
The output is a JSON array where each item represents an account object as returned by the Instantly API. Each account object typically includes fields such as email, full name, and other account-specific details.
No binary data is output by this operation.
Example output structure (simplified):
[
{
"email": "user1@example.com",
"fullName": "User One",
"id": "account_id_1",
...
},
{
"email": "user2@example.com",
"fullName": "User Two",
"id": "account_id_2",
...
}
]
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- The node makes HTTP requests to Instantly endpoints under
/accounts. - No additional environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Authentication errors due to invalid or missing API credentials.
- Rate limiting or API quota exceeded errors from Instantly.
- Network connectivity problems preventing API calls.
Error messages:
"401 Unauthorized": Check that the API key credential is correctly configured and valid."429 Too Many Requests": You have hit the API rate limit; try reducing request frequency or contact Instantly support."404 Not Found": Unlikely for getMany but may indicate endpoint changes or misconfiguration.
To resolve errors, verify API credentials, ensure network access, and confirm that the Instantly API service is operational.
Links and References
- Instantly API Documentation (for detailed API endpoints and data structures)
- n8n documentation on HTTP Request Node (conceptual reference for API calls)