Access is granted via OAuth 2.0 tokens. Include a Bearer token in the Authorization header, request the opportunities.readonly scope (and more as needed), and rotate tokens securely to protect data.
In 123FormBuilder, configure a connected app and authorize it to access the Opportunities API. You’ll exchange client credentials for access tokens and store them securely, enabling seamless form-to-CRM actions.
GET /opportunities/search — search opportunities; GET /opportunities/:id — retrieve an opportunity by ID; GET /opportunities/pipelines — list pipelines; POST /opportunities — create a new opportunity; PUT /opportunities — write/update opportunities; PUT /opportunities/:id/status — update status of an opportunity; DELETE /opportunities/:id — delete an opportunity;
Trigger: a 123FormBuilder form submission creates a new opportunity in GHL via POST /opportunities.
Actions: map form fields to opportunity fields (name, amount, pipeline_id, stage_id); set default close date; attach contact if available.
POST /opportunities
Required: name, pipeline_id, stage_id; Optional: close_date, amount, contact_id
Trigger: a status field in 123FormBuilder is updated
Actions: PUT /opportunities/:id/status with new status; optionally update related fields; reflect in dashboards.
PUT /opportunities/:id/status
Key: id, status
Trigger: nightly sync to fetch opportunities by pipeline
Actions: GET /opportunities/pipelines and GET /opportunities/search; map results to 123FormBuilder dashboards
GET /opportunities/search
Key: id, name, pipeline_id
Fast setup with no coding required; use visual mappings to connect form fields to opportunity data.
Automate lead-to-opportunity flows and update stages automatically based on form input.
Real-time data syncing improves forecasting and reporting accuracy.
Key elements include API endpoints, authentication, data mappings, triggers, actions, and the flow of data between GHL and 123FormBuilder.
A defined set of endpoints that allow systems to communicate and perform operations on data.
A specific URL path used to perform a particular action in the API.
A callback URL that notifies your app of events like new submissions or status changes.
An authorization framework that issues access tokens for API calls.
Automatically create opportunities from submissions and keep field mappings in sync.
Pull opportunities by pipeline into 123FormBuilder dashboards for quick insights.
Trigger follow-up tasks in 123FormBuilder when opportunity status changes.
Create API credentials in GHL and authorize 123FormBuilder to access the Opportunities API.
Define mappings from form fields to opportunity fields (name, value, pipeline, stage, owner).
Run a test submission, verify data flows into GHL, then enable automated runs.
Field mapping translates form data into GHL opportunity fields. Start with required fields like name, pipeline_id, and stage_id, then add optional fields such as close_date and amount. Use transformations to combine or format values when needed. Test mappings with sample submissions to ensure data lands correctly in GHL.
No coding is required for the basic connection. The integration uses visual triggers and actions to connect 123FormBuilder to the Opportunities API. If your workflow needs custom logic, you can extend it with webhooks or additional processing steps, but it isn’t mandatory.
Data travels over HTTPS with OAuth 2.0 tokens. Use scoped tokens tied to your app and rotate credentials regularly. Store tokens securely and apply least-privilege access by choosing the appropriate scope (readonly vs write).
For basic syncing, POST /opportunities creates records, PUT /opportunities/:id/status updates status, and GET /opportunities/search retrieves records. GET /opportunities/:id helps verify a specific record. DELETE /opportunities/:id removes an unwanted record if needed.
Yes. Map the form’s status field to the opportunity status and push updates via PUT /opportunities/:id/status. Ensure the form values map to valid GHL status values to avoid errors.
Retry behavior is controlled by your integration settings. Common patterns use exponential backoff (e.g., retry after 1, 5, then 15 minutes) to respect API rate limits while maximizing recoveries.
Rate limits and quotas are documented in the API reference and in your GHL developer account. If you approach limits, consider batching writes, staggering requests, or requesting higher quotas through support.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
