C
Costco Lead Integration
GoHighLevel · e-PIC · Costco Pipeline
Not connected
API Connection
● Idle
Enter credentials to connect
Last Successful Sync
—
No sync yet
Leads Today
—
Since midnight
Leads This Week
—
Since Monday
Connection Info
Worker / Proxy URL—
Access Key—
GHL Location ID—
Costco Pipeline—
Dashboard URL—
Logged In As—
Integration Controls
Reporting
Counts from the latest syncLeads by Store Location
| Store | Share (total) | Week | Total |
|---|---|---|---|
| All stores | 0 | 0 |
Leads by Source
| Source | Share (total) | Week | Total |
|---|---|---|---|
| All sources | 0 | 0 |
Lead Recovery
Reconcile specific Centah leads into GHLComma-separated. Each ID is fetched from Centah; leads already in GHL are skipped, and missing ones are pushed (contact + opportunity) and acknowledged. Requires the Access Key (API Settings).
API Settings
Centah Credentials
ⓘ
Update the Centah / e-PIC login used by the sync. Saving writes
CENTAH_USER and CENTAH_PASS as encrypted
secrets on both the costco-ghl-worker and costco-ghl-proxy workers via the
Cloudflare API. These credentials are never stored in this browser.
The Centah API login (e.g. brandywineapi).
Stored only as a Cloudflare Worker secret — never saved in this browser.
ⓘ Requires the Access Key (above) to match the Worker's DASHBOARD_KEY, and the proxy
worker must have CF_API_TOKEN + CF_ACCOUNT_ID configured.
Activity & Error Log
e-PIC Integration
● Idle
Not yet tested this session
Last e-PIC Test
—
Run a connection test
e-PIC / Centah Sync Status
ⓘ
The e-PIC sync forwards qualified Costco leads to the Centah / e-PIC system via the proxy
worker (user brandywineapi). Use the button below to verify the worker can reach e-PIC.
Integration Status
Cloudflare Worker (Proxy)
API bridge to GHL & e-PIC
● Unknown
GoHighLevel API
Opportunities & pipelines
● Unknown
Costco Sync
Pipeline lead ingestion
● Unknown
e-PIC / Centah Sync
Outbound lead delivery
● Unknown
Auto-refresh
5-minute polling
● Off
Reference IDs
These identifiers are configuration references for the deployed workers and KV namespaces. They are not secrets, but should only be shared with authorized staff.