To securely call Funnels API from AccessAlly, generate API credentials in the Funnels API dashboard and configure them in AccessAlly. Use the scope funnels/redirect.readonly to limit access to redirect data.
Enter the API key or client credentials into AccessAlly’s integration settings. Store secrets securely and rotate them on a regular schedule.
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 user needs a redirect during a funnel step or when a redirect rule is updated.
Actions: fetch existing redirects (GET /funnels/lookup/redirect/list), create new redirects (POST /funnels/lookup/redirect), update redirects (PATCH /funnels/lookup/redirect/:id), or remove redirects (DELETE /funnels/lookup/redirect/:id).
Example methods: GET /funnels/lookup/redirect/list; POST /funnels/lookup/redirect; PATCH /funnels/lookup/redirect/:id
Key fields: id, redirect_url, funnel_id, source, status
Trigger: When new funnel pages are created or existing pages are updated.
Actions: retrieve funnels and pages (GET /funnels/funnel/list and GET /funnels/page), then check counts (GET /funnels/pagecount.readonly).
Example methods: GET /funnels/funnel/list; GET /funnels/page; GET /funnels/pagecount.readonly
Key fields: id, funnel_id, page_id, title, status
Trigger: On-demand reporting and analytics export for leadership dashboards.
Actions: pull complete funnel data (GET /funnels/funnel/list), page data (GET /funnels/page), and counts (GET /funnels/pagecount.readonly) for export.
Example methods: GET /funnels/funnel/list; GET /funnels/page; GET /funnels/pagecount.readonly
Key fields: id, funnel_id, page_count, total_pages
No-code integration lets you connect Funnels API with AccessAlly in minutes without writing code.
Prebuilt endpoints and a clear authentication flow speed up setup and reduce maintenance.
A centralized data model enables automation across redirects, pages, and reporting from a single interface.
A concise glossary of terms used in this guide, including API, endpoints, redirects, and authentication, to help you implement the integration correctly.
An Application Programming Interface that allows AccessAlly to communicate with Funnels API to manage redirects and funnel pages.
A specific URL path you call to perform an action in Funnels API, such as GET /funnels/page or POST /funnels/lookup/redirect.
A rule that forwards a user from one URL to another within a funnel, triggered by an event or condition.
The process of proving identity and securing requests between AccessAlly and Funnels API, typically via API keys or OAuth credentials.
Create a seamless user experience by automatically routing contacts through relevant funnels based on behavior, using Funnels API redirects.
Pull funnel and page counts from Funnels API to power dashboards in AccessAlly, highlighting redirects in need of review.
Automatically create or update funnel pages in response to campaigns, using GET /funnels/page and POST /funnels/lookup/redirect.
Obtain your Funnels API credentials from the GHL developer portal and enter them into AccessAlly’s integration settings.
Configure the endpoints listed above and set the scope to funnels/redirect.readonly to begin with, then expand as needed.
Use a test funnel to verify redirects and page data, fix any issues, then switch to live mode for production.
Authentication uses your Funnels API credentials. In AccessAlly, enter the API key or OAuth client details in the integration settings. Ensure the scope includes redirects access. If you see an authentication error, verify that the credentials are active and that the redirect URL is whitelisted in Funnels API. Regenerate keys if needed and update AccessAlly immediately.
Start with redirects (GET /funnels/lookup/redirect/list) to understand current rules, then create or update redirects (POST /funnels/lookup/redirect, PATCH /funnels/lookup/redirect/:id). Following this, test funnel pages (GET /funnels/page) and funnel lists (GET /funnels/funnel/list) to confirm data flow.
No heavy coding is required. This integration is designed for no-code connections between AccessAlly and Funnels API using prebuilt endpoints and a secure authentication flow. Basic familiarity with API concepts helps, but you can complete setup via guided UI in AccessAlly.
You can pull redirect data, page information, funnel lists, and basic counts for dashboards. This supports reporting on redirects performance, page reach, and funnel health across campaigns.
Credentials are renewed from the Funnels API portal or rotated in your identity provider. Update AccessAlly with the new credentials and re-test connectivity. Best practice is to rotate keys on a quarterly basis or when a risk is detected.
Common errors include invalid credentials, missing scope, or blocked IPs. Resolve by revalidating credentials, confirming the scope, whitelisting the AccessAlly server, and inspecting endpoint permissions. If needed, contact support for endpoint-specific guidance.
Yes. You can automate redirects and funnel updates with no-code tools by triggering endpoints like GET /funnels/lookup/redirect/list and POST /funnels/lookup/redirect based on user actions in AccessAlly. For complex flows, a developer can assist with advanced logic, but many use cases are achievable without code.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
