data
Google Data Manager CLI for CI
Use the Google Data Manager CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
6 functions 2 read 4 write oauth2 auth
Google Data Manager CLI for CI
Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.
Use this shape when a pipeline needs to read or update an external service. The Google Data Manager CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Google Data Manager CLI for CI
kosmokrator integrations:configure google_data_manager --enable --read allow --write ask --json
kosmo integrations:call google_data_manager.google_data_manager_diagnostics '{}' --json Discovery Before Execution
Agents and scripts can inspect Google Data Manager docs and schemas before choosing a function.
kosmo integrations:docs google_data_manager --json
kosmo integrations:docs google_data_manager.google_data_manager_diagnostics --json
kosmo integrations:schema google_data_manager.google_data_manager_diagnostics --json
kosmo integrations:search "Google Data Manager" --json
kosmo integrations:list --json Useful Google Data Manager CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
google_data_manager.google_data_manager_diagnostics | Read | none | Show safe configuration diagnostics. |
google_data_manager.google_data_manager_ingest_events | Write | none | Upload conversion event resources to destinations. |
google_data_manager.google_data_manager_ingest_audience_members | Write | none | Upload audience member resources to destinations. |
google_data_manager.google_data_manager_remove_audience_members | Write | none | Remove audience members from destinations. |
google_data_manager.google_data_manager_retrieve_request_status | Read | none | Poll request processing status by request ID. |
google_data_manager.google_data_manager_raw_request | Write | none | Low-level Data Manager API request for new endpoints. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.