Generate an API key with the necessary scopes, set access permissions, and authorize requests from Acumbamail to interact with your funnels and redirects.
Create credentials in Acumbamail to securely access Funnels API data and ensure tokens are stored securely and rotated regularly.
– GET /funnels/lookup/redirect/list; – POST /funnels/lookup/redirect; – GET /funnels/page; – 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: a user clicks a redirect within a funnel
Actions: log the click, update contact data, and route the lead to targeted Acumbamail campaigns
Paths: GET /funnels/lookup/redirect/list, POST /funnels/lookup/redirect
Key fields: id, redirectId, url, status, timestamp
Trigger: page viewed or page count reached
Actions: push page data to Acumbamail lists and trigger follow-up emails
Paths: GET /funnels/page, GET /funnels/page/count
Key fields: pageId, funnelId, count, timestamp
Trigger: new or updated funnel
Actions: map funnel data to Acumbamail segments and launch campaigns
Paths: GET /funnels/funnel/list, GET /funnels/funnel/{id}
Key fields: id, funnelId, name, status
Benefit: rapid setup with no coding required
Benefit: easy data flow and automation without developers
Benefit: scalable campaigns via webhooks and triggers
This glossary covers API keys, endpoints, triggers, webhooks, and data fields used when integrating Funnels API with Acumbamail.
A unique token used to authenticate requests to Funnels API.
A URL endpoint that receives real-time event data from services.
A specific URL in Funnels API used to access a resource.
An event that starts an automation or process.
Automatically add new funnel leads to an Acumbamail list and enroll them in a welcome campaign to increase engagement.
Trigger tailored follow-up emails in Acumbamail based on redirect outcomes to boost conversions.
Link funnel analytics to Acumbamail campaigns when milestones are reached (e.g., 50% funnel completion).
In Funnels API, create an API key with the required scope and securely store the token.
Configure GHL to call Acumbamail endpoints when funnel events occur, using the provided endpoints list.
Map key fields (email, name, funnelId) between Funnels API and Acumbamail and run end-to-end tests.
The Funnels API is a RESTful interface that lets you manage funnels, redirects, pages, and related assets. It enables programmatic control over funnel behavior and data. This integration uses those endpoints to automate tasks between Funnels API and Acumbamail. In practice, you can trigger campaigns, update contact data, and track funnel activity without manual steps.
Basic understanding of HTTP requests, authentication, and data mapping helps. While no deep coding is required, some light scripting or a workflow within GHL is helpful to configure triggers and actions. The platform supports no-code to low-code use cases.
Commonly used endpoints include listing funnels, redirects, and page views. For Acumbamail, the redirect and page endpoints are particularly useful for triggering campaigns and updating contact records based on funnel activity.
Yes. You can map fields between Funnels API and Acumbamail such as email, first name, last name, funnelId, and custom fields. Consistent data mapping improves targeting and engagement.
Review the official documentation for endpoint references, best practices, and examples. You can also explore community templates and Zapier integrations to extend capabilities.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
