Use your API key or OAuth token to authorize requests to the Contacts API. Include the credential in the Authorization header (Bearer
WooDelivery authentication uses the same token exchange to secure calls to its endpoints. Store credentials securely and rotate keys periodically.
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 when a new or updated contact is created in Contacts API to ensure WooDelivery has up-to-date contact data.
Actions: create or update the contact in WooDelivery; map fields like id, email, firstName, lastName, phone, and notes.
GET /contacts/:contactId
id, email, firstName, lastName, phone, tags
Trigger on new or updated tasks in Contacts API to reflect status in WooDelivery.
Actions: create or update tasks in WooDelivery; map taskId, title, dueDate, status, and related contact.
GET /contacts/:contactId/tasks
taskId, title, dueDate, status
Trigger when notes are added or updated for a contact in Contacts API.
Actions: create or update notes in WooDelivery; attach to the correct contact; include noteId, subject, content.
GET /contacts/:contactId/notes
noteId, subject, content, updatedAt
Fully automated data flows without writing code; quick setup via triggers and actions.
Real-time data synchronization across Contacts API and WooDelivery to keep records current.
Scalable workflows that grow with your business and new endpoints.
This glossary explains API terms, endpoint usage, data fields, and how the integration processes map between Contacts API and WooDelivery.
A URL path that performs a specific action (e.g., GET /contacts/:contactId).
A credential used to authorize API requests and access scoped resources.
A mechanism to notify your app when data changes occur in the connected API.
Translating API data fields to equivalent fields in WooDelivery.
Automatically pull enriched data from Contacts API during sync to enhance contact profiles in WooDelivery.
Create and assign tasks in WooDelivery based on contact activity updates from Contacts API.
Trigger note events to drive follow-ups and reminders in WooDelivery.
Obtain and securely store API credentials for both systems, then test a basic connection.
Define how contact, task, and note fields map between the APIs and the app.
Create a Zapier-style workflow with triggers from Contacts API and actions in WooDelivery.
You can use API keys or OAuth tokens to authenticate requests to the Contacts API. Include the credential in the Authorization header (Bearer
For basic syncing, you typically need endpoints to read contacts and related data: GET /contacts/:contactId, GET /contacts/:contactId/tasks, and GET /contacts/:contactId/notes. When creating or updating, you may also use POST /contacts/ and PUT /contacts/:contactId to ensure WooDelivery has current data; always map fields accordingly.
Data transfer uses TLS encryption in transit and standard API authentication. Store credentials securely (prefer a vault or secret manager), rotate tokens regularly, and limit access to only those who need it. Regular security reviews and least-privilege access help reduce risk in ongoing operations.
Yes, you can customize field mappings. Define a mapping rule that translates Contacts API fields like id, email, firstName, lastName, phone, and notes to the corresponding WooDelivery fields. Test mappings in a sandbox, and consider default values if a field is missing to avoid failed syncs.
There can be rate limits depending on your plan. To avoid hitting limits, batch requests where possible and implement exponential backoff. Use caching and delta-sync strategies to minimize unnecessary calls and maintain responsiveness.
Yes, the integration supports webhooks to push real-time updates when data changes occur on either side. If webhooks are unavailable, rely on scheduled polling to keep data in sync, but webhooks are preferred for immediacy.
API credentials are found in the developer or API portal for both systems. Check the setup guide in Rankr’s docs or product help center for exact steps to generate keys and configure scopes.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
