Begin by creating a OAuth client in the Funnels API dashboard and grant the necessary scope funnels/redirect.readonly. Then copy the client ID and secret into ablefy’s connection setup to authorize calls to Funnels endpoints.
In the ablefy app settings, enter the Funnels API credentials (client ID, client secret, and redirect URI) to establish a secure connection. After saving, perform a test call to confirm access.
Public endpoints used by this integration include: 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. Additional endpoints 13-17 are available for advanced use if needed.
Trigger when a redirect is created or updated in Funnels
Actions: ablefy can create, update, or delete redirects in Funnels
GET /funnels/lookup/redirect/list; POST /funnels/lookup/redirect; PATCH /funnels/lookup/redirect/:id; DELETE /funnels/lookup/redirect/:id
Key fields: id, source, destination, type, createdAt
Trigger when page or funnel data changes in Funnels
Actions: read pages and funnels, list funnels, retrieve page counts
GET /funnels/page, GET /funnels/funnel/list, GET /funnels/pagecount.readonly, GET /funnels/page/count
Fields: pageId, funnelId, name, status, lastUpdated
Trigger: when media is uploaded or deleted
Actions: delete (DELETE /medias/:fileId) and fetch (GET /medias/:fileId)
DELETE /medias/:fileId
Fields: fileId, filename, mimeType, size
No-code automation: connect Funnels API to ablefy without writing code
Unified workflow triggers and actions across funnels, pages, and media
Pre-built templates and quick start guides to accelerate setup
This glossary defines endpoints, triggers, actions, and fields used in the Funnels API integration with ablefy.
A specific URL path exposed by the GHL API that performs a function such as retrieving or modifying data.
An event in Funnels API that starts an automation in ablefy.
The process of proving identity and obtaining authorization to access the GHL API from ablefy.
A sequence of steps that automates a business process between Funnels API and ablefy.
Automatically log redirect changes and alert your team when redirects break.
Regularly sync page and funnel data to detect mismatches and gaps.
Keep images and videos aligned between Funnels and Ablefy libraries for consistency.
In Funnels API, create OAuth credentials and copy the client ID and secret.
Set the scope to funnels/redirect.readonly and any additional needed scopes for pages and media.
Test the connection by performing sample redirects, reading pages, and uploading a media asset.
Funnels API provides programmatic access to manage funnels, redirects, pages, and media. Use it to automate common tasks without leaving Ablefy. This makes it easier to keep your funnels in sync with your content and campaigns.
Authenticate by creating OAuth credentials in Funnels API and supplying the client ID and secret to Ablefy. After setup, use a test call to confirm access and refresh tokens if applicable.
The funnels/redirect.readonly scope is needed for reading redirect data. Add additional scopes as required for pages and media operations. If you need more access, request the necessary scopes from your Funnels API admin.
Yes, redirects can be read and updated via the given endpoints. Use GET to read, POST to create, PATCH to update, and DELETE to remove redirects as needed.
Test the connection by triggering a sample redirect, fetching a page, and uploading a media asset through Ablefy. Review responses and error messages to validate the integration.
Rate limits depend on your Funnels API plan. Plan for bursts during campaigns and implement retries with backoff in Ablefy to avoid throttling.
Endpoint documentation is available in your Funnels API developer portal and the Ablefy integration guides. Refer to the endpoint list in this page for a quick reference.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
