To begin, generate an API key in Funnels API with the required scope funnels/redirect.readonly and securely store it. Use this key to authorize the integration within the GHL App Connector, enabling safe data exchange between Funnels API and 4Degrees.
In 4Degrees, configure the app to request access to Funnels API endpoints such as redirects, pages, funnels, and media. Use the provided redirect URI from the GHL App Connector and grant the minimum required scopes.
– 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 – GET /funnels/pagecount.readonly – GET /funnels/page/count – DELETE /funnels/lookup/redirect/:id – PATCH /funnels/lookup/redirect/:id – DELETE /medias/:fileId
Trigger whenever funnels redirects are created or updated to keep 4Degrees in sync with redirect paths and statuses.
Actions: create, update, or delete redirects; reflect changes in 4Degrees dashboards and workflows.
Methods and paths: GET /funnels/lookup/redirect/list, POST /funnels/lookup/redirect, PATCH /funnels/lookup/redirect/:id, DELETE /funnels/lookup/redirect/:id
Key fields: id, redirectPath, status, createdAt
Trigger on page or funnel updates to keep page counts and funnel lists aligned in real-time.
Actions: fetch funnel and page lists; read page count to populate dashboards.
Methods: GET /funnels/page, GET /funnels/funnel/list, GET /funnels/page/count
Key fields: pageId, funnelId, count, lastUpdated
Trigger when new media is added or updated in Funnels to sync with 4Degrees assets.
Actions: delete and fetch media records; update asset references in 4Degrees.
Methods: DELETE /medias/:fileId (and related media endpoints as needed)
Key fields: fileId, assetName, mimeType, size
No-code automation to build workflows visually without writing code.
Faster time-to-value with quick setup and drag-and-drop configuration in the App Connector.
Scalable integrations that you can reuse across multiple funnels and pages.
Core elements and processes include endpoints, triggers, actions, and fields that define how Funnels API and 4Degrees communicate via the GHL App Connector.
A set of functions that lets applications request and exchange data programmatically.
A specific URL that performs an action or retrieves data from a service.
An event that starts an automation in your workflow.
The task performed by an integration after a trigger.
When a new funnel is created in Funnels API, automatically update 4Degrees dashboards and reports.
Schedule periodic health checks on redirects to ensure accuracy and user experience in 4Degrees.
Automatically pull Funnels media assets into the 4Degrees asset library for quick access and reuse.
Generate the API key with the required scopes and store it securely.
Authorize the app and select the endpoints you want to use.
Run test calls, validate data, and go live.
Yes, this integration uses encryption in transit and at rest, and access is token-based with scoped permissions. Secrets are stored securely and rotated regularly. You can enable retries and built-in error handling to minimize disruption. Regular audits and least-privilege access help keep your data safe.\n\nSecurity best practices include using unique API keys per environment, monitoring for unusual activity, and restricting endpoints to only what’s needed for your workflows.
No coding is required to set up the core flow. The GHL App Connector provides a visual interface to configure triggers, actions, and data mappings. You can leverage prebuilt templates and customize only the fields you need. If you ever need more control, optional advanced settings allow for fine-tuning without writing code.\n\nThis makes it accessible for teams to deploy automations quickly while maintaining flexibility for future changes.
The integration exposes several endpoints used for redirects, pages, funnels, and media. Core endpoints include redirects lookup/list, redirect create, page and funnel retrieval, and media management. You can tailor which endpoints are active to match your workflow and data strategy.\n\nIf a required endpoint isn’t exposed, you can rely on polling or batched calls to maintain data alignment between Funnels and 4Degrees.
Error handling includes retry logic, clear error messages, and status codes that help you identify root causes. You can configure retry limits and backoff strategies to reduce failed calls. Logging and alerting make it easy to monitor and resolve issues quickly.\n\nFor persistent problems, consult the integration docs or contact support for guidance on mapping errors to your workflow.
Data mappings let you define which fields flow between Funnels and 4Degrees, including identifiers, statuses, timestamps, and asset references. You can customize how redirects, pages, and media are represented in 4Degrees to fit your data model.\n\nTemplates and field mappings can be saved for reuse across multiple funnels and projects, ensuring consistency.
Latency depends on API calls and polling frequency. Real-time updates are possible for some triggers, while others may update on a scheduled cadence. In typical setups, data syncs within seconds to minutes, depending on your configuration and network constraints.\n\nFor critical data, you can configure webhooks or frequent polling to minimize delay.
Logs and activity are available in the App Connector dashboard and the target app’s activity feeds. You can filter by time, endpoint, and status to diagnose issues. Detailed call traces help you audit changes and verify successful data transfers.\n\nSet up alerts for failures to stay informed and maintain smooth operations.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
