Use a secure API key or OAuth token to authorize calls from 123FormBuilder to the Workflows API. Ensure the scopes include surveys.readonly for read access.
During setup, 123FormBuilder will request permission to access your Workflows API resources. Approve to enable data flow for surveys and submissions.
– GET /surveys/ – Retrieve all surveys – GET /surveys/submissions – Retrieve survey submissions – Note: Additional endpoints are available in the API docs for advanced use.
Trigger: when a new 123FormBuilder submission is created, push data to the Workflows API to create or update a survey submission.
Actions: map form fields to survey fields, format dates, and handle errors with retries.
Method path: POST to the Workflows API submissions endpoint.
Key fields: submission_id, form_id, survey_id, respondent, timestamp
Trigger: updates in Workflows API propagate back to 123FormBuilder when a submission is edited.
Actions: push edits to 123FormBuilder forms, keep a history, handle conflicts.
Method path: PATCH to the submission resource in Workflows API.
Key fields: submission_id, last_updated
Trigger: schedule a batch pull/push (e.g., hourly) to sync data between systems.
Actions: batch-create or update submissions, deduplicate records, and maintain version history.
Method path: POST to batch or bulk submissions endpoint.
Key fields: batch_id, timestamp, status
Automate data transfers without writing code, saving time and reducing errors.
Eliminate manual data entry and ensure consistent data across apps.
Fast setup with drag-and-drop builders and ready-made templates.
This section defines API, endpoint, trigger, action, and field mapping to describe how 123FormBuilder connects to the Workflows API.
Application Programming Interface: a set of rules that lets software programs communicate and share data.
A specific URL in an API that performs a function, such as retrieving surveys or submitting data.
An event that starts a workflow, such as a new form submission in 123FormBuilder or a new record in Workflows API.
A operation performed in response to a trigger, such as creating or updating a submission in an API.
Automatically create a Workflows API survey when a 123FormBuilder form is submitted, with fields mapped to survey questions.
Push updated responses from Workflows API back into 123FormBuilder for real-time visibility.
Set up nightly exports to your data warehouse for archival and reporting.
Create or retrieve an API key from Workflows API and configure OAuth scopes.
Authorize 123FormBuilder to access surveys and submissions in Workflows API.
Map your form fields to survey fields and run a test to confirm data flow.
You will need API credentials from Workflows API and grant access to surveys and submissions. Use either an API key or OAuth token. Then configure the mapping between 123FormBuilder fields and Workflows API survey fields. This setup requires no code. You can test the connection by submitting a test form and confirming the data appears in Workflows API.
Use OAuth with scopes that cover surveys.readonly and submissions.read for read access. If you need write access, request the appropriate scopes and ensure your app is approved for those permissions. Store credentials securely and rotate keys periodically.
The primary endpoints are the surveys and submissions endpoints. Additional endpoints exist for advanced scenarios and will be available in your API docs. Consult the API reference for endpoint-specific parameters and response formats.
Create a test form in 123FormBuilder and run a test submission. Check Workflows API to confirm the submission was created and mapped fields align correctly. Use a staging environment when possible to avoid impacting live data.
Yes. Field mapping lets you align 123FormBuilder fields with Workflows API survey fields. Update mappings as your forms or surveys evolve and re-test to ensure data integrity. Keep a changelog of mappings for troubleshooting.
Errors are surfaced in the integration logs. Implement retry logic and backoff to handle transient failures. If an error persists, verify credentials, endpoints, and field mappings. Enable alerting to notify your team when critical failures occur.
Yes. No-code tools and templates allow you to set up common flows quickly. You can also use visual mapping to align fields and configure triggers and actions without writing code. For complex use cases, combine pre-built templates with custom mappings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
