Skip to main content

Set up a connector domain

Give your clients a connector address on your own domain, so the address and the icon their AI assistant shows are yours.

What a connector domain gives you

When you give a client an assistant, they install a connector — an address their AI assistant connects to in order to run your workflows and follow your skills. By default that address lives on TaskJuice's own hostname.

A connector domain moves it to a hostname you control, like connect.agency.com. Three things change for your client:

  • The address they paste into Claude, ChatGPT, or Cursor is yours.
  • The icon their assistant shows beside the connector is your icon, not ours.
  • Your published tools are renamed once to carry your own name.

This is separate from your app domain. The two do different jobs, break in different ways, and are set up independently: the app domain is where you and your team work; the connector domain is where your clients' assistants connect.

Who can do this

You must be a tenant admin on the agency. A connector domain uses the same custom-domain entitlement as your app domain — if your plan includes one, it includes both.

Before you start

  • You need a domain you control, and the ability to add records at its DNS provider.
  • Use a subdomain like connect.agency.com. Apex domains (agency.com) are not supported, because the record type this needs conflicts with your email records.
  • One connector domain per agency. To change it later, remove the existing one first.
  • Read What changes for installs you have already sent before you start. One of the changes is permanent.

Set it up

  1. Open domain settings

    Go to Settings → Domain. The Connector domain card sits at the bottom of the page, below your app domain.

  2. Enter your hostname

    Type the full hostname — for example, connect.agency.com — and submit. Nothing routes yet; this registers your claim and generates the ownership token you prove next.

  3. Add the three DNS records

    The card shows you the exact records to create at your DNS provider: a TXT record that proves you own the hostname, a CNAME that lets us issue a TLS certificate for it, and a CNAME that points traffic at TaskJuice. Add all three. Do not remove them afterwards — they are re-checked periodically.

  4. Wait for it to go live

    We check your records every five minutes, then issue a certificate automatically. The card walks through four steps and tells you which one it is on. Most domains are live within fifteen minutes; slower DNS providers can take an hour.

Nothing changes for your clients until every record verifies

Until the card says the domain is live, the console keeps showing your clients' existing connector address, and installs you send keep using it. A hostname that is registered but not yet verified does not accept connections — so the console will not show it to you as an address you can hand out.

What changes for installs you have already sent

Connectors your clients already installed keep working. They keep using the address they were set up with. You do not need to re-send anything, and your clients do not need to reinstall.

New installs use the new address. Anything you issue after the domain goes live — a pasteable install artifact, an emailed set of install instructions, the address shown on a client's portal page — carries your connector domain.

Each client's portal page keeps showing the address their own install actually uses, so a client who set up before you provisioned the domain is never shown an address their assistant does not know.

Your published tools are renamed once, permanently

When the connector domain goes live, every workflow you have published as a tool is renamed once, from taskjuice_ to a prefix derived from your agency's name. taskjuice_weekly_digest becomes something like acme_weekly_digest.

The console shows you the exact prefix before you submit the hostname, and again on the Published tools tab afterwards.

This one is permanent

Assistants re-read your tool list every session, so they pick up the new names on their own. What does not update on its own is a tool name a person typed somewhere — a saved prompt, a Claude Project instruction, an internal runbook — and those keep naming the old tool and stop matching. The rename happens once, when the domain goes live, and removing the connector domain later does not rename your tools back. If you or your clients have written tool names into saved prompts, update them once the domain is live.

The icon your clients see

The icon an assistant shows beside your connector comes from your branding settings. Upload it under Settings → Branding, in the Favicon field. If that field is empty we fall back to your light icon, then your dark icon, and finally to TaskJuice's own icon.

Two limits decide whether your icon is actually used:

  • Accepted formats: PNG, JPEG, and WebP. Other file types are rejected at upload.
  • 512 KB ceiling for serving. If the stored image is larger than 512 KB, or takes longer than three seconds to fetch, we serve the TaskJuice icon instead rather than showing your client a broken image.

The second limit is the one worth checking, because there is no error to see: the connector still works, the page still loads, and the only symptom is our icon where yours should be. If your icon is not appearing, re-export it smaller and re-upload — a 128×128 or 256×256 PNG is comfortably inside the limit and is more than enough resolution for the places an assistant draws it.

Where the icon shows up

In Claude, the icon appears both in the chat surface beside your connector and in the connector settings menu. Other assistants place it differently, and some do not show one at all.

While your client is granting access

Part of the connect flow — the screen where your client approves the connection — is served on a TaskJuice address rather than yours. That screen carries your agency's name, and it says plainly why it is not on your domain, so a cautious client is not left comparing an unfamiliar address against a familiar brand with no explanation.

Everything else in the flow, and every request their assistant makes afterwards, is on your connector domain.

Remove a connector domain

Remove it from the same card, in Settings → Domain.

Removing it breaks your clients' installs

Connectors your clients installed from the connector domain stop working. Getting them back means re-issuing every client's install from your TaskJuice address. Your published tools keep their renamed form — removing the domain does not rename them back.

What a connector domain does not change

  • Your app domain. The two are independent. Removing one leaves the other alone.
  • Sign-in configuration. Sign-in applies to your app domain only; there is nothing to configure for a connector domain.
  • Your permanent address. Your TaskJuice address keeps working, and keeps serving connectors your clients already installed.
  • What an assistant can do. Your plan, the skills you have licensed to each client, and the workflows you have published decide that. The address does not.

Troubleshooting

My domain is set up but the connector does not work. Check the connector card first. If it has not reached the live state, the hostname is registered but not yet accepting connections — that is expected, and the console shows which step it is waiting on. Use Check now on the card to re-check immediately instead of waiting for the next five-minute window.

The card shows a failure and lists the records it expected. Compare each expected value against what your DNS provider actually returns. The most common causes are a provider stripping the leading underscore from the TXT record name, and a record added to the wrong zone. Fix the record and use Reset and try again.

My icon is not showing up. See The icon your clients see — most often the file is over the 512 KB serving ceiling. Assistants also cache connector icons; give it a few minutes, or remove and re-add the connector in the assistant to force a refresh.

A tool name in my saved prompt stopped working. Your published tools were renamed when the connector domain went live. Open AI → Published tools to see their current names and update the prompt.

Next steps

Was this helpful?