Authenticate requests to the Workflows API using credentials scoped to surveys.readonly. Use OAuth2 or API keys as provided in your developer console.
Beetexting uses its own OAuth client to connect to the Workflows API. In your Beetexting dashboard, enter the API credentials and authorize the integration.
Primary endpoints used in this guide: GET /surveys/ — retrieve all surveys; GET /surveys/submissions — fetch submissions for a survey. Other endpoints exist but are not required for this Beetexting integration.
Trigger: When a new survey is created or updated, Beetexting can start a workflow to send a text message or update a contact.
Actions: Create or update records in Beetexting, enqueue messages, or tag responses for segmentation.
GET /surveys/
Key fields: survey_id, title, status
Trigger: New submission for a survey.
Actions: Create or update contact records, adjust lead scoring, or apply tags based on responses.
GET /surveys/submissions
Key fields: submission_id, survey_id, responder_email
Trigger: Custom events based on API data.
Actions: Update app records, trigger analytics, or notify teams.
N/A
N/A
No-code setup lets you connect, map fields, and automate campaigns without writing code.
Automate surveys to emails, SMS, or in-app messages at scale with simple triggers.
Visual workflow mapping keeps data aligned between the API and Beetexting triggers.
A quick glossary of terms used throughout this guide to help you configure the integration.
Application Programming Interface: a set of rules that lets Beetexting talk to the Workflows API.
A specific URL path you call to access data or trigger actions in the Workflows API.
How you prove your identity to the Workflows API (e.g., API keys or OAuth2) so requests are allowed.
An HTTP callback that lets the API push data to Beetexting when events occur.
Trigger an onboarding text drip when a new survey is submitted by a user to guide them through setup.
Use survey responses to tailor messages and re-engagement campaigns based on answers.
Notify your team instantly when critical survey responses arrive.
Generate a client ID/secret or API key with the surveys.readonly scope in the GHL developer portal.
Authorize Beetexting in the GHL dashboard and run a test pull of a survey to confirm connectivity.
Configure data mappings between surveys data and Beetexting triggers to start automated campaigns.
The GHL Workflows API is the back-end that powers automated workflows. It exposes endpoints to fetch surveys and submissions. This makes it easy to pull data into Beetexting and trigger messaging.
The primary endpoints for Beetexting integration are GET /surveys/ and GET /surveys/submissions. Additional endpoints exist for more complex automations if needed.
Authentication is typically via OAuth2 or API keys. In Beetexting, configure credentials in the app settings and test the connection.
Yes. You can trigger text campaigns from new survey submissions or based on specific responses. Map fields to ensure the right data flows.
Yes. A no-code connector handles setup: authorize, connect, and map fields, with optional templates for common use cases.
GET /surveys/ returns surveys with IDs and metadata. GET /surveys/submissions returns responses for each survey, including responder details.
Docs and rate limits are available on the GHL developer portal. The docs provide endpoint schemas, authentication details, and usage guidelines.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
