Google Essential Contacts
Google CloudOAuth 2.0Connection test available
Essential Contacts (Google OAuth2).
OCNORA ships 6 typed Google Essential Contacts operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Essential Contacts
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Essential Contacts
Operations, grouped by what they do to your data.
Create and send 1
Read and search 2
Update 1
Delete and cancel 1
Other operations 1
A sample Google Essential Contacts workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Essential Contacts trigger is needed.
- 2Get Contactessential_contacts.get_contactGets a single contact.
- 3Compute Contactessential_contacts.compute_contactLists all contacts for the resource that are subscribed to the specified notification categories, including contacts inherited from any parent resources.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 6
- Compute ContactLists all contacts for the resource that are subscribed to the specified notification categories, including contacts inherited from any parent resources.essential_contacts.compute_contact
- Create ContactAdds a new contact for a resource.essential_contacts.create_contact
- Delete ContactDeletes a contact.essential_contacts.delete_contact
- Get ContactGets a single contact.essential_contacts.get_contact
- List ContactsLists the contacts that have been set on a resource.essential_contacts.list_contacts
- Update ContactUpdates a contact.essential_contacts.update_contact
Google Essential Contacts questions
- How does OCNORA authenticate with Google Essential Contacts?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Essential Contacts?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Essential Contacts operation I need is not listed?
- Where Google Essential Contacts has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Essential Contacts?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Essential Contacts calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Essential Contacts workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.