Requests to the Contacts API should be authenticated using the Bird Eats Bug integration. Ensure the requested scope is contacts.readonly.
Configure your Bird Eats Bug credentials (API key or OAuth token) to authorize calls to the Contacts API.
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: A contact is selected or updated and a related task is created or updated in the Contacts API.
Actions: Create, update, or attach tasks in Contacts API; sync status back to Bird Eats Bug.
GET /contacts/:contactId/tasks
contactId, taskId, status, dueDate
Trigger: New or updated notes for a contact.
Actions: Create or update notes in Bird Eats Bug and link to the contact; reflect changes in the Contacts API.
GET /contacts/:contactId/notes
contactId, noteId, content, createdAt
Trigger: Contact record is created or updated.
Actions: Retrieve contact details and related appointments; push to Bird Eats Bug.
GET /contacts/:contactId
contactId, name, email, phone, appointments
Automate data syncing without writing code.
Set up real-time triggers for tasks, notes, and appointments.
Easily monitor data flow with built-in analytics.
Key definitions to help you understand endpoints, triggers, actions, and fields in this integration.
A specific API route used to access or modify data.
An event that starts an automation.
An operation performed in response to a trigger.
A data attribute within a resource, like contactId or taskId.
Automatically create Bird Eats Bug contacts when a new contact is created in the Contacts API.
Assign tasks from Contacts API to Bird Eats Bug workflows for seamless task management.
Attach notes from Contacts API to Bird Eats Bug records to provide richer context.
Grant permissions for Contacts API access to Bird Eats Bug.
Select endpoints like /contacts/:contactId to fetch data.
Run tests and deploy the integration.
No coding is required. Use the visual builder to connect Bird Eats Bug with the Contacts API. You can map fields and set up triggers without writing code.
Typically you’ll need the contacts.readonly scope for read access. If you need write access, upgrade accordingly.
Yes. You can sync notes, tasks, and appointments as part of automated workflows between the two systems.
There are rate limits based on your plan. If you hit a limit, the connector will retry after a cooldown.
Use built-in error handling and retries to recover from transient issues.
Field mapping allows you to customize which data is shared and stored.
Yes. You can disconnect anytime from the Bird Eats Bug integration settings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
