IT Glue icon

IT Glue

Utilize the IT Glue API
Join our community

Actions34

Overview

This node integrates with the IT Glue API to retrieve domain information. Specifically, the "Domain - Get" operation fetches domain records from IT Glue based on optional filters and sorting preferences. It is useful for scenarios where you need to query domain data programmatically, such as syncing domain details into other systems, auditing domain inventories, or automating domain-related workflows.

Practical examples include:

  • Retrieving all domains associated with a specific organization.
  • Fetching a limited number of recent domains sorted by creation or update date.
  • Filtering domains by their unique ID or organization ID to get precise results.

Properties

Name Meaning
Return All Whether to return all matching domain results or limit the number of returned items.
Limit Maximum number of domain results to return (only applicable if "Return All" is false).
Filters Criteria to filter the domains:
• Domain ID — filter by a specific domain's ID.
• Organization ID — filter domains belonging to a particular organization.
Sort How to sort the returned domains:
• Created (Ascending) — oldest first
• Created (Descending) — newest first
• None — no sorting applied
• Updated (Ascending) — oldest update first
• Updated (Descending) — newest update first

Output

The node outputs JSON data representing the retrieved domain records. Each item in the output corresponds to a domain object fetched from IT Glue, containing its properties as provided by the API.

If multiple domains are returned, they are output as an array of JSON objects. The structure aligns with IT Glue's domain resource schema, typically including fields like domain ID, name, organization association, creation and update timestamps, and other metadata.

The node does not output binary data.

Dependencies

  • Requires an active connection to the IT Glue API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node uses standard HTTP headers for JSON API communication (Accept: application/json and Content-Type: application/vnd.api+json).

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing invalid filter values (e.g., non-numeric IDs) may result in errors or empty responses.
    • Requesting too many results without pagination or limits might lead to timeouts or rate limiting.

  • Error Messages:

    • Authentication errors typically indicate issues with the API key or token; verify credentials and permissions.
    • Validation errors may occur if filter parameters are malformed; ensure numeric IDs are used where expected.
    • Rate limit exceeded errors suggest too many requests in a short period; implement delays or reduce request frequency.

Links and References

Discussion