Skip to main content
For a connected GoHighLevel account, the send_email platform tool can submit an email through the location’s messaging service. The location needs a working email sender, and the conversation must be linked to a contact.

​
Configure the assistant

  1. Open the assistant’s Tool Kit → Tools & APIs. Add send_email and confirm it appears under Assigned to this assistant.
  2. In the prompt, explain when an email is appropriate and what it should contain. Tell the assistant to confirm the recipient’s address before sending.
  3. Add update_user_details if the assistant needs to collect or correct identity before another action. Use the customer’s stated address; do not invent one to satisfy a tool requirement.
  4. Save the assistant’s changes. If you will use the tool on live voice calls, Publish before that channel test. Use platform tools for the tool reference.
For example: “When the customer asks for our service summary by email, confirm their email address, send the requested summary, and report a failure if the email tool rejects it.”

​
Email fields

Location and contact context are required. Use the schema shown on the assigned tool when constructing a conversation request; these aliases describe accepted field names, not permission to send to unrelated contacts. A successful result confirms the provider accepted the send request, not inbox delivery.

​
Verify sending and delivery

Use a test contact and an inbox you control. Ask the assistant to send a distinct subject and short message. Check the tool result, the GHL conversation, and the receiving inbox, including spam. Provider acceptance and inbox delivery are separate results. The send operation requires contact and location context plus message content. When GHL reports that a contact has no email, a supplied recipient address can also be written to that contact before one retry. Confirm the address on the contact record after testing.

​
Troubleshooting

  • No contact or location context: start from the intended connected account and linked contact.
  • No access token or authorization failure: repair the GHL connection.
  • Sender/channel rejected: check the location’s email configuration and provider error; changing the assistant prompt will not repair a disabled sender.
  • Request accepted but no email received: inspect the provider’s delivery status and recipient address before retrying.
  • Tool not called: check assignment and make the trigger in the prompt specific.
For a different mail provider, use an optional custom API tool with that provider’s sender rules and delivery checks.