Authorize requests to the Funnels API with your API key or OAuth token. Store credentials securely, rotate keys regularly, and scope requests to the minimum permission required.
46elks authenticates via API tokens or basic auth depending on your setup. Keep credentials secret and use HTTPS for all calls.
GET /funnels/lookup/redirect/list; funnels/redirect.write; POST /funnels/lookup/redirect; funnels/page.readonly; GET /funnels/page; funnels/funnel.readonly; GET /funnels/funnel/list; funnels/pagecount.readonly; GET /funnels/page/count; DELETE /funnels/lookup/redirect/:id; PATCH /funnels/lookup/redirect/:id; DELETE /medias/:fileId
Trigger: a new or updated redirect is created in Funnels
Actions: reflect the change in 46elks by updating a related redirect or creating a new one in your campaigns
GET /funnels/lookup/redirect/list
Key fields: redirect_id, funnel_id, destination
Trigger: a page is created or updated in Funnels
Actions: push page data to 46elks or update a contact’s page reference
GET /funnels/page
Key fields: page_id, title, url
Trigger: a new funnel appears in Funnels
Actions: create or update a corresponding record in 46elks
GET /funnels/funnel/list
Key fields: funnel_id, name, status
No coding required—connect, map fields, and automate workflows visually
Real-time data sync so redirects and pages update instantly
Faster go-to-market with reusable automation blocks
This glossary explains terms like GHL API, APPNAME, endpoints, triggers, actions, and key fields used throughout the integration.
The GHL API is the gateway that lets apps access Funnels data to read and update redirects, pages, funnels, and media.
APPNAME refers to the 46elks integration app that connects your GHL Funnels API to external systems.
An endpoint is a specific URL path and HTTP method used to perform an API action.
A trigger starts an automation when a selected event occurs in GHL or APPNAME.
Send real-time alerts via 46elks when a Funnels redirect is created or updated, triggering SMS or voice messages.
Sync page data to 46elks to trigger personalized messages or calls based on page changes.
Batch and schedule updates between Funnels API and 46elks to scale campaigns without code.
Obtain API keys or OAuth tokens for Funnels API and 46elks, and store them securely.
Define which Funnels events will trigger actions in 46elks and map the required fields.
Run end-to-end tests, monitor logs, and enable automation in production.
Both Funnels API and APPNAME can be authenticated with API keys or OAuth tokens. Use the method your team already uses for secure storage and rotate keys every 90 days. Always use HTTPS to protect credentials in transit.
Start with core endpoints to understand data structure: GET /funnels/lookup/redirect/list, POST /funnels/lookup/redirect, GET /funnels/page, GET /funnels/funnel/list. As you validate, add delete and patch endpoints and map key fields to your 46elks records.
No heavy coding is required if you use a no-code integration tool or prebuilt automation blocks. Some light scripting may help with token handling and data transformation, but you can commonly map fields and triggers visually.
Test in a staging environment by triggering Funnels events and confirming data arrives in 46elks. Use logs, retries, and alerts to catch failures and verify data integrity across redirects, pages, and funnels.
Webhooks can push changes from Funnels to APPNAME or be used to poll endpoints for updates. Sign and validate payloads to ensure security and reliability.
No-code benefits include rapid setup, visual field mapping, and reusable automation blocks that span funnels and campaigns. This reduces development time and makes the integration approachable for non-developers.
Endpoint documentation is available in the GHL API docs and the APPNAME integration guide. For deeper customization, consult the API reference and release notes for endpoint specifics and authentication details.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
