Authenticate requests to Funnels API using your API key and limit scope to funnels/redirect.readonly for initial setups. Include the API key in the Authorization header as Bearer
Zapier authenticates to Funnels API by storing your API key in a secure connection. Use the API key method and test the connection before building Zaps.
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 on new or updated redirects to keep downstream systems in sync.
Actions to list redirects, check status, and apply updates as needed.
GET /funnels/lookup/redirect/list
id, source, destination, status, updated_at
Trigger when pages or funnels are updated to reflect changes in reports.
Actions to fetch page and funnel lists for dashboards.
GET /funnels/page; GET /funnels/funnel/list
page_id, funnel_id, name, slug
Trigger when media assets are uploaded or changed.
Actions to upload, delete, and reference media files in Funnels API.
DELETE /medias/:fileId
fileId, filename, size, type
Automate redirect management and data flows without writing code.
Create seamless workflows across Funnels API and your apps using triggers and actions.
Scale automations quickly with a visual Zap builder and robust endpoints.
This glossary defines core terms like Redirect, Endpoint, Trigger, and Authentication, plus how they apply to the Funnels API and Zapier App Connector integration.
A mapping that forwards a funnel or page request from one destination to another within a funnel flow.
A specific API path and method used to perform an action with Funnels API.
An event in Funnels API that starts an automation in Zapier.
The process of validating requests using credentials such as an API key or OAuth token.
Set up a Zap to clean up stale redirects, verify destinations, and report anomalies.
Automatically sync page changes to your dashboards and analytics.
Aggregate funnel data into a daily report sent via email or Slack.
Retrieve your Funnels API key and ensure the scope includes funnels/redirect.readonly.
Add a new connection in Zapier using the API key and test the connection.
Create Zaps that use triggers from Funnels API and actions that update redirects, pages, and funnels.
Endpoints include GET /funnels/lookup/redirect/list, POST /funnels/lookup/redirect, GET /funnels/page, GET /funnels/funnel/list, and more. These endpoints let you read redirect lookups, create or update redirects, fetch page and funnel data, and manage media assets as needed. Use the read-only scope initially to explore available data without modifying your setup. As you expand, you can access additional endpoints to manage pages, funnels, and media, enabling richer automation and reporting across funnels and campaigns.
Funnels API authenticates via API keys. Store your key securely in the Zapier connection and include it in the Authorization header as Bearer
If you use the funnels/redirect.readonly scope, you can read redirect data but cannot create or modify redirects. To write redirects or related resources, you must request additional permissions such as funnels/redirect.write and update your connection accordingly. Start with read-only access to validate your setup, then gradually elevate permissions in a controlled manner and monitor activity for security and compliance.
Pages are managed via endpoints like GET /funnels/page and related funnel endpoints such as GET /funnels/funnel/list. Use these to pull page and funnel metadata for dashboards and reports. Combine with redirect data to create complete flow visuals and automation in Zapier. You can also reference media and assets with the provided media endpoints to enrich content and ensure assets stay in sync across systems.
In Zapier, use the Test Connection feature in the Funnels API app to verify credentials and endpoint accessibility. If tests fail, re-check the API key, scope, and base URL, then retry. Once the connection succeeds, build your first Zap using a simple trigger (e.g., new redirect) and a basic action (e.g., create or fetch a redirect). Review error codes in the Zapier task history and adjust headers or payloads as needed.
Rate limits vary by endpoint and plan; monitor your requests and implement exponential backoff to handle retries gracefully. Follow minimal permissions to reduce blast radius and optimize token usage. Cache frequently requested data where appropriate and avoid unnecessary polling by using webhooks or event-driven triggers when supported.
Common issues include invalid API keys, incorrect scopes, or attempting to access non-existent endpoints. Double-check the Authorization header, ensure the scope matches the operation, and confirm the endpoint path and HTTP method. If problems persist, regenerate keys, reauthorize the connection, and test each step in isolation.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
