To start, connect your Funnels API account and grant the required scope (funnels/redirect.readonly). This enables 17hats to read redirect data, fetch funnel pages, and manage funnel mappings securely.
Allow 17hats to access Funnels API endpoints for redirects, pages, and funnels. Generate an API token or OAuth credential and configure in your integration setup.
List of endpoints used in this integration:\n- GET /funnels/lookup/redirect/list\n- POST /funnels/lookup/redirect\n- GET /funnels/page\n- GET /funnels/funnel/list\n- GET /funnels/page/count\n- GET /funnels/pagecount.readonly\n- DELETE /funnels/lookup/redirect/:id\n- PATCH /funnels/lookup/redirect/:id\n- DELETE /medias/:fileId\n\nNote: Endpoints 13–17 are not required for this page and may be unused in this context.
Trigger: A new contact is created or updated in 17hats.
Actions: Post a new redirect mapping using POST /funnels/lookup/redirect to route leads to the correct funnel and redirect URL.
POST /funnels/lookup/redirect
redirect_id, funnel_id, source_url, target_url, status
Trigger: A funnel page is created or updated in Funnels API.
Actions: Retrieve page data via GET /funnels/page and synchronize title/content to 17hats; optionally pull funnel list via GET /funnels/funnel/list.
GET /funnels/page
page_id, funnel_id, title, content, seo_title
Trigger: Media added or removed in 17hats triggers cleanup in Funnels API.
Actions: Delete media assets in Funnels API with DELETE /medias/:fileId and update related redirect mappings.
DELETE /medias/:fileId
fileId, media_id, status
Automate funnel redirects and page management without writing custom code.
Set up triggers and actions using visual builders or native integration tools for rapid deployment.
Unified data flow between Funnels API and 17hats improves conversion paths and reporting.
Key elements include API endpoints, triggers, actions, and data fields used to connect Funnels API with 17hats. Understanding these helps you design reliable automations.
A set of rules and protocols that allow applications to communicate over the internet.
A specific URL in Funnels API that performs a defined operation when called.
A real-time notification mechanism from Funnels API to 17hats when events occur.
A URL that forwards a user to a target page based on a trigger or rule.
Automatically route new leads to the correct funnel in Funnels API based on contact data in 17hats.
Mirror funnel page metadata from Funnels API into 17hats to keep content consistent.
Attach media assets to redirects for richer landing experiences.
Obtain API credentials for Funnels API and grant 17hats access to the necessary scopes.
Map 17hats triggers to Funnels API endpoints (redirects, pages, funnels) and test thoroughly.
Set up monitoring and dashboards to verify redirects, funnels, and page counts.
Funnels API provides programmatic access to funnels, pages, and redirects. When connected to 17hats, you can automate funnel routing based on contact data and events. This minimizes manual work and ensures consistent experiences across your funnels.\nIn practice, you’ll trigger actions from 17hats and push updates to Funnels API to keep redirects and pages aligned with your customer journey.
Essential endpoints to start include: GET /funnels/page to fetch pages, POST /funnels/lookup/redirect to create redirects, GET /funnels/funnel/list to discover funnels, and GET /funnels/page/count to monitor page metrics. You can expand to DELETE /medias/:fileId for media cleanup as needed.\nThese cover basic create/read/update flows to get a working integration quickly.
Authentication typically uses an API token or OAuth credentials with scopes such as funnels/redirect.readonly. Ensure 17hats is configured to request these scopes and securely store credentials. Test connections in a staging environment before going live.\nRotate credentials periodically and monitor for unusual activity via your integration dashboard.
Yes. You can trigger redirects from 17hats when events occur (new lead, updated contact, or form submission). The Funnels API endpoint POST /funnels/lookup/redirect enables creating or updating redirect mappings that drive users to the correct funnel pages.\nCombine with page data to ensure consistent navigation paths for your customers.
Expect standard HTTP status codes. Implement retries for transient errors (e.g., 5xx) and exponential backoff. Validate input data to minimize 4xx errors, and log failures for audit purposes. Build alerting so you’re notified of repeated failures quickly.
This integration is designed to be approachable for non-developers using no‑code tools or simple automation platforms. Some basic API concepts help, but you can start with point‑and‑click triggers and actions before adding custom logic.
API rate limits and support details are documented in your Funnels API plan. If you hit limits, consider batching requests or scheduling them during off-peak times. For complex needs, contact support to discuss higher limits or dedicated assistance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
