Access to the Contacts API is secured with OAuth 2.0 Bearer tokens. Instapage will exchange credentials securely and store tokens to authorize calls to read and modify contact data.
Authorize Instapage to interact with Contacts API using a secure access token and scoped permissions. Map permissions to the minimum necessary scope (contacts.readonly) for a safe integration.
1) GET /contacts/:contactId 2) GET /contacts/:contactId/tasks 3) GET /contacts/:contactId/tasks/:taskId 4) GET /contacts/:contactId/notes 5) GET /contacts/:contactId/notes/:id 6) GET /contacts/:contactId/appointments 7) GET /contacts/ 8) GET /contacts/business/:businessId 9) POST /contacts/ 10) PUT /contacts/:contactId 11) DELETE /contacts/:contactId 12) POST /contacts/:contactId/tasks 13) PUT /contacts/:contactId/tasks/:taskId 14) PUT /contacts/:contactId/tasks/:taskId/completed 15) DELETE /contacts/:contactId/tasks/:taskId 16) POST /contacts/:contactId/tags
Trigger: A new Instapage form submission creates or updates a Contact in Contacts API.
Actions: POST /contacts/ to create a contact; PUT /contacts/:contactId to update existing. Map fields like email, first_name, last_name.
POST /contacts/ and PUT /contacts/:contactId
Key fields: email (unique identifier), first_name, last_name, company.
Trigger: Submission creates a note or a task for the contact.
Actions: POST /contacts/:contactId/notes, POST /contacts/:contactId/tasks.
POST /contacts/:contactId/notes and POST /contacts/:contactId/tasks
Key fields: contactId, notes or task details.
Trigger: Contact tagging updates drive segmentation.
Actions: POST /contacts/:contactId/tags to add tags.
POST /contacts/:contactId/tags
Key fields: contactId, tagIds or tag names.
Automate lead capture by syncing form data to Contacts API in real time.
Create follow-up tasks and notes automatically after a form submission.
Tag and segment contacts for personalized follow-ups without writing code.
A concise glossary of terms used in this integration, including endpoints, triggers, actions, and key data fields.
A specific URL path that performs an action on Contacts data.
The method used to verify identity and grant access to the API (e.g., OAuth 2.0 Bearer tokens).
A record in your Contacts database containing fields like email, name, and company.
A label applied to a contact to enable segmentation and targeted actions.
Capture a submission and instantly create or update a contact in the Contacts API, triggering downstream workflows.
Apply tags based on form responses to enable precise audience segmentation.
Create notes or tasks to ensure timely follow-ups after each submission.
Connect Instapage to Contacts API and align form fields with contact fields.
Choose when to push data (on submit, on success, etc.).
Set up the actions (create contact, add notes, etc.) and run end-to-end tests.
Yes. The integration uses OAuth 2.0 Bearer tokens to verify identity and grant access. All data in transit is protected with TLS, and tokens can be rotated or revoked as needed. Store tokens securely and apply the principle of least privilege to limit access to only the necessary contacts data. Regularly review access logs and implement IP restrictions if supported by your environment to maintain a strong security posture.
The connection exposes a range of endpoints for reading and modifying contacts, tasks, notes, appointments, and tags. You can review endpoints like GET /contacts/:contactId, POST /contacts/, POST /contacts/:contactId/tasks, and POST /contacts/:contactId/tags to manage and organize contact data. Use the endpoints that fit your workflow, and document the exact field mappings in your Zapier App Connector configuration for repeatable processes.
You can write and delete contacts using POST /contacts/ to create and DELETE /contacts/:contactId to remove. Updates are done with PUT /contacts/:contactId. Be mindful of data retention policies and confirm deletions with safeguards to avoid accidental data loss. Always back up important contact attributes before performing bulk delete operations.
Yes. You can automate creation of notes and tasks from submissions, such as creating a follow-up task when a form is submitted or adding a note with submission details. This keeps your team aligned and reduces manual data entry. Leverage triggers to ensure actions occur immediately after a submission or on a scheduled cadence.
Usage limits depend on your API plan and rate limits defined by the Contacts API. For typical forms and lead capture, this setup handles frequent submissions without issues. If you anticipate high volume, monitor API usage and apply batching or queuing where appropriate to stay within quotas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
