Short answer: Drop the "GoHighLevel → Create GoHighLevel Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Location ID locationId | string | Required | The GoHighLevel sub-account (location) the contact belongs to. |
Email email | string | Optional | Email. e.g. "user@example.com" |
Phone phone | string | Optional | Phone in E.164 format. e.g. "+15551234567" |
First Name firstName | string | Optional | First Name. e.g. "Jane" |
Last Name lastName | string | Optional | Last Name. e.g. "Smith" |
Company companyName | string | Optional | Company Name. e.g. "Acme Inc" |
Source source | string | Optional | Where this contact came from (used in GoHighLevel reporting). e.g. "Website Form" |
Tags tags | string | Optional | Comma-separated tags to apply on creation. |
{"locationId": "e.g. ve9EPM428h8vShlRW1KT","email": "user@example.com","phone": "+15551234567","firstName": "Jane","lastName": "Smith"}
{"contact": {"id": "ocQHyuzHvysMo5N5VsXc","tags": ["newsletter","lead"],"email": "jane@example.com","phone": "+15551234567","source": "Website Form","lastName": "Smith","dateAdded": "2026-04-11T10:00:00.000Z","firstName": "Jane","locationId": "ve9EPM428h8vShlRW1KT","companyName": "Acme Inc"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.