Overview
The "TANSS Domains" node manages domain and DNS entries via the TANSS API. It supports creating, retrieving, listing, updating, and deleting domain records. This node is useful for automating domain management tasks such as provisioning new domains, updating domain details like expiry dates or nameservers, and cleaning up unused domains.
Practical examples:
- Automatically create a new domain record when onboarding a client.
- Retrieve domain information to verify status or registrar details.
- Update domain settings such as enabling/disabling auto-renewal or changing nameservers.
- List all domains managed under an account for reporting or auditing.
- Delete expired or unwanted domains programmatically.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform: createDomain, getDomain, listDomains, updateDomain, deleteDomain |
| API Token | API token from TANSS authentication used to authorize requests |
| Domain-ID | ID of the domain (required for getDomain, updateDomain, deleteDomain operations) |
| Domain-Felder | Collection of domain fields used for creation or update, including: |
| - Domain-Name: Domain name (e.g., example.com) | |
| - Unternehmen-ID: ID of the associated company | |
| - Registrar: Domain registrar | |
| - Ablaufdatum: Expiry date of the domain | |
| - Nameserver: Comma-separated list of nameservers | |
| - Status: Domain status with options: Active, Inactive, Expired, Locked | |
| - Auto-Renewal: Boolean flag for automatic renewal |
Output
The node outputs JSON data representing the response from the TANSS API for each operation:
- For createDomain and updateDomain, the output contains the created or updated domain object with its properties.
- For getDomain, the output contains detailed information about the specified domain.
- For listDomains, the output is an array of domain objects.
- For deleteDomain, the output typically confirms deletion success or returns related status.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL and a valid API token credential.
- The node expects credentials configured in n8n that provide the base URL for the TANSS API and the API token.
- Network access to the TANSS API service must be available.
Troubleshooting
- Missing Credentials Error: If no API token or credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure the API token is correctly set in the node credentials.
- Empty Fields on Create/Update: When creating or updating a domain, if no domain fields are provided, the node throws errors like "Keine Felder für die Domain-Erstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." Always provide at least one field to modify.
- Unknown Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
- API Request Failures: Errors during API calls include the operation name and the original error message. Check network connectivity, API token validity, and correct domain IDs.
- Invalid Domain-ID: For operations requiring a domain ID, ensure the ID is valid and exists in the TANSS system.
Links and References
- TANSS API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices