My agent can’t connect
- The connector never prompts for sign-in: re-add it with the exact endpoint
https://app.granvl.com/api/mcp. For stdio-only clients, bridge withnpx -y mcp-remote https://app.granvl.com/api/mcp. - Tools connect but act on the wrong workspace: OAuth follows your active workspace. Switch workspaces in the dashboard, then reconnect. API keys are pinned to their workspace and can’t drift.
- The agent connects but builds pages that don’t track: the skill isn’t installed. Ask the agent
Granvl: confirm the skill is installed; if the reply doesn’t start with “Granvl skill ready”, follow Install the skill.
My domain won’t verify
- DNS can take minutes to propagate; use Refresh on the domain card.
- Check the record type matches the card exactly: subdomains use a
CNAMEtocname.vercel-dns.com, apex domains use anArecord to76.76.21.21. A common miss is a proxying CDN (orange-cloud Cloudflare) in front of the record; set it to DNS-only. - If the card asks for an extra verification
TXTrecord, it’s required; add it alongside the main record.
Leads aren’t arriving at my CRM
- Open the funnel’s Lead delivery settings and hit Send test lead (available for GoHighLevel and Webhook destinations). It fires a clearly-fake payload carrying every field from every variant, so you can confirm the endpoint and map fields.
- For GHL specifically: the webhook URL must be the workflow’s Inbound Webhook trigger URL, and the workflow must be published after mapping. See Forms.
- Check granvl’s delivery alerts email; failed or unconfirmed sends trigger a workspace email within the hour.
- Field-name mismatches fail silently at some vendors (HubSpot rejects unknown fields, LeadProsper is case-sensitive and requires separate
FirstName/LastName). Compare your form’s field names against the destination’s expectations.