I am interested to register our AI bookkeeping tool as one of the verified app in app integrations section and have a landing page. Can you help me provide the steps I need to do?
Once its reviewed, may I know who is assigned to edit the landing page like for example when you search for an app and you see what the integrated app can do on Make?
I need more information about the design on the website.
To get your AI bookkeeping tool listed as a verified app, you’ll likely need to go through Make’s app development and verification process. I’d start by checking the developer documentation, creating the app integration, and preparing details like authentication setup, API documentation, and app description.
I would prepare the app description and listing material before submitting the app for review, not after.
The technical review and the public app page are connected. Make needs to understamd not only that the app works, but also what it does, who it is for, what modules are available, how authentication works, and what users should expect when they install it.
I would prepare at least:
short app description
main use cases
authentication details
module/action descriptions
required permissions or scopes
example scenarios
support contact
privacy policy and terms links
screenshots or brand assets if Make requests them
For an AI bookkeeping tool, I’d be especially careful with the wording around data handling, user permissions, and what the AI does versus what still needs human review. That will make the app page more trustworthy and may reduce uncertainty during review.
So my answer would be: prepare the material before submission, even if Make finalizes or formats the page later.
You probably do not need to restart the review or submit the app again.
First, ask your colleague for the existing “App review: [App name]” email thread. Then open the app’s App flow and Review tabs to check its current status. Make allows you to update an existing review form and add information by replying within that same email thread.
I would do three things now:
Confirm the current review stage.
Update the existing form with anything missing, especially the API documentation, current test-scenario links, support contact, categories, logo and service URL.
Reply in the review email thread with a short summary of what was added.
I would not create a second submission unless Make specifically asks for one.
If the app is approved, there is ongoing maintenance. Your team will have a development version for testing and a public version used by Make customers. Public changes must be tested first and reviewed by Make before release. Your team will also be responsible for API changes, reported bugs, user support and the API checkup Make requests every six months.
Yes, I can help you structure that process. What status do you currently see in the App flow or Review tab, and which materials were missing from the submission? With those two details, I can tell you the safest next step without disturbing the review already in progress.