simstudioai · waleedlatif1 · Feb 27, 2026 · Feb 25, 2026 · Feb 25, 2026 · Feb 25, 2026
diff --git a/apps/docs/components/icons.tsx b/apps/docs/components/icons.tsx
@@ -1265,6 +1265,20 @@ export function GoogleSlidesIcon(props: SVGProps<SVGSVGElement>) {
   )
 }
 
+export function GoogleContactsIcon(props: SVGProps<SVGSVGElement>) {
+  return (
+    <svg {...props} xmlns='http://www.w3.org/2000/svg' viewBox='0 0 500 500'>
+      <path fill='#86a9ff' d='M199 244c-89 0-161 71-161 160v67c0 16 13 29 29 29h77l77-256z' />
+      <path fill='#578cff' d='M462 349c0-58-48-105-106-105h-77v256h77c58 0 106-47 106-106' />
+      <path
+        fill='#0057cc'
+        d='M115 349c0-58 48-105 106-105h58c58 0 106 47 106 105v45c0 59-48 106-106 106H144c-16 0-29-13-29-29z'
+      />
+      <circle cx='250' cy='99.4' r='99.4' fill='#0057cc' />
+    </svg>
+  )
+}
+
 export function GoogleCalendarIcon(props: SVGProps<SVGSVGElement>) {
   return (
     <svg

diff --git a/apps/docs/components/ui/icon-mapping.ts b/apps/docs/components/ui/icon-mapping.ts
@@ -49,6 +49,7 @@ import {
   GoogleBigQueryIcon,
   GoogleBooksIcon,
   GoogleCalendarIcon,
+  GoogleContactsIcon,
   GoogleDocsIcon,
   GoogleDriveIcon,
   GoogleFormsIcon,
@@ -204,6 +205,7 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   google_bigquery: GoogleBigQueryIcon,
   google_books: GoogleBooksIcon,
   google_calendar_v2: GoogleCalendarIcon,
+  google_contacts: GoogleContactsIcon,
   google_docs: GoogleDocsIcon,
   google_drive: GoogleDriveIcon,
   google_forms: GoogleFormsIcon,

diff --git a/apps/docs/content/docs/en/tools/databricks.mdx b/apps/docs/content/docs/en/tools/databricks.mdx
@@ -5,7 +5,7 @@ description: Run SQL queries and manage jobs on Databricks
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
 
-<BlockInfoCard
+<BlockInfoCard 
   type="databricks"
   color="#FF3621"
 />
@@ -24,6 +24,7 @@ With the Databricks integration in Sim, you can:
 In Sim, the Databricks integration enables your agents to interact with your data lakehouse as part of automated workflows. Agents can query large-scale datasets, orchestrate ETL pipelines by triggering jobs, monitor job execution, and retrieve results—all without leaving the workflow canvas. This is ideal for automated reporting, data pipeline management, scheduled analytics, and building AI-driven data workflows that react to query results or job outcomes.
 {/* MANUAL-CONTENT-END */}
 
+
 ## Usage Instructions
 
 Connect to Databricks to execute SQL queries against SQL warehouses, trigger and monitor job runs, manage clusters, and retrieve run outputs. Requires a Personal Access Token and workspace host URL.

diff --git a/apps/docs/content/docs/en/tools/google_contacts.mdx b/apps/docs/content/docs/en/tools/google_contacts.mdx
@@ -0,0 +1,144 @@
+---
+title: Google Contacts
+description: Manage Google Contacts
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="google_contacts"
+  color="#E0E0E0"
+/>
+
+## Usage Instructions
+
+Integrate Google Contacts into the workflow. Can create, read, update, delete, list, and search contacts.
+
+
+
+## Tools
+
+### `google_contacts_create`
+
+Create a new contact in Google Contacts
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `givenName` | string | Yes | First name of the contact |
+| `familyName` | string | No | Last name of the contact |
+| `email` | string | No | Email address of the contact |
+| `emailType` | string | No | Email type: home, work, or other |
+| `phone` | string | No | Phone number of the contact |
+| `phoneType` | string | No | Phone type: mobile, home, work, or other |
+| `organization` | string | No | Organization/company name |
+| `jobTitle` | string | No | Job title at the organization |
+| `notes` | string | No | Notes or biography for the contact |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Contact creation confirmation message |
+| `metadata` | json | Created contact metadata including resource name and details |
+
+### `google_contacts_get`
+
+Get a specific contact from Google Contacts
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `resourceName` | string | Yes | Resource name of the contact \(e.g., people/c1234567890\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Contact retrieval confirmation message |
+| `metadata` | json | Contact details including name, email, phone, and organization |
+
+### `google_contacts_list`
+
+List contacts from Google Contacts
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `pageSize` | number | No | Number of contacts to return \(1-1000, default 100\) |
+| `pageToken` | string | No | Page token from a previous list request for pagination |
+| `sortOrder` | string | No | Sort order for contacts |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Summary of found contacts count |
+| `metadata` | json | List of contacts with pagination tokens |
+
+### `google_contacts_search`
+
+Search contacts in Google Contacts by name, email, phone, or organization
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `query` | string | Yes | Search query to match against contact names, emails, phones, and organizations |
+| `pageSize` | number | No | Number of results to return \(default 10, max 30\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Summary of search results count |
+| `metadata` | json | Search results with matching contacts |
+
+### `google_contacts_update`
+
+Update an existing contact in Google Contacts
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `resourceName` | string | Yes | Resource name of the contact \(e.g., people/c1234567890\) |
+| `etag` | string | Yes | ETag from a previous get request \(required for concurrency control\) |
+| `givenName` | string | No | Updated first name |
+| `familyName` | string | No | Updated last name |
+| `email` | string | No | Updated email address |
+| `emailType` | string | No | Email type: home, work, or other |
+| `phone` | string | No | Updated phone number |
+| `phoneType` | string | No | Phone type: mobile, home, work, or other |
+| `organization` | string | No | Updated organization/company name |
+| `jobTitle` | string | No | Updated job title |
+| `notes` | string | No | Updated notes or biography |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Contact update confirmation message |
+| `metadata` | json | Updated contact metadata |
+
+### `google_contacts_delete`
+
+Delete a contact from Google Contacts
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `resourceName` | string | Yes | Resource name of the contact to delete \(e.g., people/c1234567890\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Contact deletion confirmation message |
+| `metadata` | json | Deletion details including resource name |
+
+
diff --git a/apps/docs/content/docs/en/tools/greenhouse.mdx b/apps/docs/content/docs/en/tools/greenhouse.mdx
@@ -5,7 +5,7 @@ description: Manage candidates, jobs, and applications in Greenhouse
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
 
-<BlockInfoCard
+<BlockInfoCard 
   type="greenhouse"
   color="#469776"
 />
@@ -24,6 +24,7 @@ With the Greenhouse integration in Sim, you can:
 In Sim, the Greenhouse integration enables your agents to interact with your recruiting data as part of automated workflows. Agents can pull candidate information, monitor application pipelines, track job openings, and cross-reference hiring team data—all programmatically. This is ideal for building automated recruiting reports, candidate pipeline monitoring, hiring analytics dashboards, and workflows that react to changes in your talent pipeline.
 {/* MANUAL-CONTENT-END */}
 
+
 ## Usage Instructions
 
 Integrate Greenhouse into the workflow. List and retrieve candidates, jobs, applications, users, departments, offices, and job stages from your Greenhouse ATS account.

diff --git a/apps/docs/content/docs/en/tools/meta.json b/apps/docs/content/docs/en/tools/meta.json
@@ -44,6 +44,7 @@
     "google_bigquery",
     "google_books",
     "google_calendar",
+    "google_contacts",
     "google_docs",
     "google_drive",
     "google_forms",

diff --git a/...r/components/sub-block/components/credential-selector/components/oauth-required-modal.tsx b/...r/components/sub-block/components/credential-selector/components/oauth-required-modal.tsx
@@ -40,6 +40,7 @@ const SCOPE_DESCRIPTIONS: Record<string, string> = {
   'https://www.googleapis.com/auth/drive.file': 'View and manage Google Drive files',
   'https://www.googleapis.com/auth/drive': 'Access all Google Drive files',
   'https://www.googleapis.com/auth/calendar': 'View and manage calendar',
+  'https://www.googleapis.com/auth/contacts': 'View and manage Google Contacts',
   'https://www.googleapis.com/auth/tasks': 'Create, read, update, and delete Google Tasks',
   'https://www.googleapis.com/auth/userinfo.email': 'View email address',
   'https://www.googleapis.com/auth/userinfo.profile': 'View basic profile info',