Obtain OAuth credentials and request the scope: contacts.readonly. The connector stores tokens securely and uses them for all requests to the Contacts API.
Create or configure the Cardly integration, paste in the API client id and secret, and select the allowed scope. Authorize the connection to enable data flow.
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 Cardly contact is created to mirror the contact in Contacts API and start related task creation.
Create or update the contact in Contacts API and pull in related tasks, notes, and appointments.
POST /contacts/
name, email, phone, externalId
Trigger on note updates in Cardly to sync with Contacts API notes.
Create, update, and fetch notes via endpoints like GET /contacts/:contactId/notes and POST /contacts/:contactId/notes.
GET /contacts/:contactId/notes
contactId, notesId, noteContent
Trigger when a business profile is updated to sync all associated contacts.
Batch create or update contacts via POST /contacts/ and update via PUT /contacts/:contactId.
POST /contacts/
businessId, contactList, mappingFields
No-code data sync eliminates manual entry and reduces errors.
Visual workflow setup with the Zapier App Connector makes automation accessible to non-developers.
Faster time-to-value thanks to ready-to-use endpoints, triggers, and actions.
This glossary covers endpoints, methods, triggers, and key field mappings used in the integration.
A person or organization stored in your CRM with unique identifiers such as name, email, and phone.
A specific API route that performs a function, such as retrieving or updating data.
An event in Cardly that starts an automation, such as a new contact being created.
An operation performed by the integration, for example creating or updating a record.
Automatically create a Cardly contact when a new lead is added to your CRM and assign initial tasks.
Pull notes, tasks, and appointments into Cardly to view everything in one place.
Use batch endpoints to sync large contact lists from your CRM into Contacts API and Cardly.
Register API access in the Contacts API and obtain client_id, client_secret, and the appropriate scope.
Enter credentials in Cardly, set scope to contacts.readonly, and select endpoints to sync.
Run a test sync, verify data mapping, review logs, and promote to production.
You can sync core contact data, notes, tasks, and appointments between Cardly and the Contacts API. This keeps both systems up to date without manual entry. The integration can map fields like name, email, phone, and company to ensure accurate records.
Basic setup requires no extensive coding. You will configure the Cardly connector with API credentials and map key fields via a guided UI. Advanced needs can use simple automation rules without writing code.
A minimal sync often uses GET /contacts/:contactId, POST /contacts/, PUT /contacts/:contactId, and GET /contacts/:contactId/tasks to align contact records and tasks. You can expand with notes and appointments as needed.
Yes. You can create and update tasks from Cardly via the API endpoints such as POST /contacts/:contactId/tasks and PUT /contacts/:contactId/tasks/:taskId. Changes sync back to Cardly automatically.
Authentication tokens are refreshed automatically by the connector when needed. You will not need to re-authenticate for every action, but long-lived sessions may require periodic re-authorization.
The connection uses standard OAuth tokens over TLS. Credentials are stored securely in the Cardly connector and access is restricted by scope (e.g., contacts.readonly).
Logs and error details are accessible in the Cardly connector’s dashboard under Integration Logs, with any failed endpoint calls flagged for quick troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
