---
title: Integration Access
published: true
index: 10
---

# Request missing report access

On-site measurement needs either matching Shopify or Google Analytics aggregates, not both. Search Console is optional for requested organic acquisition context and cannot supply the on-site rates. Authorized aggregate artifacts are an alternative when direct connection is unavailable. Keep the configured storefront as the target throughout setup.

## Connection setup outside evaluation

Explain the missing source, target and decision it would support, then offer its supported connection flow or continuing without it. An explicit connection request already authorizes starting that flow; do not ask again. Never request passwords, keys or tokens in chat.

### Present one question per missing integration

Ask about one useful missing source at a time, with its verified status and two choices. For a verified, available and permitted Composio fallback outside Glue:

> You don’t have access to Google Analytics.

- Use Composio for Google Analytics
- Continue without Google Analytics

Substitute the relevant integration/status, such as “Your Shopify connection needs to be reconnected.” With only a native host flow, offer “Connect Google Analytics” or “Reconnect Shopify” and “Continue without …”. Never offer unavailable/prohibited Composio or combine integrations, connection methods and exports in one question.

Request another source only for a specific unresolved decision. Shopify or GA4 alone may supply the funnel; Search Console is optional for requested acquisition context. Core needs no analytics. If the user declines or has not answered, continue independent work and retain dependent gaps. Explain consequences briefly in progress/results; do not repeat declined requests or treat silence as consent.

### Choose the connection flow

In Glue, use its connection/setup flow exclusively and resume when the host supplies access. Never invoke Composio CLI or bypass guarded evaluation with CLI, proxies or browser automation.

Outside Glue, prefer the host connector/UI. An execution-capable host may use already available, permitted Composio as a fallback. Check `command -v composio` and `composio link --help`; install nothing and create no auth configuration during evaluation. Confirm the toolkit: `github`, `shopify`, `google_analytics`, or `google_search_console` only for Funnel.

After authorization:

```bash
composio link <toolkit>
```

If the host cannot open a browser, use `composio link <toolkit> --no-browser --no-wait` and show only the provider-returned authorization URL. Keep this temporary URL out of reports, repos and evidence. The user completes sign-in/consent and reviews actual scopes; never approve for them or claim the grant is read-only because this skill only reads.

Have the user select among multiple accounts using account/alias controls; preserve other connections. Verify completion through supported status/list operations (`composio link <toolkit> --list` when available), then bind the intended repo/store/property before business reads. Discover read schemas and select accounts explicitly; do not probe ambient identity or use business mutations.

Missing tools, failed linking, declined consent or absent responses leave only dependent decisions blocked. Retain completed evidence; do not loop on authorization, substitute accounts or weaken host guards.

## Resume the report

Follow the [funnel workflow](../workflows/funnel.md#bind-and-validate-the-data) for source binding and metric integrity, and the [Search Console procedure](search-console.md) before optional acquisition reads. Preserve completed evidence and report only actual measurements; successful OAuth alone does not establish property access, analytics-report access or usable rates.