To connect, generate an API key or use OAuth depending on your setup; ensure scope: contacts.readonly; keep credentials secure.
Zapier handles the OAuth flow or API key management on your side; configure in your Zap settings.
Key endpoints include: 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: A new TikTok lead is captured and sent to Zapier, which creates or updates a contact (POST /contacts/ or PUT /contacts/:contactId) in the Contacts API.
Actions: attach notes, add tasks, or apply tags to the contact based on lead data.
Primary methods: POST /contacts/ for new leads; PUT /contacts/:contactId for updates.
Key fields mapped: email, firstName, lastName, phone, leadSource = TikTok, leadId, and custom fields.
Trigger: When a contact is updated, automatically fetch and sync related tasks and notes.
Actions: create tasks, update notes, and align status fields.
Methods: GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes
Key fields: contactId, taskId, noteId, status, dueDate.
Trigger: A lead qualifies and triggers an appointment creation in the Contacts API.
Actions: create an appointment, add follow-up notes, and tag as ‘Scheduled’.
Methods: POST /contacts/:contactId/appointments
Key fields: contactId, appointmentId, dateTime, location.
No-code setup lets you connect TikTok leads to your CRM without writing a line of code.
Automated bidirectional sync keeps data fresh across platforms.
Visual workflow builder lets you map fields intuitively and test connections instantly.
This glossary defines API endpoints, triggers, actions, method paths, and key fields used in the integration.
A specific URL path and method that performs a defined operation against the Contacts API.
An event in TikTok or Zapier that starts a workflow in the integration.
An operation executed as a result of a trigger, such as creating a contact or updating a task.
Mapping between lead data fields (email, name, etc.) and Contacts API fields.
Automatically create or update a contact as soon as a TikTok lead is captured, triggering downstream tasks.
Score leads in TikTok data, route to appropriate tags and tasks in the Contacts API.
When a lead qualifies, automatically create an appointment via /contacts/:contactId/appointments and notify your team.
Obtain API keys or set up OAuth, then test the connection in Zapier.
Match TikTok lead fields to Contacts API fields (email, name, phone, custom IDs) using the mapper.
Create a Zap: trigger TikTok lead capture, then actions like create contact, add notes, create tasks, or schedule appointments; test thoroughly.
The Contacts API endpoints include GET operations to fetch contacts, tasks, notes, and appointments, as well as POST, PUT, and DELETE operations to create, update, and remove data. This enables you to pull in TikTok lead data, then push updates back to the CRM as needed. You can retrieve a contact with GET /contacts/:contactId and fetch related tasks with GET /contacts/:contactId/tasks for a complete view of lead activity.
Authentication for the Contacts API typically relies on API keys or OAuth. Securely store credentials, rotate keys periodically, and scope permissions (e.g., readonly vs write) according to your workflow. In Zapier, configure connected accounts to handle the OAuth flow or key-based authentication for each Zap.
Field mapping is done in Zapier’s mapper interface. Map essential lead fields (email, firstName, lastName, phone) to the corresponding Contacts API fields. Include the TikTok lead ID and source as custom fields to preserve origin and enable accurate deduplication.
Rate limits depend on your API plan. If you hit limits, spread calls over time or use batching where supported. Implement error handling in Zapier to retry requests or pause workflows when limits are approached.
In Zapier, use the Test Trigger and Test Action tools to validate each step. Check the API responses, map fields, and verify that created or updated records appear correctly in the Contacts API. Use sample data from TikTok to confirm end-to-end functionality.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
