Actions28
Connector → Get Many
AI-generatedOverview
This node interacts with the Twingate GraphQL API to manage connectors. Specifically, the 'Get Many' operation for the 'Connector' resource retrieves multiple connector records from the Twingate system. It supports fetching all connectors or limiting the number of results returned. This is useful for workflows that need to list or process multiple connectors, such as inventory management, reporting, or synchronization tasks.
Use Case Examples
- Retrieve all connectors in the Twingate network to generate a report of active connectors.
- Fetch a limited number of connectors to display in a dashboard or to process in batches.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all connector results or only up to a given limit |
| Limit | Maximum number of connector results to return when 'Return All' is false |
Output
JSON
id- Unique identifier of the connectorname- Name of the connectorremoteNetworkid- ID of the remote network associated with the connectorname- Name of the remote network associated with the connector
state- Current state of the connector
Dependencies
- Requires Twingate API credentials including network name and API token for authentication.
Troubleshooting
- Common issues include authentication errors due to invalid or missing API tokens. Ensure the Twingate API credentials are correctly configured.
- GraphQL errors may occur if the query is malformed or if the API endpoint is unreachable. Verify network connectivity and API endpoint URL.
- If the 'Return All' option is enabled but the results are incomplete, check for pagination handling and API limits.
Links
- Twingate GraphQL API Documentation - Official documentation for Twingate's GraphQL API, useful for understanding available queries and mutations.