Why our integration directory admits what is not built

Go look at almost any B2B integration directory. Every logo looks equally official. Nothing tells you whether a given integration is a native connector somebody maintains, a Zapier template, or a slide in a roadmap deck.

We built ours the other way. Every partner on our directory carries one of six status labels, and two of them are admissions.

The six labels

Live — built, tested, available today, you can turn it on yourself.

Beta — running with real customers, not generally available, expect us in your setup.

Via Zapier — not a native connector. Works today through our Zapier app, which means you build and maintain a Zap and may need a paid plan for the volume.

Via webhook — not a native connector. Works today through our signed universal webhook, and someone technical on your side wires the endpoint.

Coming soon — not built, or built and waiting on a marketplace review we do not control.

Partner-only — the platform does not publish integration documentation. Access requires a partnership we have not signed.

Why the last two exist at all

Because the alternative is a directory that quietly implies coverage we do not have, and because a buyer who discovers the gap during implementation is right to be angry.

Some specifics we would rather tell you now:

• NGP VAN production keys can only be requested by you, the client, from inside VAN. A vendor cannot request one on a client’s behalf. Getting into VAN’s in-app integration dropdown also wants a security tier and an active-client count we do not have yet.
• Salesforce AppExchange requires a security review that costs $999 per submission attempt for paid apps, takes roughly six to nine weeks for a first pass, and which about half of first-time submissions fail.
• Zapier’s public directory requires a public launch, public API docs and a review, followed by an invite-only beta before the app goes fully public.
• i360, Numinar, and every voter file provider do not publish open documentation. That is a business-development track, not an engineering one.

None of that is unusual. All of it takes months. What is unusual is saying so on the page.

The strategic version of the argument

Honest labels are not just ethics, they are positioning. They let us claim broad “works with your stack” coverage truthfully on day one — through Zapier, webhook, CSV and embed — while we earn the native badges over the following cycle. A directory that lies has to keep lying. A directory that grades itself gets to show progress.