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

# Connect your channels

> Connect the accounts Goosy publishes to and reads numbers from, read the health of each one, and fix a connection that drops.

Goosy can draft without any connections at all. To publish for you, or to tell
you what happened after you published, he needs access to the accounts you
already own — your social profiles, your ad accounts, your analytics, your CRM.

Go to **Settings → Integrations**. The screen is called **Connections**, and
[Integrations](/setup/integrations) covers it in full.

## Connect one

<Steps>
  <Step title="Find the one you want">
    Every provider is a card. Above them, a line counts what you have —
    "7 connected · 1 need attention" — and three filters let you show **All**,
    only **Connected**, or only the ones needing **Attention**.
  </Step>

  <Step title="Press Connect">
    Press **Connect** and follow the provider's own steps to grant access.
    Do this as the person who owns that account — you are granting access to
    something you control, not creating a new account.
  </Step>

  <Step title="Check it landed">
    The card now reads **Connected** and, where it applies, names the account
    it connected to. Some providers need one more choice after that — an
    advertising account still to be picked, for instance, shows *ad account
    setup is part-finished* until you finish it.
  </Step>
</Steps>

<Note>
  Connecting is per workspace. If you run several workspaces, each connects its
  own accounts — switching workspace switches the whole set.
</Note>

## What each state means

| State             | What it means                                                                                                                           | What you do                                                               |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Connected**     | Goosy has access, and the last health check passed. Cards show when they were last checked.                                             | Nothing. **Manage** opens the details.                                    |
| **Reauth needed** | The access expired or was withdrawn at the provider's end. The card says the latest health check failed and when the last good one was. | **Reconnect**.                                                            |
| **Not connected** | Available, but you have not connected it.                                                                                               | **Connect**, when you want it.                                            |
| **Coming soon**   | We do not support it yet.                                                                                                               | Nothing — it is not connectable, and we would rather say so than pretend. |

"Connected and healthy" means both halves: Goosy holds valid access, and a
check against the provider has recently succeeded. A connection can be present
and still unhealthy, which is exactly the case the **Attention** filter exists
to show you.

## When one drops

Access expires. Passwords change. Somebody removes an app at the provider's
end. When that happens the connection does not fail silently.

* A banner appears at the top of **Connections** naming the provider and
  offering to reconnect it.
* The provider's card moves to **Reauth needed**, says the latest health check
  failed, and tells you when it last worked.
* The **Attention** filter narrows the page to just those.

Press **Reconnect** and approve the access again at the provider. A card can
also ask you for something short of a full reconnection — a request waiting for
your approval, for instance — and says so on the card itself.

<Warning>
  A publish can fail, and a connection that dropped is a common reason. A
  failed publish appears at the top of that week in **Schedule** with the
  options you have for it — it does not disappear quietly.
</Warning>

## Which ones you actually need

You do not need all of them. Connect against what you are trying to do:

* **To publish** — the accounts you want things to go out on.
* **To see what worked** — your analytics and advertising accounts, so the
  numbers on your Dashboard are yours rather than estimates.
* **To follow up** — your CRM, if you have the Goosy Grow add-on.
* **To make videos** — the voice and presenter providers, if you want Goosy to
  narrate or present rather than hand you a script.

The **Connections** screen is the list that is true today, and it changes as we
add providers. Read it there rather than from a list in a document.

## Ask Goosy instead

Goosy can do this part with you. From any screen, ask him to connect an account
or ask why one is erroring — on the **Connections** screen he offers exactly
those two as suggestions.

## What to do next

You have a brand and somewhere to publish. Make something:
**[Your first piece](/start/your-first-piece)**.