google-contactsGoogle 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).
Install via ClawdBot CLI:
clawdbot install byungkyu/google-contactsGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.ai/byungkyu/api-gatewayUses known external API (expected, informational)
discord.comAudited Apr 16, 2026 · audit v1.0
Generated Feb 24, 2026
Sales teams can automatically sync new leads from CRM systems to Google Contacts, ensuring contact details are updated in real-time. This reduces manual data entry and improves accuracy in client communication. It also enables quick access to contact histories during sales calls.
Event planners can manage attendee lists by creating and updating contacts for participants, speakers, and vendors in Google Contacts. This facilitates easy communication and scheduling through integrated email and calendar tools. It helps streamline event logistics and follow-ups.
Support teams can link customer support tickets to Google Contacts to maintain up-to-date contact information and interaction histories. This allows for personalized support and faster resolution by accessing past communications. It enhances customer relationship management in service industries.
HR departments can use this skill to manage candidate contacts, track application stages, and schedule interviews via integrated tools. It helps organize recruitment pipelines and improve communication with potential hires. This streamlines the hiring process for companies.
Freelancers can centralize client contacts, project details, and billing information in Google Contacts for easy access and organization. This simplifies invoicing and follow-up communications, improving productivity. It supports small business operations and independent contractors.
Offer a subscription-based service that integrates Google Contacts with other business tools like CRMs or email marketing platforms. Charge monthly or annual fees for access to advanced features and support. This model provides recurring revenue and scales with customer growth.
Implement a tiered pricing model based on API call volume, number of contacts managed, or features like advanced search. Offer free tiers for basic usage and paid tiers for higher limits and premium functionalities. This attracts a wide range of users from individuals to enterprises.
Provide white-label versions of the integration for other companies to rebrand and resell as part of their own products. Charge licensing fees or revenue shares for customization and support services. This expands market reach through partnerships and resellers.
💬 Integration Tip
Ensure the MATON_API_KEY is securely stored in environment variables and test connection management endpoints before deploying to production to avoid authentication issues.
Scored May 17, 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.
Google Docs API integration with managed OAuth. Create documents, insert text, apply formatting, and manage content. Use this skill when users want to interact with Google Docs. 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 Docs connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Docs 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 Docs examples; they add no Google Docs capability - Google Docs is not an event source, a trigger cannot read Google Docs 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).
Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. 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 Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides 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 Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides 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).