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

# Connections

> The keys and tokens your workspace runs on, and the HubSpot pull

**Settings → Connections** holds the credentials Nudge uses to reach the services your workspace is connected to. Only admins can open it.

## How a value shows

Each row has its name on the left and its current value in a box on the right. To change a value, click it or the pencil beside it, and the box becomes an input in place.

Secrets are write-only. Once saved you see that a value is set and its last few characters, never the whole thing. Nobody can read a token back out of Nudge, you included, so keep your own copy where you keep your other secrets.

A value tagged **managed** was set for your workspace by Nudge and is kept up to date for you. You can replace it with your own, which stops Nudge updating that field.

## HubSpot

The **Private app token** Nudge uses to read and write your HubSpot records. See [HubSpot mode](https://docs.autonudge.dev/crm/hubspot.md).

## AI & Voice defaults

The services that cost money per use and have a model to choose sit together in one card.

* **Voice agent engine** is the model a newly created voice agent starts on. Agents that already exist keep the one they were made with, so changing it does not touch calls that are already running. The prices beside each option are per conversation minute, for comparing options. They are not what Nudge bills you.
* The **voice key** is what your voice agents run on.
* **Anthropic** and **OpenAI** each have a key and a model.

The two AI keys are optional. Leave a key empty and Nudge answers with its own; the row says **Provided by Nudge**. Paste your own key and Nudge uses yours from then on. OpenAI runs the writing help, such as suggesting a note for an automation, and either one can power the [WhatsApp assistant](https://docs.autonudge.dev/channels/assistant.md). Both model fields offer a list read from the key in use, so you only see models it can actually run. Leave a model blank and the field shows the one that will run instead.

With both keys saved, the one marked **default** is the one Nudge's own AI uses. Click **set default** on the other row to switch.

## WhatsApp Cloud API

The **System user token** from Meta, plus the webhook values that let replies on your official numbers reach Nudge. One token covers every Cloud API number in the workspace. Each number's own Meta IDs are entered when you add it under **Channels → WhatsApp**. See [Cloud API numbers](https://docs.autonudge.dev/channels/whatsapp.md#cloud-api-numbers).

## HubSpot lead pull

HubSpot workspaces only. This card decides how often Nudge refreshes your contacts from HubSpot.

* **Auto-pull leads from HubSpot** turns scheduled pulls on or off. With it off, nothing is pulled on a timer, but you can still sync by hand.
* **Pull frequency** is the wait between pulls, five minutes at the least. Pulling faster runs into HubSpot's own rate limits.
* **HubSpot portal ID** is the number in your HubSpot web address. Nudge uses it for the **Open in HubSpot** links on contacts.
* **Restart automations on a new form** lets automations that already ran on a contact run again after they fill in a form again. See [Once per contact](https://docs.autonudge.dev/automation/triggers.md#once-per-contact).

Which contacts get pulled is not set here. Your active automations decide that, as explained in [What Nudge pulls](https://docs.autonudge.dev/crm/hubspot.md#what-nudge-pulls).

> [!NOTE]
>
> A few connections are run by Nudge for every workspace, such as the system email that sends invites and alerts. They are not listed here because there is nothing for you to set.

Keys that let other tools reach Nudge are a different thing, and live under [Settings → API](https://docs.autonudge.dev/api/overview.md).


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