Connect Facebook Page to GoHighLevel
Three steps: connect the page, map the form fields, point the automation at the new form. Miss the third and the client's leads go nowhere.
Owner: Hanif. New process as of 2026-07-27.
WARNING
Do not stop after step 2. On the AirBear STL launch the page was connected and the fields were mapped, but the automation trigger was never pointed at the new form. Leads came in and no text ever went out. Fagr caught it by hand on a Saturday morning. The third step is the one that gets skipped — it is the one that matters most.
Before you start
- You have already built the lead form (Lead Form Standard Questions).
- You have GoHighLevel access. If you do not, ask Sean for an invite to the media address before you begin.
Step 1 — Connect the page
- In GoHighLevel, open the client's sub-account (search the client name at the top).
- Click the gear icon at the bottom of the left menu → Settings.
- Click Integrations.
What you see next depends on the client:
- Brand new client — the page is empty. Click Connect an account and sign in.
- Existing client, new page — the account is already connected and you are adding a second page to it.
- Find the new page in the list, select it, and click Update.
If the Integrations page shows a Sign in button and you do not have the login, stop and tell Sean. Those use his credentials.
Step 2 — Map the form fields
- On the connected account, click Configure field map (or the three-dot menu → Form Field Mapping).
- Find your new lead form. On a brand new client it will be the only one listed.
- Click Edit.
- Map each question to its GoHighLevel field:
| Lead form question | Maps to |
|---|---|
| Are you a homeowner in [Region]? | service_area |
| What do you need help with? | project_scope |
| How do you plan to pay? | payment method |
| How soon are you looking to get this done? | urgency / timeline field |
The first three are on every form. Anything beyond them is client-specific — map it to the field with the closest name.
- Click Save.
NOTE
If a field does not appear when you search for it, wait a few seconds and refresh. The field list lags behind newly created fields.
Step 3 — Point the automation at the new form
This is the step that gets missed. Do not skip it.
- Go to Automations in the left menu.
- Open the first workflow — it is labelled
[Company initials] W1. - Click the trigger at the top of the workflow. It is the block that fires when a lead comes in.
- On a new client this block will be empty or showing an error. That is expected — the form did not exist when the workflow was built.
- Select: - The Facebook page you just connected. - The lead form you just created.
- Click Save — at both the trigger level and the workflow level. GoHighLevel needs both.
WARNING
Every time a new lead form is added later, it has to be added to this trigger too. A form that is not listed on the trigger does not fire the workflow. New form = revisit this step.
Step 4 — Confirm
Post in the client's Discord channel:
Facebook page connected in GHL, fields mapped, W1 trigger pointed at the new form.
If anything on the front end looks broken after this — for example the end page returns a 404 — that is usually the domain not published yet, not your mapping. Post in the channel and let Mohamed or Griffin sort it.
What is NOT your job
The rest of the GoHighLevel build — the snapshot, custom values, pipelines, calendars, the other workflows — belongs to Mohamed. See GHL Client Setup — Snapshot & Automation Build SOP. You are connecting the page you built to the automation that already exists.