Provider setup · Google Business Profile
Qualify, reapply, then enable the connector.
Hoozh fails closed: Gmail OAuth can remain available, but the Business Profile connector cannot start until Google approves the Cloud project and the project quota confirms that approval.
Eligibility comes before polish
Google requires the applicant to manage a verified, active Business Profile for at least 60 days. A profile is eligible only for a real business that meets customers in person at a staffed location or travels to customers. Do not create a virtual office, mailbox, or fake storefront for Hoozh. If Hoozh is online-only, use an eligible client profile that the applicant is genuinely authorized to manage.
Stop gate: do not reapply with zero businesses
Open Business Profile Manager with the exact Google account that will submit the API request. If it shows zero businesses, stop. First obtain written permission from a real restaurant pilot, have its owner add that business-domain Google account as an owner or manager, and wait until the verified profile has been active for at least 60 days. Creating a Hoozh listing to bypass this gate would violate Google's eligibility rules because Hoozh is an online software service.
Prove the Business Profile is eligible
- The profile is verified and has remained active for at least 60 days.
- The application email is listed as an owner or manager on that exact profile.
- Business Profile Manager visibly lists that profile for the application account before the API form is opened.
- The restaurant owner has given Hoozh written authorization, retains ownership, and can revoke access.
- The location makes real in-person customer contact or is a legitimate service-area business.
- The profile is not a virtual office, mailbox, lead-generation listing, brand-only listing, or duplicate.
Make the profile complete and consistent
- Use the real-world business name exactly as it appears on the website, signage, stationery, and invoices.
- Set one accurate primary category, precise address or service area, current hours, and a direct business-controlled phone number.
- Use https://hoozh.app as the official website only if the profile is genuinely for Hoozh; a client profile must use that client's own website.
- Add truthful photos and business details. Never add keywords, taglines, or a fake address to the profile name.
Use the completed Hoozh website evidence
- Homepage: https://hoozh.app/
- Company identity: https://hoozh.app/about
- Direct contact: https://hoozh.app/contact and hello@hoozh.app
- Human support: https://hoozh.app/support
- Privacy and terms: https://hoozh.app/privacy and https://hoozh.app/terms
- Public integration authorization and data use: https://hoozh.app/integrations/google-business-profile
- Before reapplying, the applicant must confirm Hoozh's exact legal operator name and any real business address. Never add an unverified corporate suffix or location to the website or application.
- Keep the verified Hoozh name, domain, logo, company description, contact email, and applicant identity consistent everywhere.
Reapply with the correct project and account
- Select the one Google Cloud project that will own the Business Profile API access.
- Create a dedicated Business Profile OAuth client using GOOGLE_BUSINESS_PROFILE_CLIENT_ID and GOOGLE_BUSINESS_PROFILE_CLIENT_SECRET; do not reuse the Gmail client.
- Create or confirm the Google Business Profile Organization account.
- Use a business-domain email that is also an owner or manager of the qualifying profile.
- Record the applicant's verified legal operator name exactly as it appears on official records. If it has not been confirmed, stop instead of guessing.
- Choose “Application for Basic API Access” and explain that Hoozh lets each owner manually sign in to manage only profiles they own or are authorized to manage.
- Be ready to provide a live demo account if Google requests one.
Prove approval before production enablement
- In Google Cloud Console, 0 QPM means the project is not approved; keep the Hoozh connector disabled.
- A 300 QPM quota confirms approval. Then enable the Business Profile APIs Google lists for the project.
- Only after the quota is 300 QPM, set GOOGLE_BUSINESS_PROFILE_API_APPROVED=true in Railway.
- Confirm the dedicated Business Profile OAuth client and callback are configured before enabling the flag.
- Run the Hoozh integration health check, connect a real owner profile, verify location selection, import reviews, and test disconnect/reconnect.
Copy-ready application explanation
Business purpose: Hoozh is restaurant operations software. A restaurant owner or an expressly authorized manager signs in with Google and chooses only a Business Profile they own or manage. Hoozh imports that profile's review history so the restaurant can read reviews and prepare owner-controlled replies in one workspace.
Control and consent: Hoozh does not claim, create, transfer, or edit a Business Profile without the business owner's action. The business owner retains ownership and can disconnect Hoozh or revoke Google access at any time.
Data handling:Access is tenant-scoped to the restaurant location selected by the authorized user. OAuth tokens are encrypted. Hoozh does not scrape Google or sell Business Profile data. It never uses one restaurant's data for another restaurant.
Website evidence:The developer identity, product purpose, direct contact, support, privacy policy, and terms are published on hoozh.app. The qualifying restaurant profile continues to use the restaurant's own website and real-world identity.
Hoozh production gate
The connector route, callback, review sync, customer cards, and health screen all use the same explicit approval flag. Missing or rejected approval cannot be mistaken for a working integration. Gmail OAuth remains separate.