Actions28
Access Request → Reject
AI-generatedOverview
This node interacts with the Twingate GraphQL API to manage access requests, specifically allowing users to reject an access request by its ID. It is useful in scenarios where access requests need to be programmatically managed, such as automating security workflows or integrating access control with other systems. For example, it can be used to automatically reject access requests that do not meet certain criteria or to handle bulk access request rejections based on external triggers.
Use Case Examples
- Reject an access request by providing its ID to deny access to a resource.
- Automate the rejection of access requests that fail compliance checks.
Properties
| Name | Meaning |
|---|---|
| Access Request ID | The ID of the access request to reject, required to identify which access request to reject. |
Output
JSON
id- The ID of the rejected access request.status- The status of the access request after rejection, indicating it has been rejected.
Dependencies
- Twingate GraphQL API
Troubleshooting
- Ensure the Access Request ID is correct and exists; otherwise, the API will return an error.
- Check that the API token credential is valid and has the necessary permissions to reject access requests.
- If the node throws a GraphQL error, review the error message for details such as invalid ID or permission issues and correct accordingly.
Links
- Twingate GraphQL API Documentation - Official documentation for the Twingate GraphQL API used by this node.