Google Keep actions: read and automate through the Google API.
Usage and specifics
Select Google Workspace with service scopes and enabled APIs. Supply operation path parameters, query and body. Triggers poll changes after publishing and initializing the baseline. Administrator permissions, domain delegation and quotas depend on the service.
Technical type : google_keep. Runtime : nodulz.
Credentials and prerequisites
Google Workspace (integration / google_workspace). OAuth or service account for Calendar, Analytics and other Google APIs.
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Parameter
Type
Default
Values / limits
credentialId
string
""
-
operation
string
"list_notes"
-
parameters
record
{}
-
query
string
"{}"
-
data
string
""
-
pollInterval
number
60
-; ≥ 30, ≤ 86400
events
array
["created","updated"]
-; min 1
Configuration help
credentialId Google Workspace credential
User OAuth or service account. Enable the API and authorize the listed scopes. The user also needs Google resource permissions.
data Advanced JSON body
Official Google object. Examples are prefilled. Use requests for batch updates and etag when updating contacts. Expressions are supported.
query Advanced parameters (JSON)
Additional URL parameters as an object. Lists return nextPageToken; reuse it as pageToken. Triggers follow every page and disallow pageToken and fields.
events Events
The first snapshot establishes a baseline without running the workflow. Subsequent snapshots detect additions and updates. Explicit deletions are available for Calendar and Tasks. Missing resources are not treated as deleted.
pollInterval Check interval (seconds)
30 to 86400 seconds. Google quotas apply. Intermediate changes between snapshots may be missed.
Available operations
ID
HTTP
Path / parameters
list_notes
GET
/notes
get_note
GET
/notes/{noteId}
create_note
POST
/notes - title, body.text.text
delete_note
DELETE
/notes/{noteId}
An asterisk marks an operation-required parameter. Body fields and permissions depend on the selected operation; use its guided form and the provider’s official reference.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Google Keep actions: read and automate through the Google API.
Usage and specifics
Select Google Workspace with service scopes and enabled APIs. Supply operation path parameters, query and body. Triggers poll changes after publishing and initializing the baseline. Administrator permissions, domain delegation and quotas depend on the service.
Technical type :
google_keep. Runtime :nodulz.Credentials and prerequisites
integration/google_workspace). OAuth or service account for Calendar, Analytics and other Google APIs.Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
credentialIdstring""operationstring"list_notes"parametersrecord{}querystring"{}"datastring""pollIntervalnumber60eventsarray["created","updated"]Configuration help
credentialIdGoogle Workspace credential
dataAdvanced JSON body
queryAdvanced parameters (JSON)
eventsEvents
pollIntervalCheck interval (seconds)
Available operations
list_notesGET/notesget_noteGET/notes/{noteId}create_notePOST/notes-title,body.text.textdelete_noteDELETE/notes/{noteId}An asterisk marks an operation-required parameter. Body fields and permissions depend on the selected operation; use its guided form and the provider’s official reference.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "credentialId": "", "operation": "list_notes", "parameters": {}, "query": "{}", "data": "", "pollInterval": 60, "events": [ "created", "updated" ] }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.