Can HumDay connect to Google Application Integration?

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

Do I need to write code to automate Google Application Integration?

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 Application Integration account.

What can HumDay do in Google Application Integration?

23 of the 40 documented operations change something in Google Application Integration, and 17 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Application Integration 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 Application Integration is held behind that approval.

Automate Google Application Integration

HumDay reads Google Application Integration’s own published API description and derives 40 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 HumDay can do in Google Application Integration

23 documented operations change something in Google Application Integration.

POSTCreates an sfdc channel record./v1/{parent}/sfdcChannels
POSTCreates an auth config record./v1/{parent}/authConfigs
POSTCreates a new certificate./v1/{parent}/certificates
POSTCreates an sfdc instance record./v1/{parent}/sfdcInstances
DELETEDeletes an sfdc channel./v1/{name}
PATCHUpdates an sfdc channel./v1/{name}
POSTLifts suspension for advanced suspension task./v1/{name}:lift
POSTSchedules an integration for execution by passing the trigger id and the scheduled time in the request body./v1/{name}:schedule
POSTSets the status of the ACTIVE integration to SNAPSHOT with a new tag "PREVIOUSLYPUBLISHED" after validating it./v1/{name}:unpublish
POSTCreate a integration with a draft version in the specified project./v1/{parent}/versions
POSTCreates an cloud function project./v1/{parent}/cloudFunctions
POSTUploads an integration./v1/{parent}/versions:upload
POSTPerform the provisioning steps to enable a user GCP project to use IP./v1/{parent}/clients:provision
POSTCreates an Apps Script project./v1/{parent}/appsScriptProjects
POSTPerform the deprovisioning steps to disable a user GCP project to use IP and purge all related data in a wipeout-compliant way./v1/{parent}/clients:deprovision
POSTExecute the integration in draft state/v1/{name}:test
POSTCancellation of an execution/v1/{name}:cancel
POSTExecutes integrations synchronously by passing the trigger id in the request body./v1/{name}:execute
POSTThis RPC throws an exception if the integration is in ARCHIVED or ACTIVE state./v1/{name}:publish
POSTResolves (lifts/rejects) any number of suspensions./v1/{name}:resolve
POSTClears the lockedby and lockedattimestampin the DRAFT version of this integration./v1/{integrationVersion}:takeoverEditLock
POSTUpdate client from GMEK to CMEK/v1/{parent}/clients:switch
POSTLinks a existing Apps Script project./v1/{parent}/appsScriptProjects:link

What HumDay can read from Google Application Integration

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

GETGets an sfdc channel. If the channel doesn't exist, Code.NOTFOUND exception will be thrown./v1/{name}
GETReturns the list of all integration versions in the specified project./v1/{parent}/versions
GETList all the certificates that match the filter./v1/{parent}/certificates
GETReturns the list of all integrations in the specified project./v1/{parent}/integrations
GETLists all sfdc channels that match the filter./v1/{parent}/sfdcChannels
GETReceives the auth code and auth config id to combine that with the client id and secret to retrieve access tokens from the token endpoint./v1/callback:generateToken
GETDownloads an integration./v1/{name}:download
GETEnumerates the regions for which Connector Platform is provisioned./v1/connectorPlatformRegions:enumerate
GETGets the client configuration for the given project and location resource name/v1/{parent}/clients
GETLists the results of all the integration executions./v1/{parent}/executions
GETLists all auth configs that match the filter./v1/{parent}/authConfigs
GETLists Connections in a given project and location./v1/{parent}/connections
GETLists suspensions associated with a specific execution./v1/{parent}/suspensions
GETLists all sfdc instances that match the filter./v1/{parent}/sfdcInstances
GETGets the metadata info for the requested client/v1/{parent}/clientmetadata
GETLists the JSON schemas for the inputs and outputs of actions, filtered by action name./v1/{parent}/runtimeActionSchemas
GETLists the JSON schemas for the properties of runtime entities, filtered by entity name./v1/{parent}/runtimeEntitySchemas

How automating Google Application Integration 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 Application Integration account.
Grant access, then go live. You approve the specific Google Application Integration operations it may use — and only those.