Use a secure API key from your Workflows API dashboard and protect it with a secret header.
Authenticate requests to 46elks using your account API key and connect with HTTPS.
GET /surveys/, GET /surveys/submissions; additional endpoints are documented in the API reference.
Trigger: A new survey submission arrives in 46elks.
Actions: Create or update a survey record in Workflows API.
HTTP method: POST to /surveys/ (or fetch with GET /surveys/ as needed).
Key fields: id, title, created_at
Trigger: New submission event in 46elks.
Actions: Create submission in Workflows API; map fields accordingly.
Path: GET /surveys/submissions
Fields: submission_id, survey_id, submitted_at
Trigger: Alerts triggered in 46elks
Actions: Push alert payload to Workflows API to start a workflow
Path: POST /surveys/alerts
Fields: alert_id, level, message
Automate data flow without writing code.
Set up triggers and actions in minutes.
Scale your integrations across endpoints quickly.
Understanding the core elements: endpoints, authentication, triggers, and data mapping in this integration.
A URL path in the GHL API that performs a specific action.
The method used to verify and authorize API requests.
A server-to-server callback that triggers workflows.
A data entity exposed by the API.
When a 46elks event happens, push data to Workflows API to create a new survey entry.
Trigger notifications in your team chat via Workflows API when 46elks flags an issue.
Regularly sync and compare 46elks data with Workflows API to highlight mismatches.
Create a secure API key and save it for the connector.
Enter authentication details and endpoint mappings.
Run a test submission and confirm data appears in Workflows API.
Generate a secure API key in the Workflows API dashboard and include it in the Authorization header (Bearer token) for all calls. Keep credentials safe, enable IP whitelisting if available, and rotate keys regularly to minimize risk.
The integration currently exposes endpoints for listing surveys and submissions: GET /surveys/ and GET /surveys/submissions. Additional endpoints may be documented in the API reference; use the provided method paths to map fields and drive workflows.
Yes. Use test mode within Workflows API or sandbox/test data to verify mappings without impacting live data. Run end-to-end tests that simulate 46elks submissions and confirm that results appear in Workflows API and trigger expected workflows.
No extensive coding is required; configure the connector in your GHL account and provide endpoint URLs and API keys. For advanced mappings, a basic understanding of JSON payloads and field mapping helps, but most setups are no-code.
Data mapping is done by selecting fields from 46elks (survey_id, submission_id, etc.) and aligning them with Workflows API fields. Ensure data types match (strings, timestamps) and consider field transformations if needed.
Rate limits depend on both services; monitor API usage in the dashboard and implement retries with backoff. If you hit limits, optimize by batching or staggering requests and consider upgrading your plan.
More resources include the official API reference, developer guides, and the community forum. Reach out to support for custom templates and examples tailored to your 46elks and Workflows API setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
