Integrations and app services
Open Project > Integrations when the current route supports external application services. The workspace groups several independent capabilities. A tab being visible means the panel is available; it does not mean a provider is connected or production-ready.
Connectors
Connectors link the application to an external business service. Choose the provider, review the requested account and scopes, and complete authorization in the provider flow. Confirm which project and environment receive the connection. Test with non-production data first and disconnect or revoke the provider when it is no longer needed.
AI and application intelligence
The AI area configures an application-facing AI service or feature. Keep provider credentials in the secret boundary, specify the environment, and review model or data-use settings. A project model selection for Agent work is separate from an AI integration that the generated application calls at runtime.
Commerce and Shopify
Commerce features can cover products, memberships, subscriptions, payments, or provider-specific storefront operations. Select the use case and provider offered by the panel, then review currency, webhooks, entitlement behavior, and test/live environment. Shopify setup requires the target store and requested scopes. Verify that a payment or entitlement event is reflected in the application before using live credentials.
Authentication, storage, and push
The Data panel can provide application Auth, Storage, and Push resources. Auth concerns the application's end users and callback/origin configuration; it is separate from your BuildWhat sign-in. Storage is for application files and access rules. Push requires platform credentials and device configuration when supported. Test identity, file access, and notifications with a non-production account.
Automations, knowledge, and web search
Automations define supported connector or scheduled workflows; inspect trigger, target, permissions, and recent run before enabling one. Knowledge provides project context for the Agent or application where supported; review source ownership and freshness. Web search is an Agent-assisted research capability and should be used within the project's authorization and data policy. Record important external assumptions in the project request.
Skills and MCP
Skills add reusable task guidance. MCP exposes authorized tools from a configured server. Review scopes, data destinations, and member access before enabling either. A connected tool can act on external systems; keep approval prompts enabled for sensitive operations and revoke unused credentials at the source.