Actions28
Connector → Get
AI-generatedOverview
This node interacts with the Twingate GraphQL API to perform various operations on different resources such as connectors, users, groups, remote networks, access requests, and resources. Specifically, for the Connector resource with the Get operation, it retrieves detailed information about a connector by its ID. This is useful for scenarios where you need to fetch connector details for monitoring, auditing, or integration purposes within an automated workflow.
Use Case Examples
- Retrieve a connector's details by its ID to display or log its current state and associated remote network.
- Use the node to fetch connector information as part of a larger automation that manages network configurations or access controls.
Properties
| Name | Meaning |
|---|---|
| Connector ID | The ID of the connector to retrieve details for. This is a required string input used to specify which connector to fetch. |
Output
JSON
id- The unique identifier of the connector.name- The name of the connector.remoteNetworkid- The ID of the remote network associated with the connector.name- The name of the remote network associated with the connector.
state- The current state of the connector.createdAt- The timestamp when the connector was created.updatedAt- The timestamp when the connector was last updated.
Dependencies
- Twingate GraphQL API
Troubleshooting
- Ensure the Connector ID is correctly provided and exists in the Twingate system to avoid 'not found' errors.
- Check that the API token credential for Twingate is valid and has the necessary permissions to query connector data.
- GraphQL errors returned by the API will be surfaced; review error messages for issues like invalid queries or permission problems.
Links
- Twingate GraphQL API Documentation - Official documentation for the Twingate GraphQL API used by this node.