google-contacts-createAtomic node skill to create a new google contact. Loops internally until successful.
Install via ClawdBot CLI:
clawdbot install zvirb/google-contacts-createGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 21, 2026
A sales rep meets a lead at a conference and immediately adds the person to Google Contacts via the agent so the lead is captured before it's forgotten. The contact becomes available for follow-up emails and future outreach sequences.
An operations team wires this skill into a pipeline that mirrors new customers from a CRM into Google Contacts so field staff see accurate records on their phones. It runs per-record after each CRM write, keeping contact lists consistent.
An assistant uses the skill to batch-create contacts for new hires or new clients, including names and emails, with the loop-until-success behavior handling transient API failures. This removes manual copy-paste work during onboarding.
A marketing team builds a workflow where scanned badge data is turned into Google Contacts entries after each trade show. The atomic skill creates each contact reliably so campaign follow-ups can start immediately.
A recruiter adds candidates from sourcing tools into Google Contacts for quick mobile access and outreach. The skill's autonomous error handling means failed creations are retried without babysitting.
An agency sells automation add-ons to clients who want their Google Workspace tools connected to internal systems. This create-contact skill is a building block in contact-management installs sold as monthly retainers.
A SaaS product enriches and deduplicates contact data, then writes final records to customers' Google Contacts. The skill handles the write path, enabling tiers that include automatic contact sync as a paid feature.
A marketplace sells prebuilt automation templates that include Google Contacts workflows for sales, recruiting, and events. This atomic skill provides the reliable contact-creation step inside those templates.
💬 Integration Tip
Wire this node after any contact-data normalization step so it receives clean, deduplicated inputs, and rely on its loop-until-success behavior to mask transient API failures in larger pipelines.
Scored Oct 21, 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).