To authenticate the Workflows API connection, obtain an API key with the scope surveys.readonly and configure OAuth as required. Ensure you grant read access to surveys and submissions.
Authenticate the ActiveDEMAND integration with your app credentials, setting the correct redirect URIs and granting the necessary permissions to read surveys and push submissions.
GET /surveys/ — Retrieve a list of surveys. GET /surveys/submissions — Retrieve survey submissions.
Trigger: When a survey is created or updated in Workflows API, send the change to ActiveDEMAND immediately.
Actions: Create or update ActiveDEMAND records, map fields, and trigger downstream campaigns.
GET /surveys/ and GET /surveys/submissions are used for syncing survey data in real time.
Key fields: survey_id, submission_id, respondent_email
Trigger: Manual or scheduled sync to import existing surveys into ActiveDEMAND.
Actions: Create multiple ActiveDEMAND records, map historical data, align campaigns.
GET /surveys/ and GET /surveys/submissions are used for initial import.
Key fields: survey_id, submission_id
Trigger: Webhooks fire when surveys or submissions change, pushing updates to the other system.
Actions: Update corresponding records in both systems and trigger automations.
Method path: Use webhooks for real-time updates and verify data integrity.
Key fields: webhook_id, event_type, resource_id
Automate survey data flow without writing code.
Reduce manual data entry and errors.
Speed up onboarding with templates and pre-built workflows.
Essential terms and processes used when connecting the Workflows API (GHL) with ActiveDEMAND.
Application Programming Interface: a set of rules that lets software components communicate and exchange data.
A real-time HTTP callback that notifies your systems about events as they happen.
OAuth 2.0 is an authorization framework that enables secure delegated access to resources.
A set of questions and responses used to gather information from users.
Automatically pull survey responses into ActiveDEMAND to enrich contact profiles and personalize campaigns.
Trigger surveys or follow-ups when a campaign reaches a milestone in ActiveDEMAND, expanding reach.
Import historical survey data into ActiveDEMAND to accelerate onboarding and segmentation.
Collect API keys, client IDs, and confirm scopes (e.g., surveys.readonly).
Set up endpoints for surveys and submissions and map fields between systems.
Run tests, verify data flows, monitor logs, and enable ongoing monitoring.
No coding is required thanks to the no-code connectors and predefined field mappings. You can set up the integration with guided steps in minutes. If you have developers, you can customize data transforms and add advanced automations for complex workflows.
You can sync surveys, submissions, and related metadata between ActiveDEMAND and the Workflows API. Common fields include survey_id, submission_id, and respondent_email. Maps let you align these fields to your contact records and campaign data.
The integration uses secure tokens and OAuth for access control. All data in transit is encrypted, and audit logs are available. You can configure IP whitelisting and rate limits for additional security.
To authenticate, create API credentials in the Workflows API and authorize the ActiveDEMAND app with the requested scopes. Then configure those credentials in your connect panel. For ongoing security, rotate keys regularly and monitor access.
Yes. You can customize field mappings to match your ActiveDEMAND contact fields. Use the mapping tool to transform data types and formats as needed. Save templates for reuse across campaigns.
Webhooks are supported for real-time updates. You can configure retries, validation, and security signatures. This ensures timely, reliable data flow between systems.
API docs and developer guides are available in the app’s integrations or developer portal. You can also contact support for tailored guidance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
