Can HumDay connect to Google Connectors?

Yes. HumDay reads Google Connectors's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 11 operations are documented.

Do I need to write code to automate Google Connectors?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Connectors account.

What can HumDay do in Google Connectors?

7 of the 11 documented operations change something in Google Connectors, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Connectors account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Connectors is held behind that approval.

Automate Google Connectors

HumDay reads Google Connectors’s own published API description and derives 11 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Connectors is

Enables users to create and manage connections to Google Cloud services and third-party business applications using the Connectors interface.

API host: connectors.googleapis.com

What HumDay can do in Google Connectors

7 documented operations change something in Google Connectors.

POSTCreates a new entity row of the specified entity type in the external system./v2/{parent}/entities
DELETEDeletes an existing entity row matching the entity type and entity id specified in the request./v2/{name}
PATCHUpdates an existing entity row matching the entity type and entity id specified in the request./v2/{name}
POSTExecutes an action with the name specified in the request./v2/{name}:execute
POSTExecutes a SQL statement specified in the body of the request./v2/{connection}:executeSqlQuery
POSTDeletes entities based on conditions specified in the request and not on entity id./v2/{entityType}/entities:deleteEntitiesWithConditions
POSTUpdates entities based on conditions specified in the request and not on entity id./v2/{entityType}/entities:updateEntitiesWithConditions

What HumDay can read from Google Connectors

These are the operations a schedule or a trigger can watch.

GETGets a single entity row matching the entity type and entity id specified in the request./v2/{name}
GETLists entity rows of a particular entity type contained in the request./v2/{parent}/entities
GETGets the schema of all the actions supported by the connector./v2/{parent}/actions
GETLists metadata related to all entity types present in the external system./v2/{parent}/entityTypes

How automating Google Connectors works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Connectors account.
Grant access, then go live. You approve the specific Google Connectors operations it may use — and only those.