Skip to main content
Start with search. Then pass one focused async arrow function to execute.

Find your identity and stores

Search input:
Execution code:
The result contains user and organizations[]. Accessible stores appear under each organization. A standard store-scoped fallback key needs no organization input. With Bily Connect, add organizationId to execute only when the user explicitly selects one accessible organization:

Explain a revenue change

Search for the right comparison operation:
Run the returned revenue-trend helper with real calendar dates:
Review the returned readiness, warning, and sample-size fields before making a business recommendation.

See which analytics data is available

The returned data appears in result. The message appears in logs.

Complete and verify a supported action

For a request such as refreshing connected advertising accounts, follow this sequence:
  1. Call search with the exact intent and store.
  2. Review riskTier, approvalPolicy, preconditions, and verification guidance.
  3. Show the proposed function to the user.
  4. Get explicit approval in the client.
  5. Run one focused action, then verify it with a read.
Do not add other writes to the function without showing them. If the request expands, present the complete function for approval again.