WEBVTT

00:00:00.000 --> 00:00:08.867
In this video, you will verify the GoHighLevel sub-account
that belongs to your agency. Connection and confirmation are

00:00:08.867 --> 00:00:13.793
separate steps because applicants must reach the correct
recruiting workspace.

00:00:14.800 --> 00:00:22.252
Open Settings, then GHL Integration. Use one-click
authorization when it is available, or the manual Private

00:00:22.252 --> 00:00:29.703
Integration Token option. Paste the token from your own
agency account, save the connection, and keep

00:00:29.703 --> 00:00:31.100
that token private.

00:00:32.133 --> 00:00:41.152
Choose Test connection. Read the returned sub-account name,
not just its location identifier. Stop if the name is

00:00:41.152 --> 00:00:45.160
unfamiliar and check which location your authorization
selected.

00:00:46.167 --> 00:00:54.675
If this is the sub-account your agency owns, confirm it
explicitly. Until confirmation, Warp does not write

00:00:54.675 --> 00:00:59.681
candidate data there. Check the successful confirmed state
before proceeding.

00:01:00.700 --> 00:01:09.201
Choose your recruiting pipeline and map the stages to the
stages your team actually uses. This tells Warp where

00:01:09.201 --> 00:01:12.333
incoming applicants and your recruiting updates belong.

00:01:13.333 --> 00:01:21.885
Select the applicant workflow you want to use, if you have
built one. Workflows are optional. Verify each choice before

00:01:21.885 --> 00:01:25.733
saving, and confirm only a sub-account that is yours.

00:01:26.733 --> 00:01:33.627
Inbound applicants can sync automatically after
confirmation. Sourced and LinkedIn people never auto-sync;

00:01:33.627 --> 00:01:42.112
pushing one requires the explicit Push to GHL action for
that individual. Interview booking remains independent

00:01:42.112 --> 00:01:43.173
of GHL.