Begin by creating and securely storing your Funnels API credentials. Use OAuth or API keys as provided by the GHL platform, then test the connection within the ABC Trainerize builder.
Authorize ABC Trainerize to access your Funnels API endpoints by granting the required permissions in the connected app settings.
– 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 when a new redirect is created in Funnels API to keep ABC Trainerize in sync, or when a redirect is updated to reflect changes.
Actions: create, update, and delete redirects; synchronize IDs; emit webhook events to both sides.
Primary methods: POST /funnels/lookup/redirect to create; GET /funnels/lookup/redirect/list to read; PATCH /funnels/lookup/redirect/:id to update; DELETE /funnels/lookup/redirect/:id to remove.
Key fields: redirectId, sourceUrl, targetUrl, status
Trigger when ABC Trainerize pages change; update Funnels API pages accordingly.
Actions: sync page details, counts, and visibility; ensure page references align across systems.
Primary methods: GET /funnels/page, GET /funnels/pagecount.readonly, GET /funnels/page/count
Key fields: pageId, pageName, slug, isActive
Trigger: ABC Trainerize updates funnels; Action: Export/Import funnel list to Funnels API.
Actions: Read funnel list; create/update funnels; map fields.
Primary methods: GET /funnels/funnel/list to read; POST /funnels/lookup/redirect to create redirects; PATCH /funnels/funnel/:id to update
Key fields: funnelId, name, slug, defaultRedirectId
Eliminate manual data entry by automatically syncing redirects, pages, and funnel data between the two systems.
Automate funnel performance tracking and media handling with simple UI-based configurations.
Scale integrations quickly without writing code, using ready-made connectors.
Overview of the elements and processes used to connect funnels, redirects, pages, and media between Funnels API and ABC Trainerize.
A URL path that forwards users from a source to a target destination within a funnel.
An HTTP callback that notifies your app when events occur in Funnels API.
A single screen or step in a funnel that users traverse.
A specific API URL and method used to perform actions in Funnels API.
Automatically prune stale redirects and archive old ones to keep your funnels tidy.
Schedule regular checks on page counts and visibility to ensure accurate funnel data.
Create guided onboarding by syncing new funnels and redirects with ABC Trainerize.
Obtain API credentials and authorize ABC Trainerize to access Funnels API.
Identify the endpoints you’ll use and map source fields to target fields in ABC Trainerize.
Test the connection and rollout the integration across your funnels.
You can setup no-code connections using the App Connector. No coding is required, and you can configure triggers, actions, and mappings through the UI. If you need more control, use the Funnels API documentation to customize requests.
For redirects, use GET /funnels/lookup/redirect/list to view redirects, POST /funnels/lookup/redirect to create, and PATCH /funnels/lookup/redirect/:id to update. DELETE /funnels/lookup/redirect/:id removes entries.
Connections are transmitted over HTTPS with OAuth or API keys as configured in the app. Keys are securely stored and rotated per best practices.
Yes. You can use test endpoints and sandbox data in ABC Trainerize to verify behavior before going live.
Yes. Map fields that match your data models, and use transform steps if needed to align formats.
Use the built-in logs and dashboards to monitor sync status and error messages.
If an endpoint changes, update mappings and test the connection again.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
