CRM
Google Contacts
Connect Google Contacts once and hand every teammate a governed MCP endpoint with 6 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards ship on the Black plan.
Automations
Put Google Contacts work on a schedule.
A trigger starts a sequence of steps: call a Google Contacts tool, transform the result, branch, wait, and ask a person when it matters.
Google Contacts digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch userinfos
Google Contacts
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Contacts
Queued
Collections and dashboards
Report on Google Contacts without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Google Contacts health
Refreshed 4 minutes ago · every 15 minutes · from the userinfos collection
Userinfos
1,284 ↓ 12%
Peoples
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Userinfos created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
AI tools
Google Contacts tools for your AI agents
6 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Contacts, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
list_all_googlecontacts_search_contacts
Get a list of contacts matching the query in Google Calendar. Requires query and readMask. Returns matched contacts with fields specified in readMask such as names, emailAddresses, phoneNumbers, and organizations.
get_single_googlecontacts_search_contact_by_id
Get information about a specific contact by id in Google Calendar. Requires personFields parameter specifying which fields to return such as names, emailAddresses, phoneNumbers, and organizations.
delete_a_googlecontacts_search_contact_by_id
Delete a contact person by id in Google Calendar. The response is empty if successful. Non-contact data will not be deleted. Mutate requests must be sent sequentially to avoid latency and failures.
list_all_googlecontacts_other_contacts
Get a list of other contacts matching the query in Google Calendar. Requires query and readMask parameters. Returns matched contacts with fields emailAddresses, metadata, names, and phoneNumbers.
list_all_googlecontacts_userinfo
Retrieves basic profile information about the authenticated user in Google Calendar. The response includes essential details such as the user's unique identifier (sub), full name (name), first name (given_name), last name (family_name), profile picture URL (picture), and email address (email).
list_all_googlecontacts_people
List people from the Google directory via the People API. Returns a collection of people objects from the caller's domain directory.
No tools match your search.
How it works
From Google Contacts account to governed MCP endpoint
Connect
Link a Google Contacts account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Google Contacts tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.