Overview
Phinite’s GitHub predefined tool lets workspace assistants call GitHub APIs through DevStudio after you save a connection under Integrations → Predefined tools. ‘Manage repositories, issues, and pull requests: create tickets, comment,Predefined tools require a saved connection before they appear in Graph Studio’s tool picker. See Predefined Tools in GraphStudio.
What this integration enables
- Automate workflows using this predefined tool from agent graphs
- Connect once under Integrations and reuse across assistants
- Enable individual subtools per agent in Graph Studio
Required credentials
- See integration configuration fields in Phinite
Setup steps
- Create a GitHub personal access token or GitHub App with repository permissions.
- Log into your Phinite workspace at app.phinite.ai
- Navigate to Integrations → Predefined tools
- Select GitHub
- Click + Add Configuration
- Enter the credential fields listed above
- Select assistants that should use this connection
- Click Save Configuration
Configure in Graph Studio
- Open an agent in Graph Studio
- Select the agent node → Tools tab → Add a new tool
- Choose GithubTool (or search for GitHub)
- Select your saved connection or add a new one
- Enable the subtools your workflow needs and save
Predefined tools
Phinite provides 11 subtools for GitHub:- Search Repositories: Search for repositories on GitHub
- List Repositories: List all repositories for the authenticated user
- Get Repository: Get details of a specific repository
- Create Repository: Create a new repository on GitHub
- Create Issue: Create an issue in a repository
- Get Pull Request: Get details of a specific pull request
- Create Pull Request: Create a new pull request in a repository
- List Issues: List issues for a repository with pagination
- Get File Content: Get the content of a file in a repository
- Create File: Create a new file in a repository
- Search Code: Search for code in GitHub repositories
Documentation & resources
- Official documentation:
https://docs.github.com/en/rest - Phinite documentation: GitHub
Notes
- Store API keys and tokens securely; many providers show secrets only once
- Use separate connections for Dev, UAT, and Prod environments where possible
- Test with a minimal subtool call after saving credentials

