Authenticate using API keys or OAuth tokens to securely authorize Runrun-it to call endpoints like GET /contacts/:contactId and related resources.
Grant Runrun-it permission to access Contacts API resources, define scopes, and manage token lifetimes for ongoing automation.
Endpoints include: GET /contacts/:contactId (retrieve a single contact); GET /contacts/:contactId/tasks (retrieve a contact’s tasks); GET /contacts/:contactId/tasks/:taskId (retrieve a specific task); GET /contacts/:contactId/notes (retrieve notes); GET /contacts/:contactId/notes/:id (retrieve a note); GET /contacts/:contactId/appointments (retrieve appointments); GET /contacts/ (list all contacts); GET /contacts/business/:businessId (list by business); contacts.write (write scope); POST /contacts/ (create contact); PUT /contacts/:contactId (update contact); DELETE /contacts/:contactId (delete contact); POST /contacts/:contactId/tasks (create task); PUT /contacts/:contactId/tasks/:taskId (update task); PUT /contacts/:contactId/tasks/:taskId/completed (mark task complete); DELETE /contacts/:contactId/tasks/:taskId (delete task); POST /contacts/:contactId/tags (add tag).
Trigger: when a contact is updated in Runrun-it, fetch the latest details from the Contacts API.
Actions: GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes, then sync to Runrun-it.
GET /contacts/:contactId
contactId, name, email, phone, tasks, notes
Trigger: when a new task is created in Runrun-it, fetch from the Contacts API.
Actions: GET /contacts/:contactId/tasks, GET /contacts/:contactId/tasks/:taskId
GET /contacts/:contactId/tasks
taskId, title, status, dueDate
Trigger: Task updated in Runrun-it, fetch /contacts/:contactId/tasks/:taskId
Actions: GET /contacts/:contactId/tasks/:taskId
GET /contacts/:contactId/tasks/:taskId
taskId, status, description, completed
No-code automation to save time by syncing contact changes automatically.
Centralized data access across apps without writing code.
Faster onboarding for teams with pre-built templates.
A quick glossary of terms and processes to help you implement the integration.
Application Programming Interface that allows programs to talk to each other.
The process of verifying identity and granting access tokens.
A specific URL path or route exposed by an API that performs a function.
A HTTP callback that sends data in real time when an event occurs.
Whenever a contact record changes in the Contacts API, automatically update Runrun-it and create related tasks.
Use webhooks to trigger task creation when a key contact event occurs.
Sync notes from Contacts API into Runrun-it for quick reference.
Register your app, obtain client ID/secret, and authorize Runrun-it to access your data.
Set up endpoint permissions, scopes, and map contact fields to Runrun-it fields.
Run test flows, verify data integrity, then enable production automation.
The Contacts API provides programmatic access to contact records, their tasks, notes, and more via RESTful endpoints. Use standard HTTP methods to read, create, update, and delete data in a structured way. To get started, obtain your API credentials, review the appropriate scopes (such as contacts.readonly or contacts.write), and test in a sandbox before moving to production.
Yes. While low-code options exist, non-developers can set up this integration with templates and guided steps. Begin by mapping fields between Runrun-it and the Contacts API, then test in a safe environment and progressively enable production automation.
Most useful endpoints for Runrun-it are GET /contacts/:contactId to fetch a contact, GET /contacts/:contactId/tasks to pull tasks, and GET /contacts/:contactId/notes to retrieve notes. For write actions, use POST, PUT, and DELETE endpoints with appropriate scopes. Start small and expand as you validate data flows.
Authenticate with OAuth tokens or API keys as configured for your app. Always store credentials securely and rotate tokens regularly. Implement error handling with retries and exponential backoff to manage transient failures.
Absolutely. Use sandbox environments to validate flows before deploying to production. Leverage sample payloads and staged data to ensure the integration behaves correctly without affecting real customers.
Rate limits are documented in the API docs; plan for batching and caching where possible. If limits are reached, implement backoff strategies and stagger requests to maintain smooth operation.
The endpoint list is available in the integration guide and within the Runrun-it connectors docs. We also provide example calls to help you verify flows quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
