Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Google Contacts

Stay connected and organized

CategorySales And Crm
AuthenticationOAuth 2.0
Version0.5.0
Published scopes2 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Google Contacts with Flows360

Stay connected and organized

Use the Google Contacts connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 1 trigger.

Available actions

  • Add Contact
  • Update Contact
  • Search Contacts
  • Custom API Call

Available triggers

  • New Or Updated Contact

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Google Contacts
  • Package: @activepieces/piece-google-contacts@0.5.0
  • Exact artifact digest: sha256:01eb907c6746504a51dfa5961eedc4d9ec160aacea0077c6f76a052fadf1037d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Contact (add_contact), Add a contact to a Google Contacts account Classification: read.
  • Update Contact (update_contact), Update a contact in Google Contacts account. Classification: read.
  • Search Contacts (search_contact), Search contacts in Google Contacts account. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Or Updated Contact, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects5
Supported actionsNot published
Triggers1

Authentication

Authentication method: OAuth 2.0

Required scopes

https://www.googleapis.com/auth/contactsemail

Authentication profiles

connection · oauth2

OAuth scopes: https://www.googleapis.com/auth/contacts, email

Supported objects

ObjectReadWriteNotes
Add Contact Yes No Add a contact to a Google Contacts account
Update Contact Yes No Update a contact in Google Contacts account.
Search Contacts Yes No Search contacts in Google Contacts account.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Or Updated Contact Yes No polling trigger declared by the pinned package.

Triggers

New Or Updated Contact · Poll

Triggers when there is a new or updated contact

Setup

Setup

  1. Add the Google Contacts connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • https://www.googleapis.com/auth/contacts
  • email
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-google-contacts@0.5.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Google Contacts connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-google-contacts@0.5.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com