Twingate icon

Twingate

Interact with Twingate GraphQL API

Actions28

Access Request → Get

AI-generated

Overview

This node interacts with the Twingate GraphQL API to manage access requests. Specifically, the 'Get' operation for the 'Access Request' resource retrieves detailed information about a single access request by its ID. This includes the request's reason, timestamp, status, and associated user and resource details. It is useful for workflows that need to fetch and process access request data, such as auditing, approval processes, or monitoring access control.

Use Case Examples

  1. Retrieve details of a specific access request by its ID to review the request before approval.
  2. Fetch access request information to log or notify relevant stakeholders about access activities.

Properties

Name Meaning
Access Request ID The ID of the access request to retrieve. This is a required string input used to specify which access request to fetch.

Output

JSON

  • id - The unique identifier of the access request.
  • reason - The reason provided for the access request.
  • requestedAt - The timestamp when the access request was made.
  • status - The current status of the access request (e.g., pending, approved, rejected).
  • user
    • id - The unique identifier of the user who made the access request.
    • email - The email address of the user who made the access request.
    • firstName - The first name of the user who made the access request.
    • lastName - The last name of the user who made the access request.
  • resource
    • id - The unique identifier of the resource for which access was requested.
    • name - The name of the resource for which access was requested.

Dependencies

  • Twingate API key credential with network name and API token

Troubleshooting

  • Ensure the Access Request ID is correct and exists in the Twingate system to avoid 'not found' errors.
  • Verify that the Twingate API credentials (network name and API token) are correctly configured and have sufficient permissions to query access requests.
  • GraphQL errors returned by the API will be included in the error message; check the message for details on what went wrong.
  • If the node fails with HTTP status errors, verify network connectivity and API endpoint correctness.

Links

Discussion