To access the Contacts API from Zeev, configure OAuth with the Contacts API scope of readonly and provide your credentials in the app settings.
In Zeev, authorize the app to access the Contacts API resources you need and grant the required scopes within the app settings.
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, 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: when a contact is requested or updated, Zeev pulls the contact data along with related tasks
Actions: GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes
GET /contacts/:contactId
contactId, name, email, phone, tasks, notes
Trigger: new or updated contact in Zeev workflow
Actions: POST /contacts/, PUT /contacts/:contactId, POST /contacts/:contactId/tasks
POST /contacts/
name, email, phone, businessId, tasks
Trigger: note or appointment created or updated for a contact
Actions: GET /contacts/:contactId/notes, GET /contacts/:contactId/appointments
GET /contacts/:contactId/notes
notesId, note, startTime, endTime, location
Automate data sync without writing code
Consolidated view of contact data across tasks, notes, and appointments
Rapid setup with prebuilt actions and triggers
Key elements include endpoints, triggers, actions, methods, parameters, and data fields used to move information between Zeev and the Contacts API.
A set of rules that enables Zeev to communicate with the Contacts API and perform operations.
A specific URL path that performs a defined operation on a resource.
The process of verifying identity and granting access to resources.
Permissions granted to an app to access specific resources or actions.
Automatically tag and categorize contacts in Zeev when they engage with emails or tasks via the Contacts API.
Bridge notes with tasks, creating context for each task.
Create calendar events in Zeev from contact relationships.
Configure app credentials and authorize Zeev to access the Contacts API.
Choose endpoints and map fields for sync.
Run tests, verify data flows, and deploy the integration.
Zeev uses OAuth 2.0 to authorize access to the Contacts API. You provide client credentials and grant Zeev the necessary scopes, typically contacts.readonly for read-only access. If write access is required, enable additional scopes in your app settings.
All endpoints listed are available based on your permissions. Common endpoints include retrieving a contact, its tasks, notes, and appointments. You can combine endpoints in a single Zap to create powerful workflows.
Use Zeev’s test mode to simulate data flows, check responses, and verify mappings. Review error logs, adjust mappings, and re-test until successful.
Yes, mappings can be customized in Zeev’s editor. You can map source fields to destination fields and adjust data formats. If the API updates, you can modify the mappings accordingly.
Rate limits apply to API requests. If you reach the limit, Zeev will prompt you to retry after a short interval or batch requests to stay within the quota.
Yes, the integration supports creating and updating records. Use POST to create new contacts and PUT to update existing ones, along with related tasks, notes, and appointments.
For help, consult the Rankr docs and support channels. You can also reach out to our support team for guidance on mapping and troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
