Authenticate using an API key or OAuth token and apply the forms.readonly scope. Attach the token to requests to read forms and submissions securely.
Pair Acuity Scheduling credentials with your Forms API keys. Use secure storage for credentials and test a read of GET /forms/ to confirm access.
– GET /forms/; – GET /forms/submissions; (more endpoints available as you expand the integration)
Trigger: a new form submission is received via GET /forms/submissions
Actions: create or update a contact in Acuity Scheduling; attach submission data as notes
GET /forms/submissions
Key fields: form_submission_id, form_id, submission_timestamp, respondent_name, respondent_email
Trigger: fetch /forms data to populate scheduling fields
Actions: create or update Acuity Scheduling customer profiles with mapped form data
GET /forms/
Key fields: form_id, form_title, form_fields
Trigger: submission data triggers appointment scheduling events
Actions: create or update appointments in Acuity Scheduling; schedule reminders
GET /forms/submissions
Key fields: appointment_id, date, time, form_submission_id
Automate data flow without custom coding or middleware
Achieve real‑time syncing of form responses to scheduling records
Centralized visibility with a single dashboard for forms and appointments
This glossary covers API endpoint, authentication, form submission, and webhook concepts used in the integration.
A URL exposed by an app that lets you access data or trigger actions programmatically.
The process of verifying identity and permissions before granting API access.
A record of a user’s responses submitted from a form.
A callback URL that notifies your systems when an event occurs.
Create a precise field mapping so names, emails, and custom fields land in the right spots in Acuity Scheduling.
Automatically schedule appointments based on form responses to reduce manual data entry.
Implement retries, clear error messages, and alerting for failed API calls.
Generate and securely store API keys for both Forms API and Acuity Scheduling, then validate access.
Create mappings between form fields and scheduling fields to ensure correct data flow.
Run test submissions, confirm data sync, and deploy to production with monitoring.
No coding is required for the basic setup. Use GET /forms/ to fetch form definitions and GET /forms/submissions to retrieve responses. Map the relevant fields and enable the connection in your automation tool. This keeps your data flowing without writing code. In most cases, you can set up a reliable sync in under 30 minutes.
You can push common fields like name, email, phone, and custom form fields into Acuity Scheduling. Field mapping ensures data lands in the right spots on the scheduling side. Depending on your forms, you may also push form submissions as notes or appointment data.
For basic syncing, you typically need GET /forms/ and GET /forms/submissions. These endpoints let you pull form definitions and responses. Authentication and simple field mappings complete the setup; more endpoints can unlock advanced features.
Authentication uses API keys or OAuth tokens with the forms.readonly scope. Attach credentials to each request. Rotate keys regularly and store them securely in your integration platform.
Yes. Create a field mapping between your form fields and Acuity Scheduling fields. This ensures that names, emails, and custom fields map to the correct scheduling fields automatically.
When a request fails, you’ll receive an error response. Implement retries with exponential backoff and log errors. Use clear messages to diagnose issues quickly, and monitor retry counts.
Monitor status via your integration platform dashboards or webhooks. Set up alerts for failures and track successful syncs to ensure ongoing reliability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
