Google Business OAuth blocked by unverified EveryFeed app (403 access_denied)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- authentication
Research direction
Start by reproducing the flow through EveryFeed -> Connections -> Connect a channel -> Google My Business, then inspect the OAuth failure details for the business.manage scope and the https://everyfeed.ai/integrations/social/gmb callback. Done means users can reach Google's consent screen and return to EveryFeed to connect the channel, or receive a documented tester-access workaround.
Written by the indexing model from the issue text.
Description
Google Business OAuth verification failure
Summary
Connecting Google My Business through EveryFeed fails at Google OAuth with Error 403: access_denied because the EveryFeed app has not completed Google verification.
Reproduction
- Open EveryFeed -> Connections -> Connect a channel.
- Choose Google My Business.
- Select a Google account and complete Google sign-in and 2-Step Verification.
- Google redirects to an access-denied page instead of the consent screen.
Observed error
Google displays:
Access blocked: everyfeed.ai has not completed the Google verification process
The app is currently being tested, and can only be accessed by developer-approved testers.
Error 403: access_denied
The requested OAuth scope is https://www.googleapis.com/auth/business.manage.
The callback URL is https://everyfeed.ai/integrations/social/gmb.
Expected behavior
The Google Business Profile authorization should reach the consent screen and return to EveryFeed so the channel can be connected.
Impact
Google Business Profile is advertised as a supported channel, but the connection cannot be completed for a normal account unless it is added as an approved test user. This prevents publishing to the channel and may affect users during the paid/trial experience.
Request
Please either complete Google OAuth verification or add a documented tester-access/workaround path. Please also clarify whether affected users should receive a billing adjustment while Google Business Profile cannot be connected.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VoltAgent/everyfeed-agent
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in VoltAgent/everyfeed-agent
Similar issues
-
bug screener-policy
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ditto-assistant/ditto-subnet#3067 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kube-tarian/sigrun#202 ·
-
/submit, /my-list, and /onboarding return 500 when Supabase isn't configuredPossibly taken @Aryan-Techie claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Your-Voldemort/StudentStack#127 · 1 comment ·
Maintainers usually reply within 1 day
-
[🐛 Bug]: OAuth2 Proxy logout leaves the Auth.js session active when switching usersPossibly taken @juanbailon claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
keephq/keep#6888 · 1 reaction ·
Maintainers usually reply within 1 day
-
docs: four SECURITY.md statements no longer match the code (allowed hosts, body cap, OIDC, ACLs)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
akitaonrails/ai-memory#1561 ·
Maintainers usually reply within 1 day