Actions14
Overview
This node integrates with the Digital Ocean API to manage various resources such as accounts, domains, droplets, and events. Specifically, for the Domain - Get Many operation, it retrieves multiple domain records from a Digital Ocean account. This is useful when you want to list all domains associated with your Digital Ocean account or fetch a subset based on limits.
Common scenarios include:
- Automating domain inventory management.
- Synchronizing domain lists with other systems.
- Monitoring domain configurations in bulk.
For example, you could use this node to fetch all your domains and then process them to update DNS settings or audit domain statuses.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Digital Ocean API. Options: "Access Token", "OAuth2". |
| Return All | Whether to return all domain results or limit the number returned. Boolean (true/false). |
| Limit | Maximum number of domain results to return if "Return All" is false. Minimum value: 1. |
Output
The node outputs an array of domain objects in the json output field. Each object represents a domain retrieved from Digital Ocean and contains details such as domain name, creation date, and IP address associated with the domain.
If "Return All" is true, the node returns all available domains; otherwise, it returns up to the specified limit.
The node does not output binary data.
Dependencies
- Requires a valid Digital Ocean API authentication token, either via an access token or OAuth2 credentials.
- The node uses internal helper functions to make HTTP requests to Digital Ocean's REST API endpoints.
- No additional external dependencies beyond the Digital Ocean API and n8n environment are required.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Requesting both "Return All" as false and setting a very high limit may result in partial data due to API pagination limits.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials in n8n.
- If the node throws an error about exceeding limits, reduce the "Limit" value or enable "Return All".
- API rate limiting errors may occur if too many requests are made in a short time; implement delays or retries.