Connect GoHighLevel like any other CRM. On WhatsApp, a mapped phone field is filled from the sender and not asked.
GoHighLevel. Workspaces can connect GoHighLevel from Integrations and push contacts, opportunities, tags, and notes from Intake Bot action blocks. The connected sub-account is stored on connect, so builders do not paste a location id.
Phone on WhatsApp. When an Intake Bot maps a phone field to the contact, a WhatsApp conversation fills that field from the sender’s number and does not ask it. The same published bot still asks for the number on the web chat. Business and Enterprise for WhatsApp.
Signed-in app pages stay in English and Spanish, so the browser does not translate them in place. Public Intake Bots and docs still can. Admins can store a display name and logo on a Composio toolkit. That setting is not a catalog on this site.
Admin Integrations now stores display name, logo, bilingual descriptions, auth scheme, and scoping keys on the toolkit setting. A new toolkit no longer needs a code change when Composio already covers it.
The app shell was served as lang="en" on every route, including /es, so Chrome offered to translate the interface into Spanish. Once translation was on, the browser replaced text nodes in place and the next interface update failed to reconcile them, showing a generic error screen. The action behind it had usually already succeeded on the server, so testing an ad platform connection could report an error even though the test passed. Authenticated routes are now marked as not translatable because they are already available in English and Spanish; public Intake Bots and documentation remain translatable.
Workspaces can connect GoHighLevel from Integrations and push contacts, opportunities, tags, and notes from Intake Bot action blocks. The connected sub-account is stored on connect so builders do not paste a location id.
When an Intake Bot maps a phone field to the contact, a WhatsApp conversation fills that field from the sender's number and does not ask it. The same published bot still asks for the number on the web chat. The number lands on the contact, the record, and the Process Board card through the existing submission pipeline.
