What integrations are present
Nora connects the workspace to GitHub, GitLab, and Vercel. The current integration model is token-based: you add provider credentials in settings and Nora uses those credentials for repository and deployment actions from inside the workspace.
How to connect GitHub or GitLab with a personal access token
Open Settings, go to Integrations, choose GitHub or GitLab, and paste a personal access token with the repository scopes your workflow needs. Save the token, then return to the workspace and refresh integration data if needed. After connecting, verify access by opening provider-backed views such as repository metadata, pull or merge request actions, and branch targets from the current workspace.
How to connect Vercel with a personal access token
Open Settings, go to Integrations, add a Vercel personal access token, and save it. Then link the active workspace to the correct Vercel project. Once linked, use the Vercel panel to view deployment status, inspect recent runs, and trigger redeploys without leaving Nora.
How to use connected integrations in a normal flow
After agents or terminals produce branch changes, open the review flow and create a pull request or merge request from the current branch to the intended base branch. Nora keeps these actions scoped to the focused workspace and branch, so verify the source branch, base branch, and change diff before submission. For deployable projects, use the Vercel panel after review to confirm deployment state or trigger a redeploy for the linked project.
Token management and troubleshooting
If an integration suddenly fails, first confirm the token is still valid and has not expired or been revoked. Then check that the token includes required scopes for the action you are trying to run. If provider access still fails, replace the token in Settings and refresh workspace integration state. For teams, use least-privilege tokens and rotate them on a regular schedule to limit blast radius.