Authenticate requests with an API key from your GHL account. Include the key in the Authorization header as Bearer
Airfocus uses the connected GHL API credentials to read surveys and submissions. Keep tokens secure and rotate keys regularly; follow your organization’s security policies when sharing access.
– GET /surveys/ — retrieve all surveys – GET /surveys/submissions — retrieve all submissions for surveys
Trigger: When a new or updated survey is detected via GET /surveys/
Actions: Create or update corresponding records in airfocus with survey title, status, and metadata.
GET /surveys/
survey_id, title, description, last_modified
Trigger: New survey submission detected via GET /surveys/submissions
Actions: Create a feedback item in airfocus with submission data and respondent details
GET /surveys/submissions
submission_id, survey_id, respondent_email, submitted_at
Trigger: Daily scheduled pull of surveys via GET /surveys/
Actions: Upsert survey records in airfocus to keep data fresh
GET /surveys/
survey_id, title, last_modified
Fast setup with a no-code bridge between survey data and airfocus artifacts.
Automatic, ongoing data synchronization reduces manual data entry and errors.
Scales across teams and projects with consistent, rules-based data flow.
Key elements include API endpoints, authentication, triggers, actions, and field mappings that connect data from Workflows API to airfocus.
A specific URL path used to access a resource in the API, such as /surveys/ for retrieving surveys.
An event that starts an automation, like a new survey submission or a survey update.
An operation performed as a result of a trigger, such as creating or updating an airfocus item.
Assigning data fields from the API to corresponding fields in airfocus to ensure accurate data transfer.
Auto-create airfocus templates when new surveys appear in Workflows API, with mapped fields ready to use.
Generate airfocus tasks or issues from survey submissions for immediate follow-up.
Send daily digest summaries to your team, blending survey results with airfocus progress.
Generate an API key in GHL with scope surveys.readonly and securely store it for use in airfocus.
Add a new integration, selecting the Workflows API, providing the API key and base URL, and configuring scopes.
Create field mappings (survey_id, title, last_modified, submission_id, respondent_email) and run a test to confirm data flows correctly.
The Workflows API endpoints let you read surveys and submissions. Use GET /surveys/ to pull survey metadata and GET /surveys/submissions to fetch responses. Apply the surveys.readonly scope to protect data. Always respect rate limits and paginate results for large data sets. You can map this data into airfocus to generate or update records, projects, or cards that reflect the latest survey activity, enabling timely actions without writing code.
Security is built-in with API keys and scoped access. Store keys securely and rotate regularly. Use HTTPS for all requests and limit permissions to the minimum required scope. If your team shares credentials, use a secure vault and implement access controls, auditing, and secret rotation policies as part of your security posture.
Yes—this integration is designed for no-code use, via your GHL account and airfocus. No custom coding is required to get started, only enabling the integration and configuring mappings. You’ll set up authentication, select endpoints, and define field mappings within the UI, then test the flow to ensure data moves correctly.
Yes, you can map only certain fields. Field mapping lets you choose which data points are synced from Workflows API to airfocus, keeping flows clean and focused on essential attributes. Adjust mappings anytime to evolve your data model as requirements change.
The core endpoints used on this page are GET /surveys/ and GET /surveys/submissions. These provide survey metadata and responses, respectively. Additional endpoints may exist in your GHL account; contact support if you need to enable more endpoints for broader data coverage.
To test the connection, generate or use a test API key with the surveys.readonly scope, configure the integration in airfocus, and run a test pull. Check that airfocus items are created or updated as expected and review any error messages for field mismatches. Review rate limits and retries to ensure reliable operation in production.
API keys are created in GHL under Settings > API Keys. Generate a key with the required scopes (e.g., surveys.readonly) and store it securely. Rotate keys regularly and update your integrations accordingly. If you lose a key or suspect compromise, revoke it and issue a new one following your security policies.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
