Google Cloud Profiler
Manages continuous profiling information (Google OAuth2).
OCNORA ships 4 typed Google Cloud Profiler 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 Cloud Profiler
- 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 Cloud Profiler
Operations, grouped by what they do to your data.
A sample Google Cloud Profiler workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Profiler trigger is needed.
- 2List Profilescloud_profiler.list_profilesLists profiles which have been collected so far and for which the caller has permission to view.
- 3Create Offlinecloud_profiler.create_offlineCreateOfflineProfile creates a new profile resource in the offline mode. The client provides the profile to create along with the profile bytes, the server records it.
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 4
- Create OfflineCreateOfflineProfile creates a new profile resource in the offline mode. The client provides the profile to create along with the profile bytes, the server records it.cloud_profiler.create_offline
- Create ProfileCreateProfile creates a new profile resource in the online mode.cloud_profiler.create_profile
- List ProfilesLists profiles which have been collected so far and for which the caller has permission to view.cloud_profiler.list_profiles
- Patch ProfileUpdateProfile updates the profile bytes and labels on the profile resource created in the online mode.cloud_profiler.patch_profile
Google Cloud Profiler questions
- How does OCNORA authenticate with Google Cloud Profiler?
- 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 Cloud Profiler?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Profiler operation I need is not listed?
- Where Google Cloud Profiler 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 Cloud Profiler?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Profiler 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 Cloud Profiler 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.