Use your API key with the Contacts API and ensure the scope is set to read‑only (contacts.readonly) to access data securely from Geckoboard.
In Geckoboard, add the Contacts API connector and paste your API key in the credentials section. Treat these credentials like a password and keep them secure.
Endpoints used by this integration 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: Dashboard requests a specific contact by ID to display their profile.
Actions: Return contact fields such as name, email, phone, and company to Geckoboard widgets.
GET /contacts/:contactId
contactId, firstName, lastName, email, phone, company
Trigger: When a user selects a contact to view tasks.
Actions: Return taskCount, task details, and status.
GET /contacts/:contactId/tasks
contactId, taskId, title, status, dueDate, completed
Actions: Return recent notes and note counts for display.
GET /contacts/:contactId/notes
contactId, noteId, note, date
Build live dashboards without writing code. The Geckoboard connector handles requests and field mapping visually.
Get started quickly with prebuilt endpoints and widgets that you can customize to your needs.
Scale your dashboards as your data grows by adding new endpoints and fields with minimal effort.
Key terms to help you understand how the Geckoboard connector uses the GHL Contacts API.
Application Programming Interface – a defined set of endpoints and rules that lets apps talk to each other.
A specific URL path exposed by an API to fetch or modify data.
The process of proving identity to access API resources, typically via API keys or OAuth tokens.
A callback URL that Geckoboard can ping to trigger actions or data pushes.
Visualize new contacts, open tasks, and recent notes in a single overview widget to monitor engagement.
Aggregate notes and completed tasks to show context per contact and improve response times.
Combine business‑level endpoints to surface health trends and activity across accounts.
Obtain your Contacts API key and confirm the read‑only scope to protect sensitive data.
Enter the API key in Geckoboard’s connector settings, then map fields to your widgets.
Create widgets for contacts, tasks, notes and publish your live dashboard.
No‑code setup is possible with the Geckoboard connector. Configure endpoints and widget mappings in the Geckoboard UI without writing code. You can reuse saved configurations to deploy dashboards quickly. The API key is used in request headers and should be kept secret.
Endpoints available include GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes, 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. You can select the endpoints that match your dashboard needs.
API keys authorize requests to the GHL Contacts API. Use a key with the least privilege necessary (read‑only when possible). Store keys securely, rotate regularly, and monitor usage. If your key is compromised, rotate immediately and update your Geckoboard connector.
Yes. Geckoboard supports filters via query parameters or widget settings. You can limit results by date ranges, contact fields, or task status. This helps you tailor visualizations without pulling extra data.
Refresh frequency depends on your Geckoboard plan and widget settings. Typical dashboards refresh every 5 to 15 minutes, with real‑time options via webhooks where available.
You can add more endpoints or data streams by updating your widget configuration and re‑authenticating if needed. The connector is designed to scale as your data needs grow.
If you run into issues, check that your API key and scope are correct, ensure the endpoint permissions match your data needs, and review Geckoboard widget mappings. Our troubleshooting guide and support team can help diagnose common errors.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
