Required scope is contacts.readonly which allows Sprig to view contacts tasks notes and related data.
To enable the connection you will authorize Sprig to access your Contacts data via OAuth and you can revoke access anytime.
Endpoints include GET /contacts/:contactId to retrieve a single contact; GET /contacts/:contactId/tasks to list tasks for a contact; GET /contacts/:contactId/tasks/:taskId to get a specific task; GET /contacts/:contactId/notes to list notes; GET /contacts/:contactId/notes/:id to get a note; GET /contacts/:contactId/appointments to retrieve appointments; GET /contacts/ to list all contacts; GET /contacts/business/:businessId to get contacts by business. The API also supports creating, updating, and deleting data via POST, PUT and DELETE as shown in endpoints 10 through 16 and 17.
Trigger when a contact is opened or updated to fetch latest data
Actions pull contact data and sync tasks notes and appointments
GET /contacts/:contactId
Key fields contactId firstName lastName email
Trigger when a new task is created or updated for a contact
Actions create update and sync tasks and fetch task lists
GET /contacts/:contactId/tasks
Key fields taskId title status dueDate
Trigger when a note is added or updated for a contact
Actions retrieve notes create notes and manage tags
GET /contacts/:contactId/notes
Key fields noteId note createdAt
Automate data flows without writing code
Access up to date contact data across apps in real time
Scale automations with reusable templates and triggers
Glossary of common terms used in this integration and how they map to the endpoints
A unique identifier for a contact in the Contacts API
Unique identifier for a task in the contact s task list
Unique identifier for a note linked to a contact
Identifier for a business associated with a contact
Set up a workflow that creates a starter task in Sprig when a new contact is added via the Contacts API
Automatically apply tags based on notes or contact attributes to segment audiences
Push appointment data from the Contacts API into Sprig to trigger reminders and follow ups
Authenticate Sprig using OAuth and grant the requested scope contacts.readonly
Select endpoints such as GET /contacts/:contactId and GET /contacts/:contactId/tasks to tailor data flow
Run tests to verify data is syncing and deploy the integration
The Sprig integration exposes endpoints such as GET /contacts/:contactId GET /contacts/:contactId/tasks and GET /contacts/:contactId/notes. You can enable access through OAuth and select the endpoints you want to expose. This setup lets Sprig read data without writing code. In addition you can test the connection from your app dashboard and adjust permissions anytime. You can also review the endpoint reference in the API docs to understand response fields and how to map them into Sprig automations.
No coding is required to set up the connection. Use the visual integration builder to authorize Sprig and choose which data to pull. The workflow can be configured with drag and drop actions and tests run within the dashboard. If you do prefer advanced control you can export requests and map responses using standard API calls, but for most use cases the no code path is sufficient.
With the given scope contacts.readonly Sprig can view contacts tasks notes and related items. This keeps your data secure by preventing modifications through this connector. If you need additional permissions you can request extra scopes and reauthorize, then your app will have broader access as configured.
To test the connection use the built in test or run sample API requests in the developer console. Verify that you receive expected data for a sample contact and its tasks and notes. Check that subsequent automation steps map fields correctly and that data updates propagate to Sprig as designed.
Yes you can customize which endpoints are used by selecting them in the UI and adjusting field mappings. You can also disable endpoints you do not need to limit data exposure. Custom mappings let you tailor which contact fields flow into Sprig and how tasks notes and appointments are represented in your automations.
Access can be revoked at any time by revoking Sprig’s permission in your OAuth provider settings. After revocation Sprig will no longer access the Contacts API data. To disconnect simply remove the integration from your app dashboard and reauthorize if you wish to reconnect later.
The endpoint list is documented in the API reference under Endpoints. It includes the key read operations for contacts tasks notes and appointments as well as create update and delete operations where applicable. You can also view the endpoint list within the integration setup screen for quick reference.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
