> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.

# Turn connected data into useful work

> Use connected business data to spot what deserves attention, prioritize next steps, and create source-backed briefs and handoffs.

## What this article shows you

Use a connected account as a live source, then turn what StefanBrain finds into a decision or finished deliverable.

You normally do not need to choose a tool. Name the result, the connected source, the scope, and what StefanBrain should produce.

The goal is not more analysis. It is a clearer decision, a stronger next step, or a handoff your team can use.

## Practical use cases

<CardGroup cols={2}>
  <Card title="Find objections worth addressing" icon="messages-square">
    Group repeated concerns from reviews or support conversations so you can
    decide what to answer in ads, landing pages, and customer education.
  </Card>

  <Card title="Find where performance needs attention" icon="chart-no-axes-combined">
    Compare two periods and surface the campaigns, pages, or products most
    likely to explain the change, so your team knows where to investigate first.
  </Card>

  <Card title="Prioritize landing pages for review" icon="route">
    Pair analytics with page context to find high-traffic pages where a mismatch
    may be limiting conversion, then focus CRO work on the strongest candidates.
  </Card>

  <Card title="Choose evidence-backed creative tests" icon="lightbulb">
    Combine customer language, performance evidence, and an approved brand
    document into hypotheses so the creative team starts from observed patterns
    instead of assumptions.
  </Card>

  <Card title="Create an actionable handoff" icon="file-text">
    Turn the latest approved brief into a checklist, meeting brief, or client
    handoff so the next person knows what to do and which source supports it.
  </Card>

  <Card title="Prepare a focused weekly review" icon="calendar-clock">
    Compare recent performance with the prior period and create a concise brief
    of the changes, questions, and decisions the team should discuss.
  </Card>
</CardGroup>

## Watch the walkthrough

<Info>
  Members with access to an enabled connector can use its data in Chat. To run
  a request on a schedule, like the weekly review near the end of the
  walkthrough, open **Schedule** in the sidebar.
</Info>

<Frame caption="See how connected company data can support research, analysis, briefs, and better decisions. Duration: 7:22.">
  <video className="w-full h-auto rounded-xl" controls preload="metadata" poster="/images/tutorials/covers/connector-use-cases.png" playsInline alt="A walkthrough of practical connector workflows in StefanBrain" aria-label="Narrated connector use cases walkthrough">
    <source src="https://stefanbrain.com/api/tutorials/videos/connector-use-cases" type="video/mp4" />

    <a href="https://stefanbrain.com/api/tutorials/videos/connector-use-cases">
      Watch the connector use cases walkthrough
    </a>
  </video>
</Frame>

## How connectors fit into a workflow

A connector supplies current data or an external action. It does not replace the other context that makes the result useful.

| Input | What it contributes |
| - | - |
| Product | Stable business, offer, audience, and voice context |
| Project | Client or campaign context and an organized place for the work |
| Connector | Current records and supported actions from an external account |
| File or link | A specific brief, page, export, or file for this job |
| Your request | The decision, deliverable, scope, and what StefanBrain may read or change |

<Tip>
  Describe the complete job and let StefanBrain choose or combine capabilities.
  Select a specific tool only when the workflow must use that exact method.
</Tip>

<Warning>
  Some connectors can change external systems. Start with a read-only request.
  Review any approval prompt before allowing a create, update, send, publish,
  refund, delete, or other external action.
</Warning>

## A repeatable connector workflow

<Steps>
  <Step title="Choose the evidence and the deliverable">
    Start with one decision or output. Name the connected source and the part of
    that source StefanBrain should inspect.

    A strong request usually includes a date range, product, campaign, account,
    document, or other useful boundary.
  </Step>

  <Step title="Confirm the intended account in Chat">
    Open a Chat, open **Connectors**, and confirm the intended account is on.

    If you have personal and company accounts for the same provider, name the
    company and account in your request. This prevents a useful answer from
    being built from the wrong source.
  </Step>

  <Step title="Run a read-only evidence pass">
    Ask StefanBrain to retrieve and organize the evidence before asking it to
    change anything.

    ```text theme={"system"}
    Use the connected Yotpo account for Northstar Hydration.

    Compare 1–3-star product reviews with 5-star reviews. Group the repeated
    objections and benefit language, then include representative phrases with
    the rating and date for each example.

    Read only. Do not update any reviews or customer records.
    ```

    Replace the provider, account, product, and requested evidence with the
    source you actually use.
  </Step>

  <Step title="Check the evidence before the recommendation">
    Confirm the response names the source, time period, filters, and records or
    entities behind its conclusion.

    If something is missing, narrow the follow-up instead of asking for a full
    restart.

    ```text theme={"system"}
    Keep the same source and date range. Separate product-quality objections
    from shipping or support complaints, and show which review examples support
    each group.
    ```
  </Step>

  <Step title="Turn the finding into finished work">
    Once the evidence checks out, ask for the next useful result.

    ```text theme={"system"}
    Keep the five strongest customer phrases and the objection groups you found.
    Turn them into a one-page creative test brief with three hypotheses, the
    funnel stage for each, and the evidence behind each choice.
    ```

    The follow-up inherits the established Chat context, so it should say what
    to keep, what to change, and what result comes next.
  </Step>
</Steps>

## Practical prompt patterns

### Find where paid performance needs attention

Use this to separate a broad account change from a campaign-level issue and decide what the media buyer should inspect first.

```text theme={"system"}
Use the connected Meta account for Northstar Hydration.

Compare the last 30 complete days with the previous 30. Identify the three
changes that deserve the most attention based on their size and the amount of
spend affected. Name the campaigns or ad sets behind each one.

For each change, explain why it may matter. Return a short evidence table
followed by the three questions the media buyer should investigate first. Read
only.
```

### Find which landing pages are worth reviewing first

Use this to focus CRO effort on high-traffic pages where the conversion gap may create the strongest opportunity to learn.

```text theme={"system"}
Use the connected Analytics property for Northstar Hydration.

For the last 30 complete days, find the landing pages with meaningful traffic
and the weakest purchase conversion. Rank the top three review opportunities
using traffic and conversion data. For each, explain why it may be worth
testing, include its page URL, show the metrics behind the ranking, and give me
the first CRO question to investigate.

Do not change analytics settings or the site.
```

### Give the creative team a usable test plan

Use this to turn approved strategy and current evidence into one brief the creative team can act on without rebuilding the context.

```text theme={"system"}
Use the connected Glow Labs Drive account.

Find the latest approved positioning brief and the current creative report.
Create a one-page test plan the creative team can act on. Include the audience,
promise, supporting customer language, three hypotheses, the evidence behind
each one, and any unresolved decision. Cite the source document for every
section.

Read the source files only. Do not edit or move them.
```

### Prepare for the weekly media review

Use this to surface the important changes before the meeting, so the team can spend its time deciding what to investigate or change.

```text theme={"system"}
Use the connected Meta account for Northstar Hydration.

Compare the previous complete week with the week before it. Prepare a weekly
media-review brief that leads with the three largest performance changes, names
the campaigns behind them, explains why each may matter, and ends with three
questions or decisions for the team.

Read only.
```

Available records and actions vary by provider and by the permissions on the connected account.

## Team and permission boundaries

Every member can schedule requests. Open **Schedule** in the sidebar to run a
connector request you use often on a set day and time.

Team access shares the connected provider account as a whole. It does not create folder-level, property-level, or resource-level limits inside that account.

The connection owner controls team access and the Team tool-permission profile. For Meta, shared read and analysis access is separate from publishing. **Can publish ads** starts off for each teammate and must be enabled by the connection owner.

Use a narrower provider account when the full connected account contains more than the team should access.

## Common mistakes and troubleshooting

<AccordionGroup>
  <Accordion title="The answer used the wrong account">
    Confirm the intended account is on under **Connectors**, then name the
    provider, company, and account in the next request.
  </Accordion>

  <Accordion title="The answer is broad but not useful">
    Add a date range, entity, comparison, deliverable, and decision. Ask for the
    evidence behind each conclusion.
  </Accordion>

  <Accordion title="A write action asks for approval">
    Read the proposed action and target. Choose **Approve once** only when the
    change is intended, or ask the connection owner to adjust the permission.
    Do not approve a broader action to unblock a read-only job.
  </Accordion>

  <Accordion title="A shared source is missing">
    Ask the owner to confirm **Team access** and your member switch. Then check
    your own **Use in my chats** setting for that shared connection.
  </Accordion>

  <Accordion title="The connection needs attention">
    Open **Connectors** and check the account. Only the connection owner can
    reconnect a shared account.
  </Accordion>

  <Accordion title="The request tries to analyze too much at once">
    Start with one period, product, campaign group, property, folder, or review
    slice. Expand only after the first evidence set is complete.
  </Accordion>
</AccordionGroup>

## Next steps

* [Give Chat the right context](/knowledge-base/chat/give-chat-the-right-context)
* [Share connectors with your team](/knowledge-base/connectors-automations/share-connectors-with-your-team)
* [Run a CRO funnel review](/knowledge-base/creative-strategist-research/run-a-cro-funnel-review)
* [Browse connector and schedule guidance](/knowledge-base/connectors-automations)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.