What is your goal?
A new Tally form submission becomes a GitHub Issue in one of my organization repositories.
What is the problem & what have you tried?
Context:
I am the owner and admin of two GitHub organizations.
In Make, I connected GitHub using my personal GitHub account, which is also the owner of these organizations.
I tried to connect both with Github (add a token) and Github OAuth.
If I connect with Github OAuth, in GitHub, Make (Integromat) is visible under the my personal account’s OAuth App policy, and it shows as approved.
If I connect with Github (token), in Github the token is visible under one of my organization’s Fine-grained personal access tokens.
When I connect Make with Github OAuth, I can see that both my organizations have grants all the access they need to show repositories, both public and private.
Connection is successful but when I try to configure the GitHub “Create an Issue” module in Make:
- In the “owner” field I see just my personal account. Not my organizations.
- In the “repository” field I can see a list of repositories. I can see mostly my personal repo and 1 repo coming from one of my organization. No repo from the other organization.
Therefore, I cannot select the org repo where the issue should be created.
What I’ve already checked:
- I confirmed that at org level, Make is approved under Settings → Oauth App policy.
- Permissions shown there include:
- “Read org and team membership, read org projects”
- “Full control of private repositories”
- The organization’s third-party access policy is restricted, but Make is listed as approved.
Error messages or input/output bundles
No error.
Even though Make is approved in the organization, Make still cannot access or list the org repositories, making it impossible to create issues in the intended repo.
