An integration page can establish a useful approach without establishing a finished connector. Classify the setup before comparing vendors.
Ask for the executable surface
A connector has a concrete setup: an endpoint, package, install screen or documented configuration. Check the available actions, authentication and supported host.
Sendblue and Blooio publish MCP setup guides. Linq’s official Claude Code channel supplies a client-specific plugin path. Those are more specific than an app logo on a catalog page.
Keep beta scope visible
A beta connection can be usable while still carrying narrower scope or activation requirements. Miss Blue’s GoHighLevel guide explicitly identifies beta opt-in, location binding and new direct-message synchronization.
It also excludes existing history and group import. Preserve those limits in your team’s acceptance plan rather than describing a complete migration.
Treat a recipe as implementation work
A guide mapping CRM records to an API or webhook is a custom build path unless a shipped connector is separately established. Name who writes and maintains the adapter.
Miss Blue’s HubSpot, Make and n8n pages describe such patterns. Connection Map labels them as build guides and does not infer marketplace installation from their titles.
Validate the exact account
Authentication success is one check. The chosen account must also permit the number, message direction and production features used by the connection.
Request a demonstration using owned data, then inspect both source and destination records. Our directory is documentation-backed research, not a report that every path has been installed.