To begin, obtain a secure API key or OAuth token from GHL. Store credentials safely in your app and rotate them every 90 days. You’ll use these credentials to authorize calls to the Funnels API endpoints listed later.
Connect Actionstep via OAuth2 or API keys as supported by your workspace. Keep credentials in a secret manager and run a quick connectivity check before enabling live sync.
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 funnels/pagecount.readonly GET /funnels/page/count DELETE /funnels/lookup/redirect/:id PATCH /funnels/lookup/redirect/:id DELETE /medias/:fileId
Trigger when a redirect entry is created or updated in Funnels API, and propagate the change to Actionstep records that reference that redirect.
Actions: fetch redirect data, update related Actionstep activities, and maintain a consistent mapping between funnels redirects and Actionstep campaigns.
GET /funnels/lookup/redirect/list to pull existing redirects; PATCH /funnels/lookup/redirect/:id to update; DELETE as needed.
redirect_id, funnel_id, actionstep_campaign_id
Trigger when a funnel page is created or updated, then mirror the page metadata in Actionstep for reporting.
Actions: pull page data via GET /funnels/page, create/update corresponding Actionstep records, and sync page counts with funnels/pagecount.readonly.
GET /funnels/page and GET /funnels/funnel/list as needed to assemble page-to-funnel mappings.
page_id, funnel_id, page_title
Trigger when media assets are added or removed in Funnels API, ensuring Actionstep references stay up to date.
Actions: fetch media details (DELETE /medias/:fileId when needed), and link assets to campaigns in Actionstep.
GET /medias/:fileId for asset lookup; DELETE /medias/:fileId for cleanup.
fileId, asset_id, campaign_id
Create powerful automations without writing a line of code—map funnels data to Actionstep with drag‑and‑drop workflows.
Keep data synchronized in real time, reducing manual updates and errors across platforms.
Easily reuse endpoints and triggers for future integrations across marketing and sales workflows.
This glossary defines common terms used in the Funnels API and Actionstep integration, including endpoints, triggers, actions, authentication, and data payloads.
A set of rules and endpoints that allow applications to communicate with Funnels API and Actionstep.
A token-based authorization framework used to grant access to protected resources without sharing passwords.
A URL exposing a specific function of the API that you can call to retrieve or update data.
The data sent with an API request or returned in a response, typically in JSON format.
Automatically map new Actionstep contacts to funnels based on tags or lifecycle stage, triggering Redirect lookups in Funnels API as needed.
Sync pagina changes instantly to Actionstep so teammates can see up-to-date funnel content in client records.
Tie media assets from Funnels API to Actionstep campaigns to streamline delivery and reporting.
Obtain and securely store API keys or tokens for both services, then verify connectivity with a quick ping.
Select the endpoints you’ll use, set polling intervals, and configure webhooks to receive updates.
Create automation in Actionstep to call Funnels API and handle responses, updating records as data changes.
No-code integration is possible using pre-built connectors and workflows. You can map data fields between Actionstep and Funnels API using visual builders. In some cases, lightweight scripts can help with mapping logic, but most setups run entirely in UI-based automation. This makes it easy to start small and scale up as needed. If you run into edge cases, consider using the endpoints for direct calls to fetch or update data and then reflect changes in Actionstep.
GHL typically supports API key or OAuth 2.0 token-based authentication. Choose the method your workspace supports and ensure you rotate credentials regularly. Use a secret manager for secure storage and test credentials with a quick connectivity check. For added security, restrict API keys to only the required scopes (e.g., funnels/redirect.readonly, funnels/page.readonly).
The critical endpoints depend on your use case. For redirects, use GET /funnels/lookup/redirect/list and PATCH /funnels/lookup/redirect/:id. For pages, use GET /funnels/page and GET /funnels/funnel/list. If you’re unsure, start with the core redirects and pages endpoints and expand as you validate data flows. Always document your chosen endpoints for maintenance and auditing.
Test connectivity using sandbox or developer modes provided by GHL and Actionstep. Run a small dataset through a single end-to-end flow and verify the results in both systems. Check for errors in API responses, then fix mappings or permission scopes before enabling production sync. Enable logging so you can trace requests and responses if issues arise.
Historically imported data can be synced by running a one-time import script against the endpoints and then turning on periodic sync. Some platforms charge per record sync, so plan data volumes accordingly. Use webhooks to capture changes moving forward and avoid re-importing duplicates. Carefully map unique identifiers to prevent duplicates.
Poll intervals depend on your data needs and rate limits. Start with a moderate interval (e.g., every 5–15 minutes) and adjust based on latency and quota usage. Some guidance: cache frequently requested data to reduce unnecessary calls. If you need real-time updates, consider webhooks or event-driven patterns where available.
API rate limits and quotas are published in the provider docs. Monitor usage in the dashboard and apply backoff strategies for 429 responses. If you anticipate spikes, pre-warm or batch requests, and stagger calls to avoid hitting limits. Contact support if you expect sustained high-volume activity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
