Welcome: lead with the apps workspaces connect, ranked from usage; no-key demos opt-in - #889
Merged
Merged
Conversation
…-key demos opt-in
/welcome showed a fixed list of apps and, below it, the keyless starter pack
with three demos ticked. In the first days of October the demos were installed
by 20-78 new workspaces each and called by 0-2, while taking the trial's
connector slots from the app the user came for. Telegram was set up by 149
workspaces and worked for 133; Etsy 155 and 62; Odoo 20 and 17.
- GET /api/adapters/popular-connectors ranks catalog adapters by how many
workspaces had a successful call on them in the last 30 days (aggregate
counts, at least 3 workspaces, keyless ones left out), cached for an hour,
filled from a fallback list on a quiet deployment or if the query fails.
The EXISTS goes through tool_invocations(connector_id, created_at): 33 ms on
the cloud.
- Each card says what the setup asks for ("Bot token", "Sign in · Keystring
and Shared secret") and marks apps the workspace already has.
- The starter pack has nothing preselected, moves below the marketplace and
custom-API cards, and says each demo counts as a connector on the plan.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
From today's funnel check (cloud, connectors created in the last 30 days):
The keyless starter pack was ticked by default:
/welcomeshowed it 81 times today and it was installed twice, and the demos it does install take the trial's connector slots from the app the user came for.What
GET /api/adapters/popular-connectors: catalog adapters ranked by workspaces with at least one successful call in the last 30 days. Aggregate counts only, minimum 3 workspaces, keyless adapters left out (they stay in the demos), installable-here filter, cached 1 h, filled fromPOPULAR_FALLBACKon a quiet deployment or if the query fails. TheEXISTSusestool_invocations(connector_id, created_at): 33 ms on the cloud DB (checked read-only with a statement timeout). Today it would return telegram-bot, etsy, odoo, jev, weclapp, woocommerce, bitrix24, buchhaltungsbutler./welcome: the app cards come from that endpoint, labelled "What new workspaces connect most". Each card says what the setup asks for (Bot token,Sign in · Keystring and Shared secret, from the adapter's required variables without the tokens a sign-in fills in) and shows "Already added". If the ranking fails, it falls back to a fixed list resolved from the catalog.Tests
popularConnectorscases (ranking + fill, keyless excluded, setup labels, installed flag, hourly cache, query failure); starter-pack spec updated (no preselection). adapters specs: 53/53.starter-pack.spec.ts+ 3 new cases for the popular cards (labels and links, placed above the demos, fallback when the ranking fails); 26/26 with onboarding-redirect and card-trial. Also guards a non-array catalog response, which crashed the page in the onboarding spec's mocks.Measure after deploy
starter_pack_viewed/starter_pack_installedand new workspaces' first successful call within 24 h, about a week after deploy.