The docs on ‘documentation/v2’ are mostly legacy and for folks still on the legacy Web Builder. Most current policy and process docs should have an equivalent entry on https://platform.zapier.com/.
We’re hoping to finally get our docs consolidated, reorganized, and made nicely searchable in coming months.
as I’m already following new doc link to create a new integration.
Actually this new link have not clear requirements about what is needed to Launch.
For example
v2 states about first Launch:
1-Triggers: you can go with Launch with (2 or 3) triggers
2- Actions: you can go with Launch with (2 or 3) actions
3- Searches: This is optional (wecan skip in first Launch as this is an advanced)
Public release: you should have 10 Zap templates & 50 users. etc..
do I’ve to follow inherit requirements or any change in above requirements?
You can treat the v3 docs as complete and canonical.
To get your integration published (made available to everyone through the Zapier App Directory) with a beta banner, follow the guidance here https://platform.zapier.com/partners/integration-review-guidelines, as well as the automatic validation rules and warnings the platform tools will provide you with.
Limits on the numbers of triggers and actions for publishing are recommendations and best practices now, not strictly enforced rules - if that’s the crux of your question. It is still best to start with your strongest use cases and then augment and enhance your integration as you learn how your users are actually engaging with it.
To advance out of beta and get the benefits of the Zapier partner program, after you get published, take the next steps outlined here: https://platform.zapier.com/partners/lifecycle-planning#4-launch-with-the-partner-program.
If you have specific questions about your app and the program please reach out to the partner team at partners@zapier.com