How does OCNORA authenticate with Google Eventarc?

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 Eventarc?

10 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Eventarc operation I need is not listed?

Where Google Eventarc 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 Eventarc?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Eventarc 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.

Google Eventarc

Google CloudOAuth 2.0Connection test available

Build event-driven applications on Google Cloud Platform (Google OAuth2).

OCNORA ships 10 typed Google Eventarc 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.

Ask about Google Eventarc Google Eventarc API docs ↗

Before you connect Google Eventarc

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 Eventarc

Operations, grouped by what they do to your data.

Create and send 2

Read and search 4

Update 2

Delete and cancel 2

A sample Google Eventarc workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Eventarc trigger is needed.
2
Get Channeleventarc.get_channel
Get a single Channel.
3
Create Channeleventarc.create_channel
Create a new channel in a particular project and location.

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 10

Google Eventarc questions

How does OCNORA authenticate with Google Eventarc?: 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 Eventarc?: 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Eventarc operation I need is not listed?: Where Google Eventarc 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 Eventarc?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Eventarc 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 Eventarc 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.

Book a technical demo Talk to sales