Add Selector

Add Selector

Dynamic selectors expose option metadata while a workflow or connector is being configured. Every remote selector executes through the authorized selectors.execute application operation; the browser never resolves credentials or calls a provider directly.

Read the shared boundary

Before editing, read:

• apps/sim/lib/selectors/types.ts
• apps/sim/lib/selectors/manifest.ts
• apps/sim/lib/selectors/context.ts
• apps/sim/lib/selectors/server/types.ts
• apps/sim/lib/selectors/server/registry.ts
• apps/sim/hooks/queries/selectors.ts

Then read the nearest existing selector attachment and the block, trigger, or connector declaration that will consume the key.

Classify the selector

• provider-server: contacts an external provider or uses provider credentials.
• internal-server: reads protected Sim data through an existing authorized application use case.
• local: pure browser-safe data with no protected data, credentials, references, or network I/O.

Add every key to the browser-safe manifest in lib/selectors/manifest.ts. SelectorKey derives from that manifest; do not maintain a second union. Manifest entries contain data only: allowed context, readiness, scope kinds, list/search/detail capabilities, and stale time. Do not import provider SDKs, credentials, server helpers, or attachment functions into the manifest.

Build context from active values

Declare dependsOn on the consuming sub-block or connector field. The shared context builder sends only declared, active dependencies:

• Canonical basic/advanced pairs contribute the active value under their canonical key.
• Action and trigger modes contribute only fields active on that surface.
• Exact environment references such as {{GMAIL_CREDENTIAL_ID}} remain unresolved in the browser.
• Runtime block-output references are not selector context.
• Embedded environment interpolation such as https://{{HOST}}/path is unsupported.
• impersonateUserEmail is the one explicit compatibility hint projected when the manifest allows it, even when it is absent from dependsOn.

Add a new SelectorContextKey only when the value is a real, reusable selector dependency. Allow it explicitly on each relevant manifest entry. Never send a full block or connector configuration.

Add the server attachment

For provider-server, add the service's attachment map under apps/sim/lib/selectors/server/providers/ and include it in the exhaustive server registry. For internal-server, add the attachment in apps/sim/lib/selectors/server/internal.ts. Local keys use the exhaustive browser-safe registry in apps/sim/lib/selectors/client/local.ts and never enter the server registry. A provider attachment declares:

• For stored credentials, a credential policy with the exact context field and trusted serviceIds. Raw-connection selectors instead validate the connection material projected from their allowed context and bind it to a deliberate destination policy.
• Destination policy: fixed, credential-bound, or user-controlled.
• A list/detail adapter that explicitly projects id, label, and allowlisted scalar meta.

Stored credentials must pass actor-use, workspace, and provider/service binding checks. Do not trust a provider, service, operation kind, origin, or module name supplied by the browser.

Choose the destination policy deliberately:

• fixed: provider origin is code-defined.
• credential-bound: origin/account/site comes from, or is verified against, the authorized credential.
• user-controlled: the user selects the destination. Hidden use-only authentication requires an explicit security policy; do not combine it with an arbitrary destination by default.

Reuse or extract a server-only provider listing primitive. A provider route exists only when it has a non-selector caller, and then it is a thin caller of that primitive; there are no selector-only routes or contracts. Never import a route handler or make an internal HTTP request from an attachment.

The attachment must return normalized selector results only. It must never deliberately or wholesale echo selector context, and hidden/server-only resolved material, credential IDs, tokens, and authentication secrets must never cross the response boundary. Browser-known literals and viewable personal/shared values are not automatically server-only secrets, but they may appear in an option only when the adapter intentionally projects them as provider resource metadata. Let the shared executor own scope authorization, exact-reference resolution, credential authorization, error projection, and output sanitization; adapters must pass and preserve the executor's abort signal during provider work.