Use OAuth tokens with the correct scope surveys.readonly to securely access surveys and submissions from the Workflows API.
Zapier authenticates to the Workflows API using OAuth or API keys with token refresh and secure storage in your Zapier account.
GET /surveys/ — lists surveys GET /surveys/submissions — lists submissions for a survey
Trigger: When you need the latest surveys, pull with GET /surveys/ to feed Active Knocker workflows.
Actions: Map survey fields like id, title, and created_at into Active Knocker fields and trigger alerts.
GET /surveys/
id, title, created_at
Trigger: Pull submissions via GET /surveys/submissions to start a workflow when new responses arrive.
Actions: Capture submission_id, survey_id, answers, and submitted_at; feed into Active Knocker events.
GET /surveys/submissions
survey_id, submission_id, answers, submitted_at
Trigger: Combine multiple endpoints in a single workflow for richer automation.
Actions: Merge survey and submission data, perform condition checks, and route to different Active Knocker paths.
N/A (see endpoints above for examples)
N/A
Build complex Active Knocker automations without writing code.
Fast integration with your existing Zapier workflows and data.
Consistent data flow between Workflows API and Zapier, with centralized debugging.
Key elements include endpoints, triggers, actions, and data fields. This guide maps Workflows API endpoints to Active Knocker automations via Zapier.
Application Programming Interface; a set of endpoints like GET /surveys/ used to read and manipulate data.
A specific URL path in an API that performs a defined action such as /surveys/ or /surveys/submissions.
The process of proving identity to access the API, typically via OAuth tokens or API keys, with secure storage and refresh.
Translating API data fields into your app’s fields to ensure accurate automation.
Create a Zap that triggers a live Active Knocker alert whenever a survey is submitted.
Pulls a daily digest of surveys and sends a summary to your team channel.
Append survey outcomes to contact records and trigger follow-ups in Active Knocker.
Authorize using OAuth with scopes: surveys.readonly. Save token securely.
Add GET /surveys/ and GET /surveys/submissions, then map fields to Active Knocker.
Test thoroughly and deploy to production.
The Workflows API exposes endpoints to manage surveys and submissions, enabling automated Active Knocker workflows. Use GET endpoints to read data and feed it into your automations. No-code connectors in Zapier let you trigger actions without writing code. For advanced use, combine multiple endpoints in a single workflow.
You can often set up connections without coding by using the Zapier App Connector. Some basic configuration is required to authorize and map fields. If you need deeper logic, you can add filters and paths within Zapier.
Available endpoints include GET /surveys/ and GET /surveys/submissions. The rest may be added as needed. The page uses these to fetch surveys and submissions to feed Active Knocker.
Authentication is handled via OAuth tokens with the correct scopes. Tokens should be stored securely and refreshed before expiry.
You can pull survey metadata, responses, timestamps, and user details. Map fields as needed to Active Knocker triggers.
Yes. You can schedule pulls or use webhooks/triggers to fetch data when events occur in GHL.
Map API response fields to your Active Knocker fields using Zapier’s built-in mapping tools; test thoroughly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
