Select a team
Edit the playbook, pick the tools the team can reach, set up integrations, and test it live.
Generate this team from your website
Enter your business URL and what this team should do — AI writes the description and every playbook file (SOUL, BRAND, CAMPAIGN, PERSONALITY, FLOW, NOTES, FAQ) for you.
Team Key
Unique 8-char key that identifies this team across every webhook URL below. One key, many platforms. Immutable.
────────
Connect this team to any system
Universal URLs work with anything. Shortcuts skip payload-mapping for popular platforms. Every URL here embeds the team key above — paste the URL exactly.
Universal — works with any platform
Pre-built shortcuts (optional convenience for these specific tools)
📨 Send instructions via webhook
Teams are the canonical GHL webhook surface. Drive any action by passing a plain-English instruction. In a GoHighLevel Workflow → Send Webhook step (or any caller), POST to the GHL Workflow URL above with these fields under
customData:| Parameter | Required | What it does |
|---|---|---|
instructions | Yes | Plain-English directive the AI executes — e.g. "Send a friendly appointment-reminder SMS, then tag the contact 'reminded'." The AI plans & runs the actions (SMS, email, tags, custom fields, notes, pipeline moves). |
contact_id | Auto | The GHL contact the action applies to — GHL fills this automatically in a workflow. |
default_model | No | Override the AI model (else the team default). |
provider_route | No | bedrock (default — billed in credits) or anthropic (your own key). |
Example webhook body:
{
"customData": {
"instructions": "Send a warm appointment-reminder SMS for tomorrow 2pm, then add the tag 'reminder-sent'."
}
}Tip: be specific — name the action and the details. Without
instructions, the team auto-drafts an email + SMS. Every webhook run logs to the Logs tab and deducts credits when on Bedrock.Use this team as an MCP server
Pick how the client authenticates, then paste the URL or config block.
OAuth is the easiest path for Claude Code, Claude.ai, and Cursor.
API key is for VAPI MCP, scripts, and anything headless.
Claude Code, Claude.ai, and Cursor discover OAuth automatically on first connection.
Dynamic Client Registration (RFC 7591) mints a client_id for them on the fly — you don't
copy any secret. The user clicks an in-browser consent screen the first time and the token
is stored securely on their device.
MCP URL
Loading…
One-line Claude Code install
Loading…
~/.claude.json (OAuth — no headers needed)
Loading…
How to connect
- Open a terminal in your project (or anywhere — the registration is global).
- Run the install command:
claude mcp add --transport http ambrose-… https://…
- Claude Code opens your browser to the consent page. Sign in to Ambrose if asked.
- Click Approve to grant this team's tools to Claude Code.
- Done — start a new Claude Code session and the team is available as the
ask_…tool.
First-time setup uses Dynamic Client Registration (RFC 7591) — Claude Code mints its own client_id, you don't paste a secret. Tokens auto-refresh; revoke any time from Ambrose.
Discovery URL:
Revoke access: drop the row from
mcp_oauth_tokens or use the OAuth revoke endpoint (TBD admin UI).Claude Routines
Trigger Claude Code routines
Register Claude Code routines here once, and every agent, team, and Ambrose Chat in this agency can fire them by name (tools
list_claude_routines + trigger_claude_routine). Paste a routine's full URL or its trig_… ID, plus the per-routine API token from the routine's API trigger settings. Routines are shared across this agency; tokens are stored encrypted-at-rest and never shown again.
Add a routine
Default model
Model this team uses when it runs. Bedrock options are always available (system-billed at $0.01/message). Anthropic options appear once you save your Anthropic key in Settings → AI.
Tools this team can reach
Toggle on the toolboxes, your skills, and external tools. Everything checked here is also exposed via the team's MCP URL.
Your skills
Loading…
External tools (your MCPs)
Loading…
Third-party integrations (API access) — opt-in
API access to the custom REST integrations you add under Settings → Third-party integrations (Slack, Twilio, your own API…). GHL is NOT here — it's reached via the
ghl spoke in the toolboxes above. Toggle one on and this team can call its API via integration_call; credentials stay server-side.Loading…
Test run
Send a message to this team and see the response + tool trace live.
Routines
Scheduled prompts that fire against this team on a recurring cadence. Each run uses the team's default model + spokes.
Conversations
Every run of this team — chat, scheduled routines, and webhook executions — as a thread. Open one to review what it did (and any actions awaiting approval), then continue the conversation to adjust or run more. Agency-isolated.
Select a conversation to view its transcript.
Activity
API calls (LLM usage + cost) and audit trail for this team.
Loading…
Loading…