Integration Directory Addition or Removal
Software companies publish a page listing every platform they connect to, keep it current because customers depend on it, and never think of it as disclosure. It is. A connector only exists because enough paying customers demanded it, so an integration directory is a published map of the installed base's technology stack, maintained at the company's own expense. The changes are more informative still. A new listing is engineering work that was scoped, built, documented and launched, and it usually appears before the press release. A withdrawn listing is a partnership that ended or a platform that lost relevance, often with a stated sunset date. Status labels covering coming soon, beta, early access, legacy and deprecated expose the pipeline and the stalls. Attribution between native and partner-built reveals who carries the work. Clustering of additions around one vendor or category reveals a deliberate bet. Avina crawls these directories, diffs them against prior snapshots, classifies every addition, promotion, demotion and removal, and surfaces the ecosystem decisions a company has made but not yet talked about.
Why an Integration Catalogue Is a Published Customer Stack
Integration directories are built for prospects and maintained for customers. Read as data, they answer questions that account research normally cannot. They name the platforms the installed base runs. Connectors are expensive to build and more expensive to support, so no company builds them on speculation. Each listing exists because a material share of paying customers asked for it, which makes the directory a published, continuously curated inventory of the technologies those customers use. For anyone selling into the same category, that is a free segmentation of an entire customer base's stack. Additions are roadmap disclosure with a date. A new connector is the visible end of a process that included prioritisation, engineering, documentation, security review and partner coordination. It confirms that a partnership exists, indicates which customer segment drove it, and typically goes live before any announcement, which means the directory is the earliest public evidence of the relationship. Removals are the scarce half of the dataset and usually the more actionable one. Withdrawing a connector means a partnership lapsed, a counterpart platform lost relevance to the customer base, the integration became unmaintainable, or the other vendor changed its API, pricing or terms. Deprecation notices frequently state the reason and the sunset date, which both explains the decision and gives every affected customer a deadline. Status labels expose the pipeline and its failures. Listings marked coming soon, beta or early access are commitments made before delivery, and the date a listing is promoted to generally available marks completion. A connector that has sat in beta for twelve months is a partnership that stalled, a resourcing problem or a technical dependency nobody could resolve, and that is a conversation worth having with either side. Attribution distinguishes ownership from courtesy. A native connector is built and supported by the company itself. A partner-built or third-party listing places the burden elsewhere and often signals a lower-priority relationship. A listing that moves from partner-built to native is a clear statement that the integration became strategically important, and the reverse is a quiet withdrawal of investment. Scope changes measure depth. An integration that gains write access, new object types, additional authentication scopes or bidirectional sync has deepened. One whose description narrows or whose supported scopes shrink has been cut back. The detail pages carry this information explicitly because customers need it. Clustering reveals intent. Several connectors added in one category inside a quarter, or multiple connectors to one vendor's product family, is a funded bet on a segment or an alliance. The same number of additions scattered across unrelated categories is routine maintenance. The pattern distinguishes strategy from upkeep. The counterpart list is a partner map. A directory with forty listings names forty vendors with overlapping customer bases, each one a candidate for co-selling, referral or technology partnership, with the strength of the relationship inferable from attribution, status and depth. And absence is as legible as presence. A company with deep coverage of one category and nothing in an adjacent one has a gap, and its customers are usually asking about that gap in public community threads and public roadmap boards where the demand can be counted.
How Does Avina Detect and Classify Catalogue Changes?
Avina, an AI-powered GTM platform, treats an integration directory as a structured dataset with a revision history. Directories are discovered and mapped. Avina locates integration and app directory pages, connector catalogues, partner marketplaces and technology partner pages from sitemaps, navigation and documentation, and records the category taxonomy and filter structure the company uses to organise its ecosystem. Listings are captured in full. Avina records each listing's name, counterpart vendor, category, description, status label, build attribution, supported scopes and objects, setup requirements, plan or tier restrictions, any additional fee, and the content of its detail and documentation pages. Snapshots are diffed over time. Avina compares each crawl against prior snapshots and records additions, removals, promotions from coming soon or beta to generally available, demotions to legacy or deprecated with any stated sunset date, description and scope changes, attribution changes between native and partner-built, and category reorganisations. Patterns are measured rather than described. Avina tracks the rate at which listings are added, clustering of additions around a single vendor or category, the proportion of listings in beta and how long they have been there, the ratio of native to partner-built connectors, and whether removals are isolated or represent the exit of a whole category. Mutuality is checked. Avina compares the company's listing against the counterpart platform's own marketplace, since an integration published on both sides indicates a real partnership while a one-sided listing often indicates an unsanctioned or unsupported connector. Intent is corroborated from outside the directory. Avina cross-references job listings for partnerships, technology alliances, integrations engineering, solutions engineering, platform and ecosystem roles, partnerships leadership appointments, press releases and blog posts announcing alliances, joint case studies, webinars and co-marketing content, conference and marketplace participation, developer platform and public API launches or deprecations, cloud marketplace listings and co-sell programme entry, and funding and product launch activity that explains an ecosystem push. Demand for missing connectors is quantified. Avina reads public community forums, public roadmap boards and support threads for integration requests, which turns an absent category from an observation into a measured gap with named customers asking for it. The counterpart platforms are extracted as their own dataset. Avina builds the list of vendors a company integrates with, weighted by attribution, status and depth, which serves both as a technographic read on the installed base and as a partnership map. Suppression removes what is not a decision. Cosmetic page redesigns and template changes, category renames that move listings without changing them, pagination and crawl artefacts that make listings appear or disappear spuriously, listings restored within days after an error, and directories that are simply unmaintained with no changes of any kind are all filtered out. Each account is enriched with the listings added, removed, promoted and demoted, the counterpart vendors involved, status and attribution changes, any stated sunset date, clustering and velocity measures, mutual listing status, the measured demand for missing connectors, corroborating hiring and announcement evidence, and concurrent signals, then matched against your ICP filters.
What Happens When an Integration Directory Signal Fires?
Avina scores on what the change says about priority and about the counterpart relationship. A cluster of additions in one category inside a quarter, backed by partnerships or integrations hiring, scores at the top of the model, because an ecosystem programme is funded and under way. A connector promoted from beta to generally available scores highly, since a partnership has just become real and both sides have launch motion behind it. A connector removed or marked deprecated with a stated sunset date scores highly, because every customer using it has a deadline and the counterpart vendor has lost a channel. A competitor's listing appearing in the directory scores highly for competitive awareness, and a competitor's listing being removed scores highly as an opening. A listing that has sat in beta for many months scores as a stalled partnership worth approaching from either side. A measured gap, where a category has no listings and public roadmap requests for it are accumulating, scores as a build or partnership opportunity with evidence attached. Attribution moving from partner-built to native scores as a deepening commitment. Cosmetic redesigns, category renames, crawl artefacts and unmaintained directories are suppressed. Timing follows the catalogue. The window immediately after a new listing goes live is the strongest, because launch coordination, co-marketing and enablement are being arranged and the integration is still being hardened. The period after a deprecation notice but before its sunset date is a dated migration window affecting a known set of customers. A promotion out of beta is a launch moment with marketing attached. A cluster of additions marks the start of an ecosystem programme that will need partner operations, enablement and measurement it does not yet have. A directory that stops changing for several quarters is a programme that lost its owner, which often coincides with a partnerships departure. And a counterpart platform's own API change, pricing change or deprecation creates an externally imposed deadline across every company that lists a connector to it, which can be worked as a cohort. Routing depends on which side of the ecosystem the conversation belongs to. The partnerships, alliances or business development lead owns the relationship and the directory itself and is the usual counterpart. The integrations or platform engineering manager owns how connectors are built and maintained and feels the cost of a growing catalogue. The product manager for the platform or ecosystem owns prioritisation and the gaps. The solutions or sales engineering lead owns how integrations are demonstrated and sold and is the first to hear when one is missing. The developer relations lead owns the documentation and developer portal where listings are described. The chief revenue officer owns co-sell motion where a cluster of additions indicates a channel strategy. And the counterpart vendor named in an added or removed listing is itself an account, on the opposite side of the same event. Contacts are enriched with verified emails, phone numbers and LinkedIn profiles across partnerships, product, platform engineering and revenue leadership. Reps receive a Slack alert naming the company, the listings added or removed, the counterpart vendors, the status and attribution changes, any sunset date, the clustering and velocity measures, the measured demand for missing connectors, and the recommended angle. Salesforce and HubSpot records carry the catalogue diff, so outreach references the specific connector rather than a general ecosystem observation. Qualified accounts can be auto-enrolled into sequences built on the change: a launch message where a connector has just gone live or come out of beta, a migration message where a deprecation has a sunset date, an opening message where a competitor's listing was removed, a stalled-partnership message where a listing has been in beta for months, a gap message where public roadmap demand for a missing category is measurable, an operations message where catalogue growth has outpaced partner tooling and enablement, and a standard Outreach or Salesloft sequence with the connector, counterpart vendor and change date populated into the messaging.
Start Tracking Integration Catalogues With Avina
A company's integration directory is a public list of the platforms its customers run, and every addition or removal is a partnership decision made before the announcement. Activate this signal in Avina's Signals Library to read ecosystem strategy from the catalogue. Every plan includes a 7-day free trial with no credit card required.