Your requests must be authorized with a valid API token and the scope contacts.readonly. Include the token in the Authorization header as Bearer
Getform credentials are used to authorize calls to the Contacts API. Generate an API key or use OAuth credentials as your integration requires, and ensure the token has the required scope.
GET /contacts/:contactId GET /contacts/:contactId/tasks GET /contacts/:contactId/tasks/:taskId GET /contacts/:contactId/notes GET /contacts/:contactId/notes/:id GET /contacts/:contactId/appointments GET /contacts/ GET /contacts/business/:businessId contacts.write POST /contacts/ PUT /contacts/:contactId DELETE /contacts/:contactId POST /contacts/:contactId/tasks PUT /contacts/:contactId/tasks/:taskId PUT /contacts/:contactId/tasks/:taskId/completed DELETE /contacts/:contactId/tasks/:taskId POST /contacts/:contactId/tags
Trigger: A new form submission arrives from Getform for a contact.
Actions: Create or update the contact in the Contacts API; optionally create initial tasks or notes.
POST /contacts/ (to create) or PUT /contacts/:contactId (to update existing).
Key fields: name, email, contactId, businessId
Trigger: Task-related data submitted from Getform.
Actions: Create or update tasks via POST /contacts/:contactId/tasks; mark as completed with PUT /contacts/:contactId/tasks/:taskId/completed.
POST /contacts/:contactId/tasks
Key fields: contactId, taskId, title, dueDate, status
Trigger: Form submissions include notes or tag data.
Actions: Create notes via POST /contacts/:contactId/notes and add tags via POST /contacts/:contactId/tags.
POST /contacts/:contactId/notes
Key fields: contactId, noteId, noteContent, tagName
Fully automated data flow without writing code.
Real-time contact updates across your tools.
Simplified maintenance and faster go-to-market.
This section defines the core elements of the Getform-to-Contacts API integration, including contacts, tasks, notes, and tags, plus the processes that connect form submissions to CRM records.
A person or lead in your system with identifying details such as name and email.
A unit of work linked to a contact, such as a follow-up reminder.
A textual annotation attached to a contact to capture context or history.
A label used to categorize or segment contacts for easier grouping.
Score and route new form submissions to the right pipeline automatically.
Create notes for every form submission to preserve context.
Tag contacts by campaign or source for targeted follow-ups.
In Getform, generate an API key or OAuth credentials. In the Contacts API, obtain an access token with the required scope.
Set up the endpoints you will call and run test requests to validate data flow.
Review test results, set up alerts, and refine payload mappings.
Authentication for the Getform to Contacts API relies on a valid API token or OAuth credentials. Include the token in the Authorization header as Bearer
For syncing contacts, start with GET /contacts/:contactId to retrieve a contact. Use POST /contacts/ to create new contacts and PUT /contacts/:contactId to update existing records. To surface related data, you can pull tasks with GET /contacts/:contactId/tasks and notes with GET /contacts/:contactId/notes. This establishes the core data bridge between Getform submissions and CRM records.
Yes, you can create tasks and notes via the API if your token has write permissions. Use POST /contacts/:contactId/tasks to create tasks and POST /contacts/:contactId/notes to add notes. If your API supports it, you can also update or delete these items with the corresponding PUT and DELETE endpoints.
At minimum, you need read access to view contacts. For creating or updating records, your token must have write permissions (e.g., contacts.write scope). Always apply the principle of least privilege and scope access to only the data your integration requires.
Tagging contacts is done via the tags endpoint. Use POST /contacts/:contactId/tags to add tags to a contact. Ensure your token includes the necessary write scope and that the tag values conform to your tagging taxonomy.
Rate limits vary by provider. Plan for retries with exponential backoff and implement proper error handling to gracefully back off on 429 responses. Monitor usage in dashboards and adjust polling or webhook configurations as needed.
Common errors include 401/403 authentication issues, 404 not found, and 422 unprocessable entity. Verify credentials, scopes, and endpoint paths. Implement retries with backoff, log errors for debugging, and validate payload schemas before sending requests.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
