Connections are planned, not live
The website does not request access to any of these services. There are no working OAuth connections, API tokens, or publishing integrations in this build.
The list below explains the intended sequence, so the product pages do not imply that every platform is already supported.
First-workflow priorities
Google Search Console: proposed read-only source for page and query performance. Access should be limited to an approved property and the information the task requires.
GitHub: proposed source of website content and version history. The initial implementation path is a branch and pull request, not a direct write to the production branch.
Cloudflare: the hosting and deployment environment for the current 2bcome website. The planned agent workflow would use the site’s existing deployment process after a reviewed change is merged.
Google Analytics: a potential read-only measurement source when the agreed experiment needs it. It should not become a required connection for a task that does not use it.
Later publishing platforms
WordPress, Webflow, and Shopify are potential later integrations. Each needs its own scoped permissions, draft workflow, validation, and rollback behavior.
A logo on a marketing page is not evidence that a connector works. We will change the status only after a connection can be demonstrated for a defined workflow.
Other data tools
Commercial search and research tools may be useful for particular tasks. Access, account ownership, quotas, and third-party costs need to be agreed before including them in a pilot.
No tool is assumed to be included in an unannounced subscription price.
Before an integration can be called available
The proposed release checklist includes authentication, revocation, scoped access, error handling, rate limits, and a test of the actual end-to-end job.
For a publishing connection, it also needs a way to inspect the proposed change and recover from a bad release.
Explore the first workflow or describe the platform you use.