google-contacts-searchAtomic node skill to search google contacts. Loops internally until successful.
Install via ClawdBot CLI:
clawdbot install zvirb/google-contacts-searchGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 5, 2026
A sales operations team uses this skill to fetch Google Contacts by name or email during CRM data hygiene runs. It automatically fills missing phone numbers, job titles, and notes for thousands of records each night.
A field service dispatcher integrates the skill into their scheduling tool to instantly retrieve customer contact details by name. This reduces call handling time when technicians need to confirm appointments or site access.
An HR platform calls the skill to verify new hire contact information before creating employee profiles. It ensures personal emails and phone numbers match the company's Google Workspace directory.
A virtual event app uses the skill to look up attendee profiles by email during networking sessions. It quickly pulls up LinkedIn URLs, company names, and phone numbers for real-time introductions.
A helpdesk automation queries Google Contacts when a ticket is created to auto-fill caller details. This provides agents with context like account manager, department, and alternate phone numbers without manual lookup.
Sell the skill as a premium add-on for existing CRM or helpdesk platforms, enabling seamless Google Contacts search within their UI. Customers pay a monthly per-seat fee for the integration.
Offer a standalone API that charges per successful contact search query, ideal for event apps or data enrichment tools. Pricing scales with volume, offering discounts for high-volume tiers.
License the skill to large enterprises that need to sync Google Contacts with internal systems like HRIS or ERP. Includes professional services for setup and annual support contracts.
💬 Integration Tip
Wrap the skill in a retry loop with exponential backoff to handle any transient API failures, since it already loops internally for success; ensure COMPOSIO_API_KEY is securely stored in environment variables and rotate it periodically.
Scored May 25, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Query Google Places for text search, place details, resolve, reviews, or scriptable JSON via goplaces.
Google Contacts API integration with managed OAuth. Manage contacts, contact groups, and search your address book. Use this skill when users want to create, read, update, or delete contacts, manage contact groups, or search for people in their Google account. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Contacts connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Contacts action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Contacts examples; they add no Google Contacts capability - Google Contacts is not an event source, a trigger cannot read Google Contacts data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).